Re: [Json] serializing sequences of JSON values

"Jim Schaad" <ietf@augustcellars.com> Sat, 15 March 2014 02:36 UTC

Return-Path: <ietf@augustcellars.com>
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 198B71A0271 for <json@ietfa.amsl.com>; Fri, 14 Mar 2014 19:36:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 z-HGDnVeowpN for <json@ietfa.amsl.com>; Fri, 14 Mar 2014 19:36:20 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id AC80D1A0274 for <json@ietf.org>; Fri, 14 Mar 2014 19:36:18 -0700 (PDT)
Received: from Philemon (c-24-17-142-118.hsd1.wa.comcast.net [24.17.142.118]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id 9563038F85; Fri, 14 Mar 2014 19:36:11 -0700 (PDT)
From: "Jim Schaad" <ietf@augustcellars.com>
To: "'Carsten Bormann'" <cabo@tzi.org>, "'Tatu Saloranta'" <tsaloranta@gmail.com>
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> <3DE14AC0-BF6F-4BFB-AF47-53BD3513BA05@tzi.org>
In-Reply-To: <3DE14AC0-BF6F-4BFB-AF47-53BD3513BA05@tzi.org>
Date: Fri, 14 Mar 2014 19:34:23 -0700
Message-ID: <008b01cf3ff7$142c8e10$3c85aa30$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_008C_01CF3FBC.67CF8AD0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQEqnQ8EEvzQtZ7rey/gYepvhD2GLAKRxiKzAYVBhPYBriReLQI7Hj43A1aD63gCNhEeXgIzXFVYAsB+nrgA4vfrogHWBWTFAvv4ST2baQZn0A==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/json/BWXkxq8ihtyqUJrKOU-EcD0oDL4
Cc: 'Nico Williams' <nico@cryptonector.com>, 'Matt Miller' <mamille2@cisco.com>, json@ietf.org
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: Sat, 15 Mar 2014 02:36:22 -0000

 

 

From: json [mailto:json-bounces@ietf.org] On Behalf Of Carsten Bormann
Sent: Friday, March 14, 2014 4:02 PM
To: Tatu Saloranta
Cc: Nico Williams; json@ietf.org; Matt Miller
Subject: Re: [Json] serializing sequences of JSON values

 

 


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.

 

But I have seen \r\r\n on more than one occasion in the real world

 

Grüße, Carsten