Re: [Json] section 1 paragraph 2 on what JSON can represent

Tony Hansen <tony@att.com> Wed, 02 October 2013 19:50 UTC

Return-Path: <tony@att.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 BFB9521F9E99 for <json@ietfa.amsl.com>; Wed, 2 Oct 2013 12:50:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.099
X-Spam-Level:
X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 SRce-YFy25F4 for <json@ietfa.amsl.com>; Wed, 2 Oct 2013 12:49:55 -0700 (PDT)
Received: from tlpi046.enaf.dadc.sbc.com (egssmtp01.att.com [144.160.112.12]) by ietfa.amsl.com (Postfix) with ESMTP id D561621F9DF7 for <json@ietf.org>; Wed, 2 Oct 2013 12:40:36 -0700 (PDT)
Received: from mailgw1.maillennium.att.com (maillennium.att.com [135.25.114.99]) by egssmtp01.att.com (8.14.4/8.14.4) with ESMTP id r92JeXWs030895 for <json@ietf.org>; Wed, 2 Oct 2013 14:40:36 -0500
Received: from [135.91.110.247] (ds135-91-110-247.dhcps.ugn.att.com[135.91.110.247]) by maillennium.att.com (mailgw1) with ESMTP id <20131002194032gw1009k125e> (Authid: tony); Wed, 2 Oct 2013 19:40:33 +0000
X-Originating-IP: [135.91.110.247]
Message-ID: <524C76B0.9040900@att.com>
Date: Wed, 02 Oct 2013 15:40:32 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: JSON WG <json@ietf.org>
References: <BF7E36B9C495A6468E8EC573603ED9411EF1BB0B@xmb-aln-x11.cisco.com> <CAChr6SyznBktmOLpT-EiZ5Nm_0jZ16M0tOo4aZ_jhSDb=HHDqg@mail.gmail.com> <23C96FBA-3419-4C97-A075-462F7443013A@vpnc.org> <CAHBU6is2WzCNCwa0PYMM1Hr3Lij0GxWkVtVUan9=JPbvv0YCZg@mail.gmail.com> <CAChr6Sw72kxm8qJiDu=XMnARCttQPc5GNRQaXz4Xw9y+6-3=Mg@mail.gmail.com> <421F79DF-0B88-4E24-8666-189228E6E189@vpnc.org> <524C73B7.1060104@att.com>
In-Reply-To: <524C73B7.1060104@att.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [Json] section 1 paragraph 2 on what JSON can represent
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: Wed, 02 Oct 2013 19:50:07 -0000

The text in section 1 paragraph 2 on what JSON can represent is not
really accurate. I know that this text was in the original 4627 and is
unchanged from there. However, this is really one of the areas where
4627-JSON and ECMA-JSON differ, and is incorrect for 4627-JSON. This
text currently reads:

   JSON can represent four primitive types (strings, numbers, booleans,
   and null) and two structured types (objects and arrays).

In 4627-JSON, Section 2 says that JSON-text is an object / array.
In ECMA-JSON, Section 15.2 says that JSONtext is an object / array /
string / number / boolean-literal / null-literal.

4627-JSON cannot truly represent one of the four primitive types, except
when it has been encapsulated within an object or array. However,
ECMA-JSON can represent any of the four primitive types or two
structured types.

Since we've as a WG rejected extending 4627-JSON to be compatible with
ECMA-JSON, a better statement for 4627bis would be something like this:

   JSON can represent two structured types (objects and arrays) that are
created from
   four primitive types (strings, numbers, booleans, and null) and
recursive objects and
   arrays.

- Tony Hansen