OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-ccm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (OSLCCCM-36) Need to distinguish in-progress change set from delivered/committed one


     [ https://issues.oasis-open.org/browse/OSLCCCM-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Crossley updated OSLCCCM-36:
---------------------------------

    Proposal: 
[This part is replaced by a newer proposal in the comments] Add a new optional boolean property to the change set resource shape representing whether the change set has been delivered/committed. For example oslc_config:isCommitted.

[This part is somewhat orthogonal to the newer proposal in the comments] Add an optional oslc_config:committed (already a vocabulary term for baselines) to the change set resource shape to record the xsd:dateTime at which this occurred.

We should not assume that implementations record the dateTime in order to be able to distinguish between in-progress and delivered, so two separate properties are recommended,

  was:
Add a new optional boolean property to the change set resource shape representing whether the change set has been delievered/committed. For example oslc_config:isCommitted.

Add an optional oslc_config:committed (already a vocabulary term for baselines) to the change set resource shape to record the xsd:dateTime at which this occurred.

We should not assume that implementations record the dateTime in order to be able to distinguish between in-progress and delivered, so two separate properties are recommended,


> Need to distinguish in-progress change set from delivered/committed one
> -----------------------------------------------------------------------
>
>                 Key: OSLCCCM-36
>                 URL: https://issues.oasis-open.org/browse/OSLCCCM-36
>             Project: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
>          Issue Type: Improvement
>          Components: Configuration Management
>            Reporter: David Honey
>            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. We have 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)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]