IETF Logo Mail Archive

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

R S <sayrer@gmail.com> Fri, 07 June 2013 03:54 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 240C021F8DDD for <json@ietfa.amsl.com>; Thu, 6 Jun 2013 20:54:45 -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 0cFUoNADKMw3 for <json@ietfa.amsl.com>; Thu, 6 Jun 2013 20:54:39 -0700 (PDT)
Received: from mail-qa0-x236.google.com (mail-qa0-x236.google.com [IPv6:2607:f8b0:400d:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 65AF11F0D37 for <json@ietf.org>; Thu, 6 Jun 2013 20:54:22 -0700 (PDT)
Received: by mail-qa0-f54.google.com with SMTP id n20so799961qaj.20 for <json@ietf.org>; Thu, 06 Jun 2013 20:54:20 -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=4JN50hZHYTj3YXHazAdPzT4nVZtjgmwJl1Yhf8zq548=; b=WKOHOu3zfGzBVHri7O0cQ5I98hBZd77k5MWrciUg89sMs8Zo7TODq1ubN1PR7gY4TR 2NOA9dNyHfVSUEtuDbk51ML1/81okH06W796NTtzHrJc5BKgU1y4y/ws6+MEs38l0iyY rAVCsYX7CWMJlrBnH5y7qvUW7H0R1tFhjRDkh5DrlpIbfPXp/MXPEwCLeJnYCmpGbs+e yhaYmC0i1Onh/jKJRD5Xrnezjhkl6dz5YmwlFc+ddodYEdIUc6Sg2yZEQe60Tp9hlB7W nhI1bbAJCTQHajwtvYczvk/yJ1jabO0mbDsCFpGFeM5EcWca/0UccOGBI7gQfCjX56a9 +u/Q==
MIME-Version: 1.0
X-Received: by 10.229.69.34 with SMTP id x34mr14481226qci.75.1370577259897; Thu, 06 Jun 2013 20:54:19 -0700 (PDT)
Received: by 10.224.178.1 with HTTP; Thu, 6 Jun 2013 20:54:19 -0700 (PDT)
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E1151B21F9A9@WSMSG3153V.srv.dir.telstra.com>
References: <255B9BB34FB7D647A506DC292726F6E1151B21F9A9@WSMSG3153V.srv.dir.telstra.com>
Date: Thu, 06 Jun 2013 20:54:19 -0700
Message-ID: <CAChr6SyqBm6O2Vuo5Pe3PyUaGoWqOfBxasYCC_vzZ=ya5FT57w@mail.gmail.com>
From: R S <sayrer@gmail.com>
To: "Manger, James H" <James.H.Manger@team.telstra.com>
Content-Type: multipart/alternative; boundary="00032557fa1eb6b34404de8862c3"
Cc: "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 03:54:45 -0000

I support this change. It is required in interoperable implementations.


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:
>
>    A JSON text is a serialized object or array.
>
>    JSON-text = object / array
>
>
> 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
>
>
> ECMAScript already allows this.
> http://www.ecma-international.org/ecma-262/5.1/#sec-15.12
>
>    * The top level JSONText production of the ECMAScript JSON grammar
>      may consist of any JSONValue rather than being restricted to being
>      a JSONObject or a JSONArray as specified by RFC 4627.
>
> --
> James Manger
>
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>

v2.23.0 | Report a Bug | By Email