ietf
[Top] [All Lists]

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

2013-11-13 21:16:43
<no hat>

On Nov 13, 2013, at 6:35 PM, Allen Wirfs-Brock 
<allen(_at_)wirfs-brock(_dot_)com> wrote:


On Nov 13, 2013, at 3:51 PM, Joe Hildebrand (jhildebr) wrote:

On 11/13/13 3:47 PM, "John Cowan" <cowan(_at_)mercury(_dot_)ccil(_dot_)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

<Prev in Thread] Current Thread [Next in Thread>