- From: Paul Hoffman <paul.hoffman@vpnc.org>
- Date: Wed, 13 Nov 2013 19:15:28 -0800
- To: Allen Wirfs-Brock <allen@wirfs-brock.com>
- Cc: Joe Hildebrand Hildebrand <jhildebr@cisco.com>, John Cowan <cowan@mercury.ccil.org>, IETF Discussion <ietf@ietf.org>, JSON WG <json@ietf.org>, Anne van Kesteren <annevk@annevk.nl>, "www-tag@w3.org" <www-tag@w3.org>, es-discuss <es-discuss@mozilla.org>
<no hat> On Nov 13, 2013, at 6:35 PM, Allen Wirfs-Brock <allen@wirfs-brock.com> wrote: > > On Nov 13, 2013, at 3:51 PM, Joe Hildebrand (jhildebr) wrote: > >> 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. > > However, for example, a conforming implementation of the ECMAScript JSON.parse function would reject any string passed to it that starts with a U+FFEF code point because the unquoted occurrence of that code point does not conform to the ECMA-252, 5th Edition or Ecma-404 JSON grammar. > > In order to be successfully processed, that code point would have to be stripped from the string prior to calling JSON.parse. The question was specifically about ECMA-404, not ECMA-252. It would be great to hear from TC39 whether or not ECMA-404 allows or disallows it. --Paul Hoffman
Received on Thursday, 14 November 2013 03:16:38 UTC