OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

camp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Updated: (CAMP-136) 6.3.1.1 Duplicate Keys in JSON Objects


     [ http://tools.oasis-open.org/issues/browse/CAMP-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Chapman  updated CAMP-136:
---------------------------------

    Proposal: 
CAMP defined JSON objects do not contain duplicate keys. 

Consumers and Providers SHALL NOT transmit JSON objects that contain duplicate keys. [PR-02] 

If a Consumer sends a Provider a request containing duplicate keys in a JSON object, the Provider SHOULD reject the request by sending back a '400 Bad Request' status code. [PR-03] If a Provider sends a Consumer a response containing duplicate keys in a JSON object, the Consumer SHOULD raise an error to the user indicating the response from the server was malformed. [PR-04] 

Note: Duplicate keys in JSON objects are allowed by [RFC4627]. This specification prohibits duplicate keys for interoperability reasons. 

**************** 

So we have the rule: No duplicate keys 

Rule for consumer and producers (in case they encounter duplicate keys) 

Rule for invalid content (if you do get a duplicate key) 

Note: Where you may see a different rule, word about why ours is different)



  was:
CAMP defined JSON objects do not contain duplicate keys. 

Consumers and Providers SHALL NOT transmit JSON objects that contain duplicate keys. [PR-02] 

If a Consumer sends a Provider a request containing duplicate keys in a JSON object, the Provider SHOULD reject the request by sending back a '400 Bad Request' status code. [PR-03] If a Provider sends a Consumer a response containing duplicate keys in a JSON object, the Consumer SHOULD raise an error to the user indicating the response from the server was malformed. [PR-04] 

Note: Duplicate keys in JSON objects are allowed by [RFC4627]. This specification prohibits duplicate keys for interoperability reasons. 

**************** 

So we have the rule: No duplicate keys 

Rule for consumer and producers (in case they encounter duplicate keys) 

Rule for invalid content (if you do get a duplicate key) 

Note: Where you may see a different rule, word about why ours is different)


OP's proposal:

CAMP defined JSON objects do not contain duplicate keys. 

Consumers and Providers SHALL NOT transmit JSON objects that contain duplicate keys. [PR-02] 

If a Consumer sends a Provider a request containing duplicate keys in a JSON object, the Provider SHOULD reject the request by sending back a '400 Bad Request' status code. [PR-03] If a Provider sends a Consumer a response containing duplicate keys in a JSON object, the Consumer SHOULD raise an error to the user indicating the response from the server was malformed. [PR-04] 

Note: Duplicate keys in JSON objects are allowed by [RFC4627]. This specification prohibits duplicate keys for interoperability reasons. 

**************** 

So we have the rule: No duplicate keys 

Rule for consumer and producers (in case they encounter duplicate keys) 

Rule for invalid content (if you do get a duplicate key) 

Note: Where you may see a different rule, word about why ours is different)

> 6.3.1.1 Duplicate Keys in JSON Objects
> --------------------------------------
>
>                 Key: CAMP-136
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-136
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: Public Review
>            Reporter: Gilbert Pilz
>
> 6.3.1.1 Duplicate Keys in JSON Objects reads in part: 
> ***** 
> Duplicate keys in JSON objects are allowed by [RFC4627]. This specification prohibits duplicate keys for interoperability reasons. 
> ***** 
> Definitely note material. State the rule for CAMP, notes explain other choices. 

-- 
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]