Re: [Json] I-D Action: draft-ietf-json-rfc4627bis-05.txt

"Manger, James H" <James.H.Manger@team.telstra.com> Wed, 09 October 2013 00:39 UTC

Return-Path: <James.H.Manger@team.telstra.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 C26AE21F9FA4 for <json@ietfa.amsl.com>; Tue, 8 Oct 2013 17:39:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.518
X-Spam-Level:
X-Spam-Status: No, score=-0.518 tagged_above=-999 required=5 tests=[AWL=0.383, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
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 n4m5khzu9Vlm for <json@ietfa.amsl.com>; Tue, 8 Oct 2013 17:39:04 -0700 (PDT)
Received: from ipxbvo.tcif.telstra.com.au (ipxbvo.tcif.telstra.com.au [203.35.135.204]) by ietfa.amsl.com (Postfix) with ESMTP id 1CB0221F9F34 for <json@ietf.org>; Tue, 8 Oct 2013 17:38:54 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.90,1059,1371045600"; d="scan'208";a="164817951"
Received: from unknown (HELO ipcavi.tcif.telstra.com.au) ([10.97.217.200]) by ipobvi.tcif.telstra.com.au with ESMTP; 09 Oct 2013 11:38:54 +1100
X-IronPort-AV: E=McAfee;i="5400,1158,7222"; a="220642745"
Received: from wsmsg3756.srv.dir.telstra.com ([172.49.40.84]) by ipcavi.tcif.telstra.com.au with ESMTP; 09 Oct 2013 11:38:54 +1100
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by wsmsg3756.srv.dir.telstra.com ([172.49.40.84]) with mapi; Wed, 9 Oct 2013 11:38:53 +1100
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Tim Bray <tbray@textuality.com>, "json@ietf.org" <json@ietf.org>
Date: Wed, 9 Oct 2013 11:38:52 +1100
Thread-Topic: [Json] I-D Action: draft-ietf-json-rfc4627bis-05.txt
Thread-Index: Ac7EgSg0lXyjIjGyRYShoQEaDZApTAAARwNA
Message-ID: <255B9BB34FB7D647A506DC292726F6E11531C3C187@WSMSG3153V.srv.dir.telstra.com>
References: <20131008234810.28645.8207.idtracker@ietfa.amsl.com> <CAHBU6isT8yv4-xf+cL0-RCdNu6DB=6G97MSaR7Z=F-Fz11BM3w@mail.gmail.com>
In-Reply-To: <CAHBU6isT8yv4-xf+cL0-RCdNu6DB=6G97MSaR7Z=F-Fz11BM3w@mail.gmail.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [Json] I-D Action: draft-ietf-json-rfc4627bis-05.txt
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, 09 Oct 2013 00:39:09 -0000

> Real HTML at https://www.tbray.org/tmp/draft-ietf-json-rfc4627bis-05.html

Editorial:
 “for example, "Hello world!", "42", and "true" would all be valid JSON texts in the ECMAScript 5.1 context.”

This is not quite precise as the double-quotes are part of the JSON text for the string example, but not for the number and Boolean examples. Perhaps say:
 
  for example, each of the following 3 lines would be a valid JSON text
  in the ECMAScript 5.1 context:
 
  "Hello world!"
  42
  true 



But the publication of ECMA-404 means we should radically change 4627bis.
Lets do what ECMA-404 "Introduction" suggests other standards do:

  It is expected that other standards will refer to this one, strictly
  adhering to the JSON text format, while imposing restrictions on various
  encoding details. Such standards may require specific behaviours. JSON 
  itself specifies no behaviour. 

Lets reference ECMA-404 -- not repeating any of the syntax.
Define the media type.
Discuss the interop issues with surrogates, huge integers, decimal floats, duplicate names, comments, encodings.
Perhaps define terms such as "web-safe JSON" (for a subset of JSON) and "web-safe JSON parser" (for specific parser behaviour) that other specs using JSON can refer to.

I guess this is close to Tim’s "Internet JSON" or "I-JSON" proposal.
It is time to drop the minimal 4627 update.

--
James Manger