[OASIS Issue Tracker] (OSLCCCM-23) oslc_cm:status range is String in CM 2.0 and can't be changed to oslc_cm:Status

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

James Amsden created OSLCCCM-23:
-----------------------------------

             Summary: oslc_cm:status range is String in CM 2.0 and can't be changed to oslc_cm:Status
                 Key: OSLCCCM-23
                 URL: https://issues.oasis-open.org/browse/OSLCCCM-23
             Project: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
          Issue Type: Bug
          Components: Change Management
            Reporter: James Amsden
            Priority: Blocker


Early in the CM 3.0 spec development there was a plan to use Actions to define valid state transitions on property oslc_cm:status. Because Actions was deferred in Core 3.0, we decided to defer its use in CM 3.0. 

As a compromise, we created an enumeration oslc_cm:Status with values such as oslc_cm:Closed, Inprogress, etc. and used that as the range for oslc_cm:status in order to at least define a minimal set of expected values. 

However, oslc_cm:status is a String in CM 2.0 and this would be a breaking change. So we have to remove oslc_cm:Status, and change the range of oslc_cm:status to xsd:String. 

Also, the CM 2.0 boolean properties oslc_cm:closed will need to be added back. We should discuss this and see if we think these should be deprecated, and if we can retain oslc_cm:Status and xsd:String for oslc_cm:status.




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