[ https://tools.oasis-open.org/issues/browse/CAMP-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gilbert Pilz updated CAMP-171:
------------------------------
Proposal: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/53347/camp-spec-v1.1-wd42-171-v3.doc (was: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/53273/camp-spec-v1.1-wd41-171-v2.doc)
Update with a new proposal that moves the information on the use of select_attr in conjunction with PUT to a sub-section on the use of PUT. Add some explanatory text and an example.
> spec doesn't explicitly say you can use "select_attr" with PUT
> --------------------------------------------------------------
>
> Key: CAMP-171
> URL: https://tools.oasis-open.org/issues/browse/CAMP-171
> Project: OASIS Cloud Application Management for Platforms (CAMP) TC
> Issue Type: Bug
> Components: Spec
> Reporter: Gilbert Pilz
> Priority: Minor
>
> The spec handles the treatment of using 'select_attr' in a PUT request in a confusing way. In PR-08 we explicitly say that a Consumer MAY use 'select_attr' in a GET request (implying that Providers MUST support this). In PR-12 we say that "When one or more request parameters are specified for a PUT request ..."
> 1.) We never explicitly say that a Consumer MAY use the 'select_attr' query parameter in a PUT request. PR-12 implies that they can (or else why would PR-12 exist?), but this seems sloppy.
> 2.) PR-12 is vaguely worded. It says 'request parameters' but it really means 'the select_attr query/request parameter'.
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
