Re: [Json] serializing sequences of JSON values

Carsten Bormann <cabo@tzi.org> Fri, 14 March 2014 23:02 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2728F1A01FE for <json@ietfa.amsl.com>; Fri, 14 Mar 2014 16:02:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.549
X-Spam-Level:
X-Spam-Status: No, score=-1.549 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NhrhMtWlLn9w for <json@ietfa.amsl.com>; Fri, 14 Mar 2014 16:02:19 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 616841A01F5 for <json@ietf.org>; Fri, 14 Mar 2014 16:02:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id s2EN1x1X012132; Sat, 15 Mar 2014 00:01:59 +0100 (CET)
Received: from [192.168.217.140] (p54890704.dip0.t-ipconnect.de [84.137.7.4]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 27E5432A; Sat, 15 Mar 2014 00:01:59 +0100 (CET)
Content-Type: multipart/alternative; boundary=Apple-Mail-4853ACD3-0F1A-4A77-8707-5E2986595686
Mime-Version: 1.0 (1.0)
From: Carsten Bormann <cabo@tzi.org>
X-Mailer: iPad Mail (11D167)
In-Reply-To: <CAGrxA270ARHz-XepgY-4PpTGqJG+4xGbFQ15kWYXPs_52vHtEg@mail.gmail.com>
Date: Sat, 15 Mar 2014 00:01:57 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <3DE14AC0-BF6F-4BFB-AF47-53BD3513BA05@tzi.org>
References: <em2c025504-6532-4513-a339-3d71c4cdfbda@helsinki> <5FC8412F-30E5-4F80-AB63-6715B1053098@vpnc.org> <58a4b20f768b484c94a850c4eba71ec5@BL2PR02MB307.namprd02.prod.outlook.com> <53222FFC.8070204@cisco.com> <5322714F.6080508@it.aoyama.ac.jp> <CAGrxA26HRqa+R580qfEMXU_JGid-UDzwwmQigOkOW0OWuA9mpg@mail.gmail.com> <CAK3OfOier6uQ4nVuuCP+uWV+eRbYh8qqAi4FVdWqNLHOh94L+A@mail.gmail.com> <CAGrxA275TwvbUkAT7tp9NtgTDN1WwPNP33aKmAZdB7QJkSY0CA@mail.gmail.com> <CAK3OfOj3e7pqj5R-ggHhXfaN5p1CG+6djiLizaRE2nJnF1ivGA@mail.gmail.com> <CAK3OfOhYxRR1ii3=eezXAmUR1ArpZDmAzbjRdHL2ASQ7Y1deDw@mail.gmail.com> <CAGrxA270ARHz-XepgY-4PpTGqJG+4xGbFQ15kWYXPs_52vHtEg@mail.gmail.com>
To: Tatu Saloranta <tsaloranta@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/json/vDrqvBOcxSLOUSs6oCPRXUZ42m4
Cc: Nico Williams <nico@cryptonector.com>, "json@ietf.org" <json@ietf.org>, Matt Miller <mamille2@cisco.com>
Subject: Re: [Json] serializing sequences of JSON values
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Mar 2014 23:02:21 -0000


> On 14.03.2014, at 20:30, Tatu Saloranta <tsaloranta@gmail.com> wrote:
> 
>> On Fri, Mar 14, 2014 at 4:37 PM, Nico Williams <nico@cryptonector.com> wrote:
>> The most interoperable form of JSON text sequence would be this:
>> encoders MUST not use newlines in their JSON text encodings and MUST
>> follow each JSON text with a newline.
> 
> And presumably this would include all linefeeds that JSON specification supports? (\r, \n and \r\n).
> 

I hope not.

\r newlines no longer exist in the real world.
\r\n on the other hand is just a special case of \n, a sane parser can then just key on \n.

Grüße, Carsten