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

["Markus Lanthaler" <[e-mail]>]

On Friday, June 07, 2013 11:38 PM, R S wrote:
> I believe this proposal is in scope--it's one of the inconsistencies
> with ECMAScript this group has been tasked with resolving, and it was
> mentioned during the chartering process.

I disagree. Allowing something else than an object or an array at the
top-level is clearly out of scope IMO.


> Are there interoperability problems we should be aware of? In my
> experience, this change doesn't matter to applications that can only
> handle objects or arrays--they simply encounter an error immediately
> after parsing rather than during it.

Well, changing the {}s to <>s would also result in an error but that doesn't
mean that it won't cause problems. The most important thing for this WG is
to preserve backwards-compatibility. Turning JSON parsers that are currently
completely conformant obsolete and arguing that they would error clearly
breaks backwards compatibility. As someone else showed in a different
thread, this would e.g. break Rail's default JSON parser.


--
Markus Lanthaler
@markuslanthaler