Re: [oslc-ccm] Change Management Specification 3.0 is ready for CCM TC review

["Brian Steele" <steelebr@us.ibm.com>]

Hi Jim,

 

Here are my review comments for the Vocabulary:

The citation format section still says TBD

In section 5.1.8, severity is spelled incorrectly as secerity

In section 6.6, there are two places where it says oslcccm rather than oslc_cm.  Additionally we should provide descriptions for Fixed, Approved, and Reviewed.  Here are my suggestions:

Fixed: The issue is resolved or fixed but the resolution or fix has not yet been verified.

Reviewed: The resolution or fix has been reviewed

Approved: The resolution or fix is approved and can be delivered

 

I reviewed the Change Management 3.0 spec as well and I don't have any comments on it, it looks good.

 

 

Brian Steele

Senior Software Engineer
IBM Internet of Things

Phone: +1-714-327-7770
E-mail: steelebr@us.ibm.com

 

 

 

----- Original message -----
From: Jim Amsden/Raleigh/IBM@IBMUS
Sent by: <oslc-ccm@lists.oasis-open.org>
To: oslc-ccm@lists.oasis-open.org
Cc: "OASIS OSLC Core TC Discussion List" <oslc-core@lists.oasis-open.org>
Subject: [oslc-ccm] Change Management Specification 3.0 is ready for CCM TC review
Date: Thu, Feb 25, 2016 8:41 AM
 
The OSLC Change Management Specification 3.0 is complete and has had CCM chair review. There are currently no open issues for this specification so it is ready for CCM TC review pending promotion to committee specification and submission for public review.

Specification: https://tools.oasis-open.org/version-control/svn/oslc-ccm/trunk/specs/change-mgt/change-mgt.html
Vocabulary and constraints: https://tools.oasis-open.org/version-control/svn/oslc-ccm/trunk/specs/change-mgt/change-mgt-resources.html

Review comments can be posted to this email list and I will address the comments and changes. Any significant issues should be rased on the issues list (https://issues.oasis-open.org/browse/OSLCCCM/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel) where they will be addressed by the TC.

I have copied the members of the OSLC Core TC in case any of those members wish to review the first OSLC domain specification that uses OSLC Core 3.0 in case this would identify any Core issues.




Jim Amsden, Senior Technical Staff Member
OSLC and Linked Lifecycle Data
919-525-6575