[OASIS Issue Tracker] (CAMP-201) Consumer mutability of attributes and attribute types

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

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

Gilbert Pilz commented on CAMP-201:
-----------------------------------

During the meeting of 1/13/2016 the group decided that, instead of trying to bend our type system to serve the needs of metadata that we all agree should be associated at the instance level, perhaps we should just indicate mutability at the instance level. I was given an AI to put together a rough outline of what this might look like. Here it is: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/57401/mutability_outline.txt

> Consumer mutability of attributes and attribute types
> -----------------------------------------------------
>
>                 Key: CAMP-201
>                 URL: https://issues.oasis-open.org/browse/CAMP-201
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>          Components: Spec
>    Affects Versions: 1.2
>            Reporter: Anish Karmarkar
>            Assignee: Anish Karmarkar
>            Priority: Critical
>
> The spec currently defines consumer mutability of an attribute in the attribute type definition. Questions have been raised about whether that is appropriate. Few scenarios that complicate this:
> 1) Collection type 'items' attribute may be mutable or not depending on the kind of collection.
> 2) the consumer mutability of an attribute may depend on an instance not the type. Moving this to the type necessitates unnecessary invention of additional types
> 3) the mutability of an attribute may depend on other factors such as authorization/credentials of the consumer or it may change with time (because changing the attribute value may make something else inconsistent).
> Issues 180, 196, and 199 depend on resolution of this issue.



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