[OASIS Issue Tracker] (OSLCCCM-27) New type ChangeAuthorization needed for CM spec

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

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

James Amsden commented on OSLCCCM-27:
-------------------------------------

ChangeNotice label and type URI are correct in my edited version. Will be updated on the next checkin.

How about:
change: Represents a change request that controls the authorization to address a specific set of related change requests.
to: Represents an assignment notification of a change request. May be used also to bestow authority onto the assigned user to effect the changes.

These are all inherited properties, so it is appropriate for them to refer to the parent class, and it would require duplicating all the property shapes to provide different descriptions.

I updated the diagram in the introduction to include ChangeNotice. Also added the parent property.

> New type ChangeAuthorization needed for CM spec
> -----------------------------------------------
>
>                 Key: OSLCCCM-27
>                 URL: https://issues.oasis-open.org/browse/OSLCCCM-27
>             Project: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
>          Issue Type: Bug
>          Components: Change Management
>            Reporter: Martin Sarabura
>
> Notwithstanding issue #26 which I just posted, I feel that change notice should be added explicitly to the spec.
> There are two classes of type in the current spec: Request and Task.
> Requests include Change Request (which is also drawn up as the base type in the UML diagram), Enhancement and Defect.
> Tasks include Task (which is drawn up as the base type in the UML diagram) and ReviewTask.
> A change notice in certain tools is neither a request nor a task: It is an authorization to perform multiple tasks. Thus it is more of a "command" than a request and it is a container of tasks. Since it has a different meaning than the available Types and since it is found in a number of CM tools, I believe it should be listed as its own type.



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