[Json] Radically changing 4627bis

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 09 October 2013 20:26 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 D022121E81B9 for <json@ietfa.amsl.com>; Wed, 9 Oct 2013 13:26:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 CVR6otoGzyaT for <json@ietfa.amsl.com>; Wed, 9 Oct 2013 13:26:26 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 25DFB21E81B6 for <json@ietf.org>; Wed, 9 Oct 2013 13:26:25 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-185.dsl.dynamic.sonic.net [50.1.98.185]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id r99KQNd8034768 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 9 Oct 2013 13:26:24 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-185.dsl.dynamic.sonic.net [50.1.98.185] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E11531C3C187@WSMSG3153V.srv.dir.telstra.com>
Date: Wed, 9 Oct 2013 13:26:23 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E2C3B3A8-3897-44B4-8C9B-A784F63EED59@vpnc.org>
References: <20131008234810.28645.8207.idtracker@ietfa.amsl.com> <CAHBU6isT8yv4-xf+cL0-RCdNu6DB=6G97MSaR7Z=F-Fz11BM3w@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E11531C3C187@WSMSG3153V.srv.dir.telstra.com>
To: "Manger, James H" <james.h.manger@team.telstra.com>
X-Mailer: Apple Mail (2.1510)
Cc: json@ietf.org
Subject: [Json] Radically changing 4627bis
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 20:26:27 -0000

<no hat>

On Oct 8, 2013, at 5:38 PM, "Manger, James H" <james.h.manger@team.telstra.com> wrote:

> 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.

A strong -1 on ripping out our syntax and pointing to ECMA-404. Our syntax matches their syntax, so there is not a conflict issue. ECMA-404 was supposed to be syntax-only, but they included semantics about Unicode (characters vs. code points) that were important enough to this WG to generate hundreds of messages on our mailing list. If we point to ECMA-404 for the syntax only, and add in our semantics on interoperability, there will then be a conflict that will have a negative effect on developers who are trying to create interoperable implementations.

--Paul Hoffman