W3C home > Mailing lists > Public > www-tag@w3.org > November 2013

Re: [Json] JSON: remove gap between Ecma-404 and IETF draft

From: Joe Hildebrand (jhildebr) <jhildebr@cisco.com>
Date: Wed, 13 Nov 2013 23:51:44 +0000
To: John Cowan <cowan@mercury.ccil.org>
CC: Paul Hoffman <paul.hoffman@vpnc.org>, Anne van Kesteren <annevk@annevk.nl>, es-discuss <es-discuss@mozilla.org>, IETF Discussion <ietf@ietf.org>, "www-tag@w3.org" <www-tag@w3.org>, JSON WG <json@ietf.org>
Message-ID: <CEA95C60.2CF3C%jhildebr@cisco.com>
On 11/13/13 3:47 PM, "John Cowan" <cowan@mercury.ccil.org> wrote:

>It's not clear that 404 disallows it, since 404 is defined in terms of
>characters, and a BOM is not a character but an out-of-band signal.

Agree.  However, that signal would be a part of the 4627bis octet stream,
so a little interop guidance would likely be useful.  Something like:

"Some producers of JSON produce JSON-text that starts with a redundant
U+FEFF (ZERO WIDTH NO-BREAK SPACE, previously known as BYTE ORDER MARK)
with the ostensible purpose of signaling the encoding of the text to
follow.  Since JSON has other mechanisms to determine encoding, this is
not required.  Receiving applications MAY safely ignore this initial
character without generating an error.  Implementations that do not send
U+FEFF are interoperable in the sense that all software implementations
which receive the un-prefixed text will not generate parse errors."

-- 
Joe Hildebrand
Received on Wednesday, 13 November 2013 23:52:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:59 UTC