Re: [Json] serializing sequences of JSON values

Does either the old or new specification say anything about multiple
values in sequence? I'm pretty darn sure the old version at least said
that application/json documents contain one and only one value, and
says nothing about serializing JSON in other formats, so encapsulation
is not addressed. I also don't see how any process that expects to
read sequences of self-delimited JSON objects and arrays is going to
blithely accept numbers and strings and whatnot. I find the idea
unlikely that there is some running code that 1. expects sequences of
JSON values with no delimiters, 2. uses a parser that precisely
followed the JSON specification and rejected anything but JSON objects
and arrays prior to this change, 3. has that parser change under it to
accept all kinds of values and 4. is so indifferent to the contents of
what it is processing that it doesn't notice that it's getting numbers
and strings instead of objects or arrays.

On Sun, Mar 9, 2014 at 3:37 PM, Nico Williams <nico@cryptonector.com> wrote:
>
> On Mar 9, 2014 4:16 AM, "Larry Masinter" <masinter@adobe.com> wrote:
>>
>> >  This means the serializer would have to be explicitly told whether to
>> > insert space before or after
>> > writing out data.
>>
>> If you want to write out a sequence of JSON values you would write them
>> out as an array with [] around and comma separators.
>
> Doesn't work for log files...
>
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>