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

[Tatu Saloranta <[e-mail]>]

On Fri, Jun 7, 2013 at 1:59 AM, Carsten Bormann <[e-mail]> wrote:

> On Jun 7, 2013, at 05:51, "Manger, James H" <
> [e-mail]> wrote:
>
> > I propose allowing a JSON text to be any JSON value.
> >
> >   A JSON text is a serialization of any JSON value.
> >
> >   JSON-text = value
>
> 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.

I don't know what leads to assumption of irrelevancy here, and it should be
fully spelled out.

one other result is that JSON texts no longer stream.  RFC 4627 texts are
> self-delimiting, the new ones wouldn't always be.  Of course, if you want
> to stream sequences of JSON texts, you could always limit those back to
> arrays or maps ("objects").
>


I don't see this as any less self-delimiting, although best-practices would
probably dictate suggestion to add white space between root-level values.

Which is what existing tools that allow this do, as expected.

-+ Tatu +-