Re: [Json] I-JSON vs. JSON-S

Bjoern Hoehrmann <derhoermi@gmx.net> Mon, 08 July 2013 15:25 UTC

From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Carsten Bormann <cabo@tzi.org>
Date: Mon, 08 Jul 2013 17:25:25 +0200
Message-ID: <6milt8df307ep0rtfo2pp6ghgsiea25djb@hive.bjoern.hoehrmann.de>
References: <9326419D-73C0-4098-91F0-0E83A7FEA67A@tzi.org>
In-Reply-To: <9326419D-73C0-4098-91F0-0E83A7FEA67A@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Cc: "json@ietf.org WG" <json@ietf.org>
Subject: Re: [Json] I-JSON vs. JSON-S
Precedence: list

* Carsten Bormann wrote:
>When people talk about "not breaking things", it is just not clear
>whether they mean "carry along all usages of JSON-S" or "make sure all
>I-JSON implementations stil interoperate flawlessly".  That's why the
>current charter may have less of a defined meaning than it appears.
>Unless the two levels of interoperability are clearly identified, it
>is not possible to break neither.

http://www.w3.org/TR/2012/WD-XMLHttpRequest-20121206/ proposes that the
XMLHttpRequest implementations parse JSON HTTP responses by way of

  JSON.parse(decode_utf8_with_bom_and_error_recovery(bytes))

That extends and subsets what is defined in RFC 4627. If this is imple-
mented as proposed, and my parser does something else, I may eventually
have to deal with bug reports telling me "but it works with XHR". And I
might have to adapt my parser. Same for many other implementations.

http://www.w3.org/TR/2012/WD-xslt-30-20120710/#func-parse-json proposes
a `parse-json` function that takes option parameters like "RFC4627" and
"ECMA-262" to select among JSON profiles. People seeing this might ask
that my parser also has such options.

We could take RFC4627-JSON, remove unpaired surrogate escapes and dupli-
cate keys and call it RFC7xxx-JSON, but that would make ECMA-JSON and
RFC-JSON more different. RFC4627-JSON with all values at the top level
allowed would make them more similar. It would improve our understanding
of what is JSON.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/

[Json] I-JSON vs. JSON-S Carsten Bormann
Re: [Json] I-JSON vs. JSON-S Bjoern Hoehrmann
Re: [Json] I-JSON vs. JSON-S Nico Williams
Re: [Json] I-JSON vs. JSON-S Nico Williams