Re: [Json] Regarding JSON text sequence ambiguities (Re: serializing sequences of JSON values)
"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Wed, 12 March 2014 09:45 UTC
Return-Path: <duerst@it.aoyama.ac.jp>
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 64C2F1A093B for <json@ietfa.amsl.com>; Wed, 12 Mar 2014 02:45:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.362
X-Spam-Level:
X-Spam-Status: No, score=0.362 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.547] 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 EgnuvgLZAJDu for <json@ietfa.amsl.com>; Wed, 12 Mar 2014 02:44:57 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id 6DAE91A093F for <json@ietf.org>; Wed, 12 Mar 2014 02:44:57 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id s2C9igKx013828; Wed, 12 Mar 2014 18:44:42 +0900
Received: from (unknown [133.2.206.134]) by scmse02.scbb.aoyama.ac.jp with smtp id 2812_70b7_efdb21fa_a9ca_11e3_85a3_001e6722eec2; Wed, 12 Mar 2014 18:44:41 +0900
Received: from [IPv6:::1] (unknown [133.2.210.1]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id 93183C048C; Wed, 12 Mar 2014 18:44:41 +0900 (JST)
Message-ID: <53202C80.1070204@it.aoyama.ac.jp>
Date: Wed, 12 Mar 2014 18:44:32 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>, Nico Williams <nico@cryptonector.com>
References: <CAK3OfOj_XQJq-JKAjNdH-GuH0_UwZfeWntgyyizMpTLmSaWQoA@mail.gmail.com> <CAK3OfOio58+1yuxQOcvWep1CADMfE1PVC48XDid0dWvd8=SVjA@mail.gmail.com> <CAOXDeqoYb=NXz4ikMxAg3EHFA+903bFgdpR_BL-K18U2oYriXQ@mail.gmail.com> <CAK3OfOiPDfWpOZgExTmwwq6WFcuVbyi_z3C0=M9RhQveBhV_+w@mail.gmail.com> <CAHBU6iuRyRd95Wa_omGS1_T52t+s0AKjWPUW21EAh2ySHuFp=A@mail.gmail.com> <CAMm+LwjRA8x0=zXGRVDy0BqYvyOcEp7=gnUiG4vYOb1RScoyrA@mail.gmail.com> <CAK3OfOj1g_sbnhw9FBCCZtLWsFS5F+aoPX0d5AMkRxQ2fHQi0A@mail.gmail.com> <CAMm+LwhGbo2twsvhPy2Dde+y8shDcm=ysxL_XtRT53oiC8g7ug@mail.gmail.com>
In-Reply-To: <CAMm+LwhGbo2twsvhPy2Dde+y8shDcm=ysxL_XtRT53oiC8g7ug@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/json/t3uvvqUZKNeIuGDqY9SudljwYDM
Cc: Tim Bray <tbray@textuality.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Regarding JSON text sequence ambiguities (Re: 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: Wed, 12 Mar 2014 09:45:01 -0000
On 2014/03/12 04:19, Phillip Hallam-Baker wrote: > On Tue, Mar 11, 2014 at 2:08 PM, Nico Williams <nico@cryptonector.com>wrote: >> JSON text sequences would be a new Proposed Standard (if we go there) >> but like JSON, there exist uses of this "new" thing already -- that >> is, before we get to writing the RFC. > I think finding a standard JSON way to meet this requirement is > appropriate. Blessing a particular approach that isn't in the existing > grammar is not AFIK. For the record, I strongly agree. Seeing claims that we need a separate spec just because an initial '[', interleaving ','s, and a potential(1) final ']' is too much to deal with really surprises me. At the utmost, this might become an Informational RFC if some people really, really want it, but it should NOT become a working item of this group, nor should it go to standards track. Why? JSON is great, but the more variation we get, the more we end up with a *big mess*, even if every step may be small and look good. As far as I have heard (no first hand experience, fortunately), CORBA ended up that way. Many people, in particular in the JSON community, see XML that way. Similar things have been said about ASN-1, although that may have been complicated from the start (again, fortunately no first hand experience). Maybe JSON is just next in line. Regards, Martin. (1) When you write out a log, there's no need to actually write the final ']' and then replace it by a ','. XMPP did something very similar for XML streaming, please see http://tools.ietf.org/html/rfc6120#section-4. In JSON, it's slightly trickier because you need an explicit separating comma, and a 'dummy' element before the closing ']', but that's not rocket science and well worth the effort to avoid format splits.
- [Json] Regarding JSON text sequence ambiguities (… Nico Williams
- Re: [Json] Regarding JSON text sequence ambiguiti… Nico Williams
- Re: [Json] Regarding JSON text sequence ambiguiti… John Cowan
- Re: [Json] Regarding JSON text sequence ambiguiti… Nico Williams
- Re: [Json] Regarding JSON text sequence ambiguiti… John Cowan
- Re: [Json] Regarding JSON text sequence ambiguiti… Tatu Saloranta
- Re: [Json] Regarding JSON text sequence ambiguiti… Matthew Morley
- Re: [Json] Regarding JSON text sequence ambiguiti… Nico Williams
- Re: [Json] Regarding JSON text sequence ambiguiti… Tim Bray
- Re: [Json] Regarding JSON text sequence ambiguiti… Phillip Hallam-Baker
- Re: [Json] Regarding JSON text sequence ambiguiti… Nico Williams
- Re: [Json] Regarding JSON text sequence ambiguiti… Nico Williams
- Re: [Json] Regarding JSON text sequence ambiguiti… Matthew Morley
- Re: [Json] Regarding JSON text sequence ambiguiti… Tim Bray
- Re: [Json] Regarding JSON text sequence ambiguiti… Nico Williams
- Re: [Json] Regarding JSON text sequence ambiguiti… Phillip Hallam-Baker
- Re: [Json] Regarding JSON text sequence ambiguiti… Nico Williams
- Re: [Json] Regarding JSON text sequence ambiguiti… Martin J. Dürst
- Re: [Json] Regarding JSON text sequence ambiguiti… Phillip Hallam-Baker
- Re: [Json] Regarding JSON text sequence ambiguiti… Larry Masinter
- Re: [Json] Regarding JSON text sequence ambiguiti… Tim Bray
- Re: [Json] Regarding JSON text sequence ambiguiti… Larry Masinter
- Re: [Json] Regarding JSON text sequence ambiguiti… Tim Bray
- Re: [Json] Regarding JSON text sequence ambiguiti… Nico Williams
- Re: [Json] Regarding JSON text sequence ambiguiti… Manger, James
- Re: [Json] Regarding JSON text sequence ambiguiti… Bjoern Hoehrmann
- Re: [Json] Regarding JSON text sequence ambiguiti… Manger, James
- Re: [Json] Regarding JSON text sequence ambiguiti… Nico Williams
- Re: [Json] Regarding JSON text sequence ambiguiti… Martin J. Dürst
- Re: [Json] Regarding JSON text sequence ambiguiti… John Cowan
- Re: [Json] Regarding JSON text sequence ambiguiti… Martin J. Dürst
- Re: [Json] Regarding JSON text sequence ambiguiti… Nico Williams