Re: [Json] Proposed minimal change for duplicate names in objects

[Vinny A <[e-mail]>]

I prefer proposal 1, as proposal 2 may cause undue burden on parsers (they must keep track of all past keys, then we also have to discuss string key comparison which is decidedly not a minimal topic).
 
----------------
-Vinny
www.jsontest.com



________________________________
 From: Paul Hoffman <[e-mail]>
To: "[e-mail] WG" <[e-mail]> 
Sent: Tuesday, July 2, 2013 6:25 PM
Subject: [Json] Proposed minimal change for duplicate names in objects
 

<chair hats on>

Do either or both of these proposals work for people in the WG?

--Matt Miller and Paul Hoffman

The following are proposed minimal changes to make the JSON spec interoperable with respect to
objects that have duplicate names.

Proposal 1:

In section 2.2 (Grammar -> Objects):
  No change
In section 4 (Parsers):
  Add: "If a parser encounters an object with duplicate names, the parser MUST use only the last
  name/value pair that has the duplicate name.
In section 5 (Generators):
  Add: "The names within an object SHOULD be unique."

Proposal 2:

Same as Proposal 1 *except* that a second sentence is added for section 4: "A parser that streams
  its outputs MUST fail to finish parsing if it encounters more than one name/value pair with the
  same name."

_______________________________________________
json mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/json