[OASIS Issue Tracker] (CAMP-202) User Mutability of Collections

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

    [ https://issues.oasis-open.org/browse/CAMP-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62195#comment-62195 ] 

Gilbert Pilz commented on CAMP-202:
-----------------------------------

[append this paragraph to Section 5.5]

There are interactions between various HTTP methods and the "mutable" and "consumer_mutable" attributes that warrant some explanation. It is possible for a Consumer to cause the Provider to change the values of some mutable attributes to in response to a POST operation. For example, a successful POST to an operation resource could cause the Provider to change the value of the status attribute of the target resource. However, this does not mean that the status attribute of that target resource is "consumer mutable". Consumer mutability refers the to ability of the Consumer to directly alter the value of one or more attribute via the PUT or PATCH methods.

> User Mutability of Collections
> ------------------------------
>
>                 Key: CAMP-202
>                 URL: https://issues.oasis-open.org/browse/CAMP-202
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>            Reporter: Michael Norman
>            Assignee: Anish Karmarkar
>
> We need to clarify the way the user mutability of collections is expressed through the API so that a user interface can determine whether or not it is possible to add to a collection.  Since this is a POST not a PUT we need to make sure that our proposals for instance mutability are transferrable to the collections, or extend them, and ensure that the specification clearly articulates the semantics.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)