Re: [Json] serializing sequences of JSON values

Jacob Davies <jacob@well.com> Mon, 10 March 2014 18:14 UTC

Return-Path: <cromis@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 CAF701A0668 for <json@ietfa.amsl.com>; Mon, 10 Mar 2014 11:14:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.177
X-Spam-Level: *
X-Spam-Status: No, score=1.177 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, FRT_ADOBE2=2.455, SPF_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 iBrQdT50ErwX for <json@ietfa.amsl.com>; Mon, 10 Mar 2014 11:14:55 -0700 (PDT)
Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 99D221A04E7 for <json@ietf.org>; Mon, 10 Mar 2014 11:14:55 -0700 (PDT)
Received: by mail-pd0-f178.google.com with SMTP id x10so7390886pdj.37 for <json@ietf.org>; Mon, 10 Mar 2014 11:14:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=u90TbgNIp17DscybYEWeOccqICweBwa10NsWvn0nl2k=; b=wrN2PNCgSShUgPcKrIe8F+xGfedYf6JnEGL6c6FIS9JmsqchRLTFMHIvRLgbjh9HRl Egbc2AItK9ZRdxqmu5DXvjFLAEdKFYEcKvSdO1pkk3DK6EgE9mVE644Kgan7PLgnou9m LbaxZ4Edqe+7y+iLVPOtb3MQX1KETYR4NS2ZssHkgSFXYcr1hFy/Pjo1Npjq9xqPrpVr 5GPbCfP1N9ks/ZsDms9WDZZwG7pBCgc3zAZqVPp9YZn0AZTxxiH2cpaodtvrcID5ckSq goeESxQScu+iGEvYOnTjfbnTVZnblN2aCcpjxnaHbenkAKEVnqqYeZRv80MjupGA4K4F p89A==
X-Received: by 10.66.250.202 with SMTP id ze10mr5399067pac.153.1394475289648; Mon, 10 Mar 2014 11:14:49 -0700 (PDT)
MIME-Version: 1.0
Sender: cromis@gmail.com
Received: by 10.70.7.5 with HTTP; Mon, 10 Mar 2014 11:14:29 -0700 (PDT)
In-Reply-To: <CAK3OfOigDS2CizGAtdRaQWbSgiJqw0Ogi-TPkWv35GjPB=CQGw@mail.gmail.com>
References: <c19534113ff9489abcc4402fae3c1f62@BL2PR02MB307.namprd02.prod.outlook.com> <CAK3OfOigDS2CizGAtdRaQWbSgiJqw0Ogi-TPkWv35GjPB=CQGw@mail.gmail.com>
From: Jacob Davies <jacob@well.com>
Date: Mon, 10 Mar 2014 11:14:29 -0700
X-Google-Sender-Auth: lx4pDCatJGkvsVJ2eX8Bv54WP_g
Message-ID: <CAO1wJ5SLFoUSGoyM4WZa+r2Sf1A_-9e1DmUtRQqfx0UT77VXTA@mail.gmail.com>
To: Nico Williams <nico@cryptonector.com>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/json/9hvA2JOr3Uex80M_QKU4jGRrwuE
X-Mailman-Approved-At: Mon, 10 Mar 2014 11:16:03 -0700
Cc: Barry Leiba <barryleiba@computer.org>, Pete Resnick <presnick@qti.qualcomm.com>, Bjoern Hoehrmann <derhoermi@gmx.net>, Paul Hoffman <paul.hoffman@vpnc.org>, "json@ietf.org" <json@ietf.org>, "Paul E. Jones" <paulej@packetizer.com>, Tim Bray <tbray@textuality.com>, "Joe Hildebrand \(jhildebr\)" <jhildebr@cisco.com>, "Matt Miller \(mamille2\)" <mamille2@cisco.com>, Larry Masinter <masinter@adobe.com>, "rfc7158@schmorp.de" <rfc7158@schmorp.de>
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: Mon, 10 Mar 2014 18:14:57 -0000

Does either the old or new specification say anything about multiple
values in sequence? I'm pretty darn sure the old version at least said
that application/json documents contain one and only one value, and
says nothing about serializing JSON in other formats, so encapsulation
is not addressed. I also don't see how any process that expects to
read sequences of self-delimited JSON objects and arrays is going to
blithely accept numbers and strings and whatnot. I find the idea
unlikely that there is some running code that 1. expects sequences of
JSON values with no delimiters, 2. uses a parser that precisely
followed the JSON specification and rejected anything but JSON objects
and arrays prior to this change, 3. has that parser change under it to
accept all kinds of values and 4. is so indifferent to the contents of
what it is processing that it doesn't notice that it's getting numbers
and strings instead of objects or arrays.

On Sun, Mar 9, 2014 at 3:37 PM, Nico Williams <nico@cryptonector.com> wrote:
>
> On Mar 9, 2014 4:16 AM, "Larry Masinter" <masinter@adobe.com> wrote:
>>
>> >  This means the serializer would have to be explicitly told whether to
>> > insert space before or after
>> > writing out data.
>>
>> If you want to write out a sequence of JSON values you would write them
>> out as an array with [] around and comma separators.
>
> Doesn't work for log files...
>
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>