Re: [Json] The names within an object SHOULD be unique.

[Jorge Chamorro <[e-mail]>]

On 27/07/2013, at 22:22, Matt Miller (mamille2) wrote:

> Hello all,
> 
> Here is an attempt to summarize responses to the duplicate names questions.
> 
> The consensus from this thread seems to be that duplicate names within the same JSON object are not generally desirable.
> 
> There appears to be rough consensus that a generator (for some definition of "generator") ought to take steps to avoid emitting duplicate names, but that there exists a non-trivial amount of software where the prohibition of duplicates cannot be completely enforced.
> 
> There appears to be consensus that parsers (for some definition of "parser") need to be able to deal with duplicate names in some manner.  There is rough consensus that 4627bis ought to provide guidance on how parsers deal with duplicate names.  However, there is no one option that has any consensus; instead, there appears to be acquiescence that a given parser ought to support one option from a limited set of documented choices.  The most common suggestions -- which appear to reflect the majority of existing implementations -- far so:
> 
> * report an error in some manner
> * report the last value that appears in the JSON text
> * report all the values that appear in the JSON text

If duplicate names are generally considered a no-no, and given that they're mostly used for comments (usually with the key "//"), and given the security risks discussed in the "command":"launch-missiles" thread, perhaps the best thing to do with the duplicate keys and their values might be to simply drop them altogether, not throw any errors, not nothing, just drop them, all of them, including the last one.

So missiles won't be launched and comments will vaporize, which is good.
-- 
( Jorge )();