Re: [Json] Allow any JSON value at the top level

[Tatu Saloranta <[e-mail]>]

On Tue, Jun 11, 2013 at 2:25 AM, Carsten Bormann <[e-mail]> wrote:

> On Jun 7, 2013, at 19:54, Tatu Saloranta <[e-mail]> wrote:
>
> >> Apart from the (intellectually nicely challenging, but practically
> irrelevant) auto-detection thing,
> >
> > Irrelevant based on what? I thought this is what any half-decent JSON
> parser did; unless platform does not expose byte sequence as input, case
> for some scripting languages.
> > I have written multiple parsers (json, xml) that do just this, and know
> that others exist as well.
>
> It is true that there are parsers that implement autodetection.
> Lots of code is written that is then never exercised.
>

If by lots of code you mean "less than 100 lines", yes.


>
> > I don't know what leads to assumption of irrelevancy here, and it should
> be fully spelled out.
>
> This is irrelevant in practice as JSON is used with UTF-8 in practice.
>

My main concern is with UTF-16. My understanding is that for "Big 5"
languages its use make sense, from efficiency perspective. I do not have
data on this; in XML space document test sets had non-trivial amount of
content in various encodings.

If UTF-16 is not widely used then I can see why this would be considered of
little significance.


> The main job that the text in section 3 seems to do is to convince people
> not to send a BOM in front of their UTF-8 JSON.  Now that is a good
> thing...  Unfortunately, some JSON parsers have been "fixed" to accept BOMs.
>
>
Yes. That takes about 50 more lines of code to add, to work around oddities
of generators by a certain big Redmond-based software company.

-+ Tatu +-