IETF Logo Mail Archive

Re: [Json] Allow any JSON value at the top level

"Markus Lanthaler" <markus.lanthaler@gmx.net> Fri, 07 June 2013 20:11 UTC

Return-Path: <markus.lanthaler@gmx.net>
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 759AC21F998C for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 13:11:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.15
X-Spam-Level:
X-Spam-Status: No, score=-1.15 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449]
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 B9RoehaHXROh for <json@ietfa.amsl.com>; Fri, 7 Jun 2013 13:11:16 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) by ietfa.amsl.com (Postfix) with ESMTP id 985D621F9992 for <json@ietf.org>; Fri, 7 Jun 2013 13:11:14 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.10]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0MEHXK-1UZzJZ345A-00FSDD for <json@ietf.org>; Fri, 07 Jun 2013 22:11:13 +0200
Received: (qmail invoked by alias); 07 Jun 2013 20:11:13 -0000
Received: from 84-115-182-43.dynamic.surfer.at (EHLO Vostro3500) [84.115.182.43] by mail.gmx.net (mp010) with SMTP; 07 Jun 2013 22:11:13 +0200
X-Authenticated: #419883
X-Provags-ID: V01U2FsdGVkX182gct+dH42RerTnqNAGtl5SuFe8IO+Jm8raWdI0y /5T/DPMRm5HsxT
From: Markus Lanthaler <markus.lanthaler@gmx.net>
To: json@ietf.org
References: <00d601ce6360$52acce30$f8066a90$@lanthaler@gmx.net> <A723FC6ECC552A4D8C8249D9E07425A70FC33B5B@xmb-rcd-x10.cisco.com>
In-Reply-To: <A723FC6ECC552A4D8C8249D9E07425A70FC33B5B@xmb-rcd-x10.cisco.com>
Date: Fri, 07 Jun 2013 22:11:06 +0200
Message-ID: <031a01ce63bb$25218130$6f648390$@lanthaler>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac5jMj7wK5i9s5prS+2npykXIGILbgALg8dAAA49wAAACFzgIA==
Content-Language: de
X-Y-GMX-Trusted: 0
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 20:11:22 -0000

On Friday, June 07, 2013 7:09 PM, Joe Hildebrand (jhildebr) wrote:
> On 6/7/13 3:20 AM, "Markus Lanthaler" <markus.lanthaler@gmx.net> wrote:
> 
> >On Friday, June 07, 2013 5:51 AM, Manger, James H wrote:
> >> I propose allowing a JSON text to be any JSON value.
> >>
> >>    A JSON text is a serialization of any JSON value.
> >>
> >>    JSON-text = value
> >>
> >>    value = false / null / true / object / array / number / string
> >
> >I'm strictly against this. Not only would it break many
> implementations but also specs build on top of JSON that rely on
> JSON-text = object / array.
> 
> What about a new production in parallel to JSON-text, like 'JSON-
> document'?

And how is that production used? A "JSON document", i.e., a representation
labeled as application/json must be an array or an object at the top-level.
If you want something else, then it's clearly out of scope for this WG IMO.
You can of course write another RFC standardizing JSON+ :-P



--
Markus Lanthaler
@markuslanthaler

v2.23.0 | Report a Bug | By Email