[OASIS Issue Tracker] (OSLCCORE-99) Need to distinguish in-progress change set from delivered/committed one

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

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

Nick Crossley commented on OSLCCORE-99:
---------------------------------------

Geoff Clemm would rather see a "compare" operation, rather than introduce a property like oslc_config:deliveredChangesets that just introduces a compare to some specific ancestor baseline.

> Need to distinguish in-progress change set from delivered/committed one
> -----------------------------------------------------------------------
>
>                 Key: OSLCCORE-99
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-99
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Improvement
>          Components: Configuration Management
>            Reporter: Nick Crossley
>            Assignee: Nick Crossley
>
> The current change management spec describes the resource shape for a oslc_config:ChangeSet. We have a requirement to distinguish an in-progress change set from a delivered/committed change set. One implementation has been using the deprecated oslc_config:mutable property. A value of "false"^^xsd:boolean meant in-progress, and "true"^^xsd:boolean meant delivered. However, this usage is a little obscure and not documented for in the spec for this specific use case.



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