[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (CAMP-50) spec needs to clarify behavior in the case of duplicate JSON keys
[ http://tools.oasis-open.org/issues/browse/CAMP-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32589#action_32589 ] Gilbert Pilz commented on CAMP-50: ---------------------------------- The proposal looks good. Oracle suggests the following modifications: 1.) Add normative language to the effect that servers, also, MUST NOT send JSON objects that contain duplicate keys. 2.) Add normative language that states that, upon receiving a request with a JSON object that contains duplicate keys, servers SHOULD respond with a 400. > spec needs to clarify behavior in the case of duplicate JSON keys > ----------------------------------------------------------------- > > Key: CAMP-50 > URL: http://tools.oasis-open.org/issues/browse/CAMP-50 > Project: OASIS Cloud Application Management for Platforms (CAMP) TC > Issue Type: Bug > Components: Spec > Reporter: Gilbert Pilz > Assignee: Adrian Otto > > In section 2.2 of RFC 4627 (http://www.ietf.org/rfc/rfc4627.txt) it states that : > "An object structure is represented as a pair of curly brackets surrounding zero or more name/value pairs (or members). A name is a string. A single colon comes after each name, separating the name from the value. A single comma separates a value from a following name. The names within an object SHOULD be unique." > The SHOULD in the last sentence means that "if implementations think they have a valid reason, they can have duplicate names in an object". If you search the net you can find a number of different strategies for dealing with duplicate names/keys. To improve interoperability, CAMP needs to clarify its position with respect to duplicate keys. > High-level proposal: CAMP should further constrain RFC 4627 by saying that clients and the servers MUST NOT send JSON that contains duplicate keys. The clients or servers response to a message containing multiple keys should be left undefined - i.e. CAMP should not require servers to send an error response if/when they detect multiple keys. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]