IETF Logo Mail Archive

Re: [Json] serializing sequences of JSON values

Tatu Saloranta <tsaloranta@gmail.com> Sat, 15 March 2014 16:34 UTC

Return-Path: <tsaloranta@gmail.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 D359B1A00C3 for <json@ietfa.amsl.com>; Sat, 15 Mar 2014 09:34:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 XgLa5i6pPoR9 for <json@ietfa.amsl.com>; Sat, 15 Mar 2014 09:34:35 -0700 (PDT)
Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) by ietfa.amsl.com (Postfix) with ESMTP id 1EFE11A00B1 for <json@ietf.org>; Sat, 15 Mar 2014 09:34:34 -0700 (PDT)
Received: by mail-wi0-f176.google.com with SMTP id hr14so667804wib.9 for <json@ietf.org>; Sat, 15 Mar 2014 09:34:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=KoSdlq0Sij+GWf1/P5v4fnOd3dmwALZAP+CPc5e/wM8=; b=Apf9hSXEMH/9WqeQHePpMpWfRqHJlOVwbMRskxBrb4gKM0C99Y2WTnjZLUwDDclJ2k fpzFOjykEeUgg+7jvFQ5hxl2mouCNMO8iFJspZ6XBS4GYpo3zdI/jKMDoXjwto8WD16f C0cdkmizx71fHPiOkaA78REBa5JJJWsNcg8nyoeqLpwebAjp6jhk9K8GW4HCUbg5I4iI j/oM1/L9B8cxY6Kx3Jenx/uDmboEvBtoyqyFgkEWqBQ1OgiyEU/b4cZ+2cMGrH0cPC8B mPaxZEejdQ3EVYDroxxZJ3hL1RpKu1CyudkcLjAqLtDxBgRotkqFBq89Q+qwJQzAUprY xoAA==
MIME-Version: 1.0
X-Received: by 10.180.126.38 with SMTP id mv6mr2967563wib.46.1394901267442; Sat, 15 Mar 2014 09:34:27 -0700 (PDT)
Received: by 10.227.245.10 with HTTP; Sat, 15 Mar 2014 09:34:27 -0700 (PDT)
In-Reply-To: <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> <3DE14AC0-BF6F-4BFB-AF47-53BD3513BA05@tzi.org>
Date: Sat, 15 Mar 2014 16:34:27 +0000
Message-ID: <CAGrxA24mspME0C_PvErq5i9YCiSuV9-7NYd04PQoNn1CxKYXWQ@mail.gmail.com>
From: Tatu Saloranta <tsaloranta@gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary="e89a8f839ccb8af1df04f4a7c248"
Archived-At: http://mailarchive.ietf.org/arch/msg/json/HGUVn8PCjinMDv5Bcat1QeuwtmA
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: Sat, 15 Mar 2014 16:34:37 -0000

On Fri, Mar 14, 2014 at 11:01 PM, Carsten Bormann <cabo@tzi.org> wrote:

>
>
> 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.
>

I don't care deeply one way or another, but since I was assuming "of course
those are accepted" (as per XML, or JSON parsers I'm familiar with), this
needs to be specified to improve interoperability.

-+ Tatu +-

v2.23.0 | Report a Bug | By Email