Re: [Json] Allow any JSON value at the top level
R S <sayrer@gmail.com> Tue, 11 June 2013 03:06 UTC
Return-Path: <sayrer@gmail.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98C7721E80AE for <json@ietfa.amsl.com>; Mon, 10 Jun 2013 20:06:21 -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=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5-elFd8CTiXQ for <json@ietfa.amsl.com>; Mon, 10 Jun 2013 20:06:20 -0700 (PDT)
Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) by ietfa.amsl.com (Postfix) with ESMTP id 7244621E80AD for <json@ietf.org>; Mon, 10 Jun 2013 20:06:20 -0700 (PDT)
Received: by mail-wg0-f52.google.com with SMTP id z12so4829601wgg.19 for <json@ietf.org>; Mon, 10 Jun 2013 20:06:18 -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=J963Po/3Mg56F4opOXGxodlizGkxpEbFbk46QmZp3cI=; b=JEVaBQgWGLQvmJ6xrHrlC8G2nfj9p/QyOv3MStTBJQ6sKU9oc5DXEMTcz2OzY5l41h hAoRmCXWP4QFLfnaFhbBXJzHt5ObDvgc7DE3hlSevfBzKwpo5dR0PviET4oRw7DPXmo0 R7yl0kHSVjTLE65OcE3gFaA3QHdwwDmX8gJDwHP0+xqb7sGlWt7Y1pQbhXW0NBVQWHfL jknrnhUK7meJxXUz85jbSfH1Aixx+dPerHi0Aa8rBZ+GncP3fuRE+j8tpOtohaOxEDvK mt2V1BVbz4DjbiThkxllT2TPwVI8ooPV9FS/VEKBE3Epl0ovkHUbWqZZ4eOBHu+/NapI kUdQ==
MIME-Version: 1.0
X-Received: by 10.194.63.229 with SMTP id j5mr6991585wjs.79.1370919978327; Mon, 10 Jun 2013 20:06:18 -0700 (PDT)
Received: by 10.194.83.35 with HTTP; Mon, 10 Jun 2013 20:06:18 -0700 (PDT)
In-Reply-To: <CAHBU6isx8PCMGk9XAP-WZszn79c2hDPk78=7r9L4T2oTzPU7MA@mail.gmail.com>
References: <A723FC6ECC552A4D8C8249D9E07425A70FC33B5B@xmb-rcd-x10.cisco.com> <51b23e6d.6196420a.0b15.4245SMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SwrveU=fesF8VidDYWzeYMu2c1+=38+__BqHArxTiW5mg@mail.gmail.com> <51b4dbbe.64da440a.1fc2.6dd2SMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6Sx_obmG+=sY100ySBLmevN0VJ_0Z9TjYGxcXKOx+UtnJA@mail.gmail.com> <51b4ec44.ea05420a.7c73.ffffa487SMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxiZ2Yz6SiozQZpuYoGKSzWnUux6PukyWDkcvKsVyyRbQ@mail.gmail.com> <51b507b1.c686e00a.3a7e.ffffa0adSMTPIN_ADDED_BROKEN@mx.google.com> <CAO1wJ5R2H27qh-DWG5B8CzutkTFWxn-h+Qi1jiet23axxmvLyA@mail.gmail.com> <20130610201746.GC1057@mercury.ccil.org> <CAO1wJ5Q9mhspheU3h4NRx9x5LOz9yOgJBXhwPWBOVw-w71ncTQ@mail.gmail.com> <3CE20E15-8F9E-4727-BBE7-FBB06F7CAC24@jorgechamorro.com> <CAGrxA24T8m9oHmuVE8n+YG6ATr3sTTByet7Te8VyAmypD11p6w@mail.gmail.com> <B14769F1-5C71-4F1D-8E20-513271876620@vpnc.org> <CAChr6SzXUNTA+bMtFAwWh+Z2APoiSuAt7DQzx+RK57+vznN1-w@mail.gmail.com> <CAHBU6isx8PCMGk9XAP-WZszn79c2hDPk78=7r9L4T2oTzPU7MA@mail.gmail.com>
Date: Mon, 10 Jun 2013 20:06:18 -0700
Message-ID: <CAChr6Swi5UjTnggXF88qrVQ8Wg-kGfKfEQN-3+2BwoEZw5TvVA@mail.gmail.com>
From: R S <sayrer@gmail.com>
To: Tim Bray <tbray@textuality.com>
Content-Type: multipart/alternative; boundary="047d7ba97518532c3604ded82e8f"
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Allow any JSON value at the top level
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 11 Jun 2013 03:06:21 -0000
On Mon, Jun 10, 2013 at 7:43 PM, Tim Bray <tbray@textuality.com> wrote: > Rob, just to make sure I understand, you’re saying that because ECMA > doesn’t impose the 4627 restriction that a top-level object has to be a > composite, 4627bis has to be changed to acknowledge that? -T > I think the charter obligates the WG to document the difference. Whether that takes the form of a normative requirement is another matter. On a practical level, I'm not sure what the value of an informational section rather than a requirement would be. It would be great if someone could give a rationale for that. I think there's value in having the Standards-Track RFC be an accurate description of requirements for interoperability. What good does it do us to have a non-normative section that is actually required to interoperate with browsers and most other implementations? Speaking as someone that updated a widely-used implementation to support primitive root values, - Rob > > On Mon, Jun 10, 2013 at 5:18 PM, R S <sayrer@gmail.com> wrote: > >> On Mon, Jun 10, 2013 at 4:56 PM, Paul Hoffman <paul.hoffman@vpnc.org>wrote: >> >>> <no hat> >>> >>> Although I earlier supported the idea of any JSON value at the top >>> level, a bunch of recent posts show that this is probably a significant >>> revision to the RFC because it would take a lot of extra requirements as >>> well. I now support leaving the requirement in the -bis document as it is >>> now. >>> >> >> Leaving the document as-is does not seem to be an option per the charter: >> >> "It is acknowledged that there are differences between RFC 4627 and the >> ECMAScript specification in the rules for parsing JSON. Any changes that >> break compatibility with existing implementations of either RFC 4627 or >> the ECMAScript specification will need to have very strong justification >> and broad support. All differences between RFC 4627 or the current >> ECMAScript specification will be documented in the new RFC." >> >> >> >>> If we want to add a new MIME type for "any JSON item", that is clearly a >>> significant addition to the RFC. It can wait until the WG recharters. >> >> >> A new media type would solve any problem that I'm aware of. >> >> - Rob >> >> _______________________________________________ >> json mailing list >> json@ietf.org >> https://www.ietf.org/mailman/listinfo/json >> >> >
- Re: [Json] Allow any JSON value at the top level Joe Hildebrand (jhildebr)
- [Json] Allow any JSON value at the top level Manger, James H
- Re: [Json] Allow any JSON value at the top level R S
- Re: [Json] Allow any JSON value at the top level Stefan Drees
- Re: [Json] Allow any JSON value at the top level Stefan Drees
- Re: [Json] Allow any JSON value at the top level Manger, James H
- Re: [Json] Allow any JSON value at the top level Manger, James H
- Re: [Json] Allow any JSON value at the top level … Pete Cordell
- Re: [Json] Allow any JSON value at the top level … Stefan Drees
- Re: [Json] Allow any JSON value at the top level Carsten Bormann
- Re: [Json] Allow any JSON value at the top level Markus Lanthaler
- Re: [Json] Allow any JSON value at the top level Stephan Beal
- Re: [Json] Allow any JSON value at the top level Vinny A
- Re: [Json] Allow any JSON value at the top level Paul Hoffman
- Re: [Json] Allow any JSON value at the top level Tim Bray
- Re: [Json] Allow any JSON value at the top level Stefan Drees
- Re: [Json] Allow any JSON value at the top level Matt Miller (mamille2)
- Re: [Json] Allow any JSON value at the top level John Cowan
- Re: [Json] Allow any JSON value at the top level R S
- Re: [Json] Allow any JSON value at the top level Nico Williams
- Re: [Json] Allow any JSON value at the top level Joe Hildebrand (jhildebr)
- Re: [Json] Allow any JSON value at the top level Jacob Davies
- Re: [Json] Allow any JSON value at the top level Tatu Saloranta
- Re: [Json] Allow any JSON value at the top level Tatu Saloranta
- Re: [Json] Allow any JSON value at the top level Markus Lanthaler
- Re: [Json] Allow any JSON value at the top level Nico Williams
- Re: [Json] Allow any JSON value at the top level Nico Williams
- Re: [Json] Allow any JSON value at the top level Jorge
- Re: [Json] Allow any JSON value at the top level R S
- Re: [Json] Allow any JSON value at the top level Carsten Bormann
- Re: [Json] Allow any JSON value at the top level Martin J. Dürst
- Re: [Json] Allow any JSON value at the top level John Cowan
- Re: [Json] Allow any JSON value at the top level Jorge
- Re: [Json] Allow any JSON value at the top level Manger, James H
- Re: [Json] Allow any JSON value at the top level Markus Lanthaler
- Re: [Json] Allow any JSON value at the top level R S
- Re: [Json] Allow any JSON value at the top level Markus Lanthaler
- Re: [Json] Allow any JSON value at the top level Nico Williams
- Re: [Json] Allow any JSON value at the top level Jorge
- Re: [Json] Allow any JSON value at the top level Markus Lanthaler
- Re: [Json] Allow any JSON value at the top level Jacob Davies
- Re: [Json] Allow any JSON value at the top level John Cowan
- Re: [Json] Allow any JSON value at the top level Jacob Davies
- Re: [Json] Allow any JSON value at the top level Nico Williams
- Re: [Json] Allow any JSON value at the top level John Cowan
- Re: [Json] Allow any JSON value at the top level Jorge
- Re: [Json] Allow any JSON value at the top level Nico Williams
- Re: [Json] Allow any JSON value at the top level Tatu Saloranta
- Re: [Json] Allow any JSON value at the top level Paul Hoffman
- Re: [Json] Allow any JSON value at the top level R S
- Re: [Json] Allow any JSON value at the top level Nico Williams
- Re: [Json] Allow any JSON value at the top level Paul Hoffman
- Re: [Json] Allow any JSON value at the top level John Cowan
- Re: [Json] Allow any JSON value at the top level Tim Bray
- Re: [Json] Allow any JSON value at the top level Paul Hoffman
- Re: [Json] Allow any JSON value at the top level R S
- Re: [Json] Allow any JSON value at the top level Carsten Bormann
- Re: [Json] Allow any JSON value at the top level Manger, James H
- Re: [Json] Allow any JSON value at the top level R S
- Re: [Json] Allow any JSON value at the top level R S
- Re: [Json] Allow any JSON value at the top level Markus Lanthaler
- Re: [Json] Allow any JSON value at the top level Tatu Saloranta
- Re: [Json] Allow any JSON value at the top level Tatu Saloranta
- Re: [Json] Allow any JSON value at the top level John Cowan
- Re: [Json] Allow any JSON value at the top level Carsten Bormann
- Re: [Json] Allow any JSON value at the top level Martin J. Dürst