[OASIS Issue Tracker] (OSLCCORE-183) Validation of oslc_config:accepts and oslc_config:acceptedBy

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

David Honey created OSLCCORE-183:
------------------------------------

             Summary: Validation of oslc_config:accepts and oslc_config:acceptedBy
                 Key: OSLCCORE-183
                 URL: https://issues.oasis-open.org/browse/OSLCCORE-183
             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
          Issue Type: Bug
          Components: Configuration Management
            Reporter: David Honey
            Assignee: Nick Crossley


When should/must a configuration management server perform validation of oslc_config:accepts and oslc_config:acceptedBy?

This is related to whether oslc_config:accepts and oslc_config:acceptedBy are lifetime invariant or not. If they are lifetime invariant, then a contribution need only be validated once when it is added. If a configuration management server allows a stream to be made immutable, or have other state-like properties changed, then one could imagine that the validation conditions for a contributed configuration might change over time. Is there a real use case here that we need to consider?

The issue relates to [466476: Several actions are unperformable when an "Unavailable configuration" is in the tree|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/466476] and whether GCM MUST perform validation of each contribution when the contributions to a global configuration change.



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)