Next in thread → Next in month →

[OASIS Issue Tracker] (CAMP-171) spec doesn't explicitly say you can use "select_attr" with PUT

From
OASIS Issues Tracker <>
Date
2014-07-03T16:24:24+00:00
ID
Thread
[OASIS Issue Tracker] (CAMP-171) spec doesn't explicitly say you can use "select_attr" with PUT
[ https://issues.oasis-open.org/browse/CAMP-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=40061#comment-40061 ] 

Martin Chapman  commented on CAMP-171:
--------------------------------------

added a new proposal v4. Make sure all references to 400 are "400 Bad Request..."

> spec doesn't explicitly say you can use "select_attr" with PUT
> --------------------------------------------------------------
>
>                 Key: CAMP-171
>                 URL: https://issues.oasis-open.org/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)
Next in thread → Next in month →