IETF Logo Mail Archive

Re: [Json] serializing sequences of JSON values

Tim Bray <tbray@textuality.com> Sun, 09 March 2014 16:44 UTC

Return-Path: <tbray@textuality.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 481031A0268 for <json@ietfa.amsl.com>; Sun, 9 Mar 2014 09:44:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.478
X-Spam-Level:
X-Spam-Status: No, score=0.478 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, FRT_ADOBE2=2.455, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 H8v5DBOQcjfa for <json@ietfa.amsl.com>; Sun, 9 Mar 2014 09:44:40 -0700 (PDT)
Received: from mail-vc0-f180.google.com (mail-vc0-f180.google.com [209.85.220.180]) by ietfa.amsl.com (Postfix) with ESMTP id ACF921A0277 for <json@ietf.org>; Sun, 9 Mar 2014 09:44:39 -0700 (PDT)
Received: by mail-vc0-f180.google.com with SMTP id lf12so363188vcb.39 for <json@ietf.org>; Sun, 09 Mar 2014 09:44:34 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=//QypL2fAD8swhiEDD7HKLtVlq7uLy5oWtxwwqAFuyM=; b=PNFs45g05xl96g6T50+hriNieH9UqWWioMtCPh/0iucwaAH4uFxPGoeRvVQ2Vggemo 9nelGo/Yu3hn68x7VuAkMu8AbAdwh1T/Eou5+F1hcJW8SXAaaYy/eI0j7wfXbwhrshQ7 7s19QyONjyLQAQ3QnJgDvFvtSuN12eDPAsO3X8gCgAyDjMbGoxWFGUnLcyc7pYk1ZNx6 cxkiwyJOK3znK6TDXsR1qca/dYnMWIpiBz8aUbC8if6//epXv+0j9M50iRnLY4AS24IS MZNRwQCgK3N9cH3TRouEBiL8L9pxe4T5hP1B3rZ+vHIBYCPdheBL3a+3r0v7VmJORz/j 2jIQ==
X-Gm-Message-State: ALoCoQmzg7P77NJJMMZCL3+aJ081JKCHshuMNOUlyoBba1TS6O/U7SP3HDr7fe4OysqrX3+i1Tm0
MIME-Version: 1.0
X-Received: by 10.220.12.140 with SMTP id x12mr18842820vcx.19.1394383474503; Sun, 09 Mar 2014 09:44:34 -0700 (PDT)
Received: by 10.220.98.73 with HTTP; Sun, 9 Mar 2014 09:44:34 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <65449749-1e0e-40c8-9277-bd255b4c302f@email.android.com>
References: <c19534113ff9489abcc4402fae3c1f62@BL2PR02MB307.namprd02.prod.outlook.com> <20140309143608.GA14656@mercury.ccil.org> <65449749-1e0e-40c8-9277-bd255b4c302f@email.android.com>
Date: Sun, 09 Mar 2014 09:44:34 -0700
Message-ID: <CAHBU6isBxYvhSE6rpcXf3dGwzEKevuw2Vmvb8DaPG9sH1-Au7g@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: "Paul E. Jones" <paulej@packetizer.com>
Content-Type: multipart/alternative; boundary="001a11c3d97cadcb2304f42f3342"
Archived-At: http://mailarchive.ietf.org/arch/msg/json/6g0FJuICB5F5JQgdlj8qAelOBvQ
X-Mailman-Approved-At: Mon, 10 Mar 2014 00:55:34 -0700
Cc: Barry Leiba <barryleiba@computer.org>, John Cowan <cowan@mercury.ccil.org>, Pete Resnick <presnick@qti.qualcomm.com>, Bjoern Hoehrmann <derhoermi@gmx.net>, Paul Hoffman <paul.hoffman@vpnc.org>, Larry Masinter <masinter@adobe.com>, "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>, "Matt Miller (mamille2)" <mamille2@cisco.com>, "json@ietf.org" <json@ietf.org>, "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: Sun, 09 Mar 2014 16:44:42 -0000

So, all the specifications are now consistent, which is a good thing, but
note the advice in the spec: If you want interoperability, use a list or an
object.  -T


On Sun, Mar 9, 2014 at 9:41 AM, Paul E. Jones <paulej@packetizer.com> wrote:

> Right. That gets us back to the old definition. Writing an array or object
> makes sense, but an integer and then another seems like it just makes
> things unnecessarily confusing. Somewhere, somehow there must be whitespace
> inserted between those.
>
> Paul
>
> ------------------------------
> *From:* John Cowan <cowan@mercury.ccil.org>
> *Sent:* March 9, 2014 10:36:08 AM EDT
> *To:* Larry Masinter <masinter@adobe.com>
> *Cc:* "Paul E. Jones" <paulej@packetizer.com>, "Joe Hildebrand
> (jhildebr)" <jhildebr@cisco.com>, Tim Bray <tbray@textuality.com>, Pete
> Resnick <presnick@qti.qualcomm.com>, Bjoern Hoehrmann <derhoermi@gmx.net>,
> Paul Hoffman <paul.hoffman@vpnc.org>, "json@ietf.org" <json@ietf.org>,
> "Matt Miller (mamille2)" <mamille2@cisco.com>, Barry Leiba <
> barryleiba@computer.org>, "rfc7158@schmorp.de" <rfc7158@schmorp.de>
> *Subject:* Re: [Json] serializing sequences of JSON values
>
> Larry Masinter scripsit:
>
>  If you want to write out a sequence of JSON values you would write them out as an array with [] around and comma separators.
>>
>
> That would be a single JSON value, not a sequence thereof.
>
>

v2.23.0 | Report a Bug | By Email