Re: [Json] Allow any JSON value at the top level
R S <sayrer@gmail.com> Fri, 07 June 2013 16:51 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 3D57621F9926 for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 09:51:02 -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=[AWL=0.000, 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 MlV24japGhNF for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 09:51:01 -0700 (PDT)
Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 9F62F21F8613 for <json@ietf.org>; Fri, 7 Jun 2013 09:51:00 -0700 (PDT)
Received: by mail-we0-f169.google.com with SMTP id n57so3318373wev.0 for <json@ietf.org>; Fri, 07 Jun 2013 09:50:59 -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=9AbNaHW6Jpt2kLrOf00ks5TvErW0hnP9uiSwtD2V/Ek=; b=GSwmRIDDOKf4Ec6XS3k/YjgP7zdQy10PuTqM71HzfNEDYHi5Ri+09HiZ+D698H2ePe AW8hcvhzZw4wRnORFayBBVY16ciMxJQreOiDW90UdTPF53B7/QspJ+M7DH5YpsT89lMz +l1gJjPtAJyz6Qzn6PwND+jvVEHblenWW0fCmf625Bb9EQM0YEtMRF6cfHW1O8jkOLm+ Ws+KuUlJJFY86E6dboqq2UpzbkQtfSgVz+ONHuF7+CPeUYNTGce1lHN3ZI5QQN8IdAt2 rc08L+yWdWZMOVFYMnfQI2O6AV+/BgHPUPV9ky3y7y8aAJ8OuBR3KX6BNrZlcGWV1I29 TkYg==
MIME-Version: 1.0
X-Received: by 10.194.63.229 with SMTP id j5mr4767105wjs.79.1370623859652; Fri, 07 Jun 2013 09:50:59 -0700 (PDT)
Received: by 10.194.83.35 with HTTP; Fri, 7 Jun 2013 09:50:59 -0700 (PDT)
In-Reply-To: <BF7E36B9C495A6468E8EC573603ED9411527FBCE@xmb-aln-x11.cisco.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B21F9A9@WSMSG3153V.srv.dir.telstra.com> <CAHBU6isXinTGstEDtagsvTufaQDQ=W1K06sn5EFSAzkNuQrZAg@mail.gmail.com> <BF7E36B9C495A6468E8EC573603ED9411527FBCE@xmb-aln-x11.cisco.com>
Date: Fri, 07 Jun 2013 09:50:59 -0700
Message-ID: <CAChr6Szm9aw45htqLHzkhcE_upC4Vwy4WKfCAQErhBxXf+-8bw@mail.gmail.com>
From: R S <sayrer@gmail.com>
To: "Matt Miller (mamille2)" <mamille2@cisco.com>
Content-Type: multipart/alternative; boundary="047d7ba9751846802704de933cf4"
Cc: "Manger, James H" <James.H.Manger@team.telstra.com>, Tim Bray <tbray@textuality.com>, "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: Fri, 07 Jun 2013 16:51:02 -0000
On Fri, Jun 7, 2013 at 9:22 AM, Matt Miller (mamille2) <mamille2@cisco.com>wrote: > > This is one area where I think we need experimentation before we can > consider such as change. It very well could be that "everyone" (for some > definition of everyone) has ignored this particular restriction in order to > maximize compatibility with ECMAScript, in which case maintaining this > condition means everyone is technically non-compliant. > RFC 4627 says "A JSON parser MAY accept non-JSON forms or extensions." and implementations that are compatible with ECMAScript are common enough that it seems this extension to RFC 4627 actually doesn't cause problems with applications expecting only arrays or objects at the root. Does anyone have examples of this behavior creating problems in the wild? They must be out there, since support for this extension is so common. - Rob
- 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