ietf
[Top] [All Lists]

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

2013-11-13 15:54:56
On 11/13/13 2:40 PM, "Carsten Bormann" <cabo(_at_)tzi(_dot_)org> wrote:

On 13 Nov 2013, at 13:27, Paul Hoffman 
<paul(_dot_)hoffman(_at_)vpnc(_dot_)org> wrote:

It would be nice if ECMA-404 was clearer on this

I think the only way to read the English prose in ECMA-404 is to always
allow insignificant whitespace around every token, including the single
token that makes up an out-of-container JSON value.
That is also consistent with the most widely deployed extensions of JSON
for out-of-container values, including the one in recent JavaScript.

(Yes, it is easier to be unambiguous with ABNF.)

Note further that since ECMA-404 says:

"The whitespace characters are: character tabulation (U+0009), line feed
(U+000A), carriage return (U+000D), and space (U+0020)"

that the encoding detection does not need to be modified again with this
change.

-- 
Joe Hildebrand




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