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

[Stefan Drees <[e-mail]>]

On 2013-10-03 19:10 +02:00, Tim Bray wrote:
> I am very strongly against changing the -bis to allow top-level values.
> - It’s a bad practice
> - support for it in popular libraries is very patchy.

Me also very strongly against "non-container" top-level entities.

Additional rationale:
- Add two bytes to wrap the serialized/transported value into array or
   say six bytes and use eg. {"d":my_top_level_value} should be cheap
   for the benefit of producing a JSON-text.

Even if value is king, values like strings, numbers, true, false or null 
just wrapped into "no clothes" make me wonder why one would serialize 
(or forward) them as advertised JSON-text in the first place.

>
> On Thu, Oct 3, 2013 at 9:33 AM, Matt Miller (mamille2)
> <[e-mail]>wrote:
>
>> Hello all,
>>
>> There appears to be rough consensus to reference ECMA-262 edition 5.1.  As
>> James pointed out[1], something will need to be said about what is a
>> JSON-text; either 4627bis states a difference from ECMA-262 edition 5.1, or
>> 4627bis states a difference from RFC 4627.
>>
>> 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?
>>
>>
>> -  Paul Hoffman and Matt Miller
>>
>> [1] < http://www.ietf.org/mail-archive/web/json/current/msg01721.html >
>> [2] < http://www.ietf.org/mail-archive/web/json/current/msg00553.html >
>> ...

["Stefan"]