Re: [Json] What is a JSON-text? [REVISITED]

[R S <[e-mail]>]

On Thu, Oct 3, 2013 at 11:59 AM, Paul Hoffman <[e-mail]> wrote:

> <no hat>
>
> On Oct 3, 2013, at 9:33 AM, Matt Miller (mamille2) <[e-mail]>
> wrote:
>
> > There was previously much discussion on this topic[2].  Some have
> restated their support.  What do others think about changing JSON-text to
> allow any JSON value versus just objects or arrays?
>
> I'm +.5 on the proposal. It would make 4627bis more aligned with
> ECMAScript, and there is no rationale given for "a JSON-text can be less
> that what you think it can be". This change will make some parsers that are
> 4627-but-not-ECMAScript compliant become not compliant. To me, the latter
> is not as important as the former.


In the abstract, I think matching ECMAScript is a good idea. If I were
choosing a parser, I would definitely pick one that supported any JSON
value at the root.

As a sender, I wouldn't want the RFC to lead me to believe that every JSON
parser could handle the ECMAScript root-level primitive JSON values at this
time. Having a note that points out this variation exists is a good idea.

Some other group of people can come back in 10 years and write down what
happened (maybe the note will tempt everyone to support primitive root
values, maybe not).

- Rob