Re: [Json] Allow any JSON value at the top level
"Matt Miller (mamille2)" <mamille2@cisco.com> Fri, 07 June 2013 16:22 UTC
Return-Path: <mamille2@cisco.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 5410921F8EBC for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 09:22:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 VWUFt0ygpFJN for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 09:22:19 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 3CF0421F8717 for <json@ietf.org>; Fri, 7 Jun 2013 09:22:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7166; q=dns/txt; s=iport; t=1370622139; x=1371831739; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=RYHWaj3DDZP8QhotP6N3ZzPfcbfHpBCuM+VNdv6yS2Y=; b=QbIcIAsUnBgOIZSUt6I3qEBZZ0uJ+BOPuDFpt8vEuaKJxNT0SEdocQ1A sygRBTOfDqV9fKI11mBKxczpxQ/qEl01KXvIQPA66mKlSDPu6rnewzc6r p+IQlgvm1Pjeq5WDSEs8EAkwEqxG1nHYNeGI9LIbFFenAIXTBtOvOCgFx 4=;
X-Files: smime.p7s : 4136
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhEFAMgHslGtJV2Z/2dsb2JhbABZgwm/IH8WdIIjAQEBBHkFCwIBCA4KCiQCMCUBAQQOBQgGh20DD7QoHYhCjwcxB4J7YQOQAYEsgkGVFIMPgic
X-IronPort-AV: E=Sophos; i="4.87,823,1363132800"; d="p7s'?scan'208"; a="220114306"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-5.cisco.com with ESMTP; 07 Jun 2013 16:22:18 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r57GMIMC030461 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 7 Jun 2013 16:22:18 GMT
Received: from xmb-aln-x11.cisco.com ([169.254.6.24]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.02.0318.004; Fri, 7 Jun 2013 11:22:18 -0500
From: "Matt Miller (mamille2)" <mamille2@cisco.com>
To: Tim Bray <tbray@textuality.com>
Thread-Topic: [Json] Allow any JSON value at the top level
Thread-Index: Ac5jMj7wK5i9s5prS+2npykXIGILbgAj1hwAAADfq4A=
Date: Fri, 07 Jun 2013 16:22:17 +0000
Message-ID: <BF7E36B9C495A6468E8EC573603ED9411527FBCE@xmb-aln-x11.cisco.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B21F9A9@WSMSG3153V.srv.dir.telstra.com> <CAHBU6isXinTGstEDtagsvTufaQDQ=W1K06sn5EFSAzkNuQrZAg@mail.gmail.com>
In-Reply-To: <CAHBU6isXinTGstEDtagsvTufaQDQ=W1K06sn5EFSAzkNuQrZAg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.129.24.59]
Content-Type: multipart/signed; boundary="Apple-Mail=_B52A1494-2A27-4DDF-BADF-B6FA25B54C98"; protocol="application/pkcs7-signature"; micalg="sha1"
MIME-Version: 1.0
Cc: "Manger, James H" <James.H.Manger@team.telstra.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:22:40 -0000
On Jun 7, 2013, at 9:57 AM, Tim Bray <tbray@textuality.com> wrote: > On Thu, Jun 6, 2013 at 8:51 PM, Manger, James H < > James.H.Manger@team.telstra.com> wrote: > >> The current spec only allows a JSON text to be an object or array. Section >> 2. "JSON Grammar" says: >> > ... > >> I propose allowing a JSON text to be any JSON value. >> > > -1. > > 1. Our mandate is not to enhance or improve JSON. > 2. This is a bad idea in general and a terrible idea for network protocols, > which is where JSON is most valuable. > > -T > > /me doffs hat 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. However, I don't know that with any degree of certainty. - m&m Matt Miller < mamille2@cisco.com > Cisco Systems, Inc.
- 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