[OASIS Issue Tracker] Updated: (CAMP-48) Using SelectAttr in conjunction with PUT is duplicative and problematic

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Gilbert Pilz updated CAMP-48:
-----------------------------

    Proposal: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/48316/camp-36-48-2013-02-19.doc  (was: High-level proposal: add text to description of SelectAttr that prohibits its use with PUT or PATCH.)

Joint proposal for CAMP-36 and CAMP-48; specify the use of JSON Patch and narrow the scope of 'SelectAttr' to apply solely to the GET method.

> Using SelectAttr in conjunction with PUT is duplicative and problematic
> -----------------------------------------------------------------------
>
>                 Key: CAMP-48
>                 URL: http://tools.oasis-open.org/issues/browse/CAMP-48
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Improvement
>          Components: Spec
>            Reporter: Gilbert Pilz
>            Assignee: Gilbert Pilz
>
> This issue will depend upon the resolution of CAMP-36 but, if people agree we should use JSON Patch for fine-grained updates, there really isn't any need to support PUTs that use the SelectAttr parameter. Furthermore, supporting SelectAttr in the context of PUT is a mess implementation-wise. There are a bunch of tricky corner cases in which you have to make sure that request body doesn't contain any attributes that aren't selected, check for "implicit deletes" in which the user selects an attribute but don't supply a value in the body, etc. 

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