Re: [Json] I-JSON Tpic #2: Top-Level

[Stefan Drees <[e-mail]>]

On 2014-05-20 22:50 +02:00, Paul Hoffman wrote:
> On May 20, 2014, at 1:27 PM, Tim Bray <[e-mail]> wrote:
>
>> For what it’s worth, this particular consensus excludes me.
>>
>> 1. The goal for I-JSOn is to maximize interoperability, and there
>> is software out there coded to 4627 which will fail when presented with 42
>> or true; so interoperability suffers when you do that.
>> 2. For the type of work the IETF is engaged in, Must-Ignore is almost
>> always a win in protocol designs, and thus we would do well to encourage
>> the use of JSON that makes this straightforward.
>
> <no hat>
>
> The goal of this document is to maximize interoperability. RFC 4627 and
> other specs had the rule that JSON texts had to be objects or arrays.
> Restricting JSON texts *in this profile* maximizes interoperability
> better than RFC 7159 did.
>
> This profile is not meant to be correcting RFC 7159; it is meant to be
> giving a profile that maximizes interoperability.

+1 from here

{"Stefan": "Greetings"}