Re: [Json] Duplicate names: are they erroneous or not?

[Stefan Drees <[e-mail]>]

On 2013-07-07 07:53 +02:00, John Cowan wrote:
> What I wish to avoid is a specification that says that having two
> fields of the same name in an object is a perfectly okay thing to do.
> In other words, such documents for my purposes have to be erroneous,
> rather than a legitimate way of encoding multimaps.  Is there anyone
> who can't live with that restriction?

If the above question is equivalent to:

Does someone speak up, that MUST encode multimaps through members in an 
object, where the names are not pairwise distinct?

I for myself will **not** speeak up. But that is neither necessary nor 
sufficient for this important pre condition of going further as 
described i your second paragraph below.

Maybe it might good to request, that the chairs at this point - or not 
too far in the future - start such a consensus preparing call?

> If there isn't anyone, then we can talk about whether this is an error
> that generators and/or parsers MUST or SHOULD detect.  But if we can't
> even get consensus on that much, it's futile to discuss parser or
> generator behavior.

I need not consider any mandate - like the WG - only the rules for 
participating in these discussions, and I am willing to evolve the JSON 
into a versatile future proof data interchange format, as long as it 
doesn't mutate into the serialization format of just another specific 
language culture.

{"Scene":[{"Me":"All"},{"Dog":"(wags his tail)"},{"Me":"the Best."}]}