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-27) New type ChangeAuthorization needed for CM spec

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

Martin Sarabura commented on OSLCCCM-27:

The name, type uri are incorrect in https://tools.oasis-open.org/version-control/browse/wsvn/oslc-ccm/trunk/specs/change-mgt/change-mgt-resources.html#changeNotice
The Summary talks about authorization but there is another use case, where the change notice is used simply to designate a user who will be responsible for implementing the changes. This is not so much an authorization as an assignment. Perhaps "An assignment notification of a change request. May be used also to bestow authority onto the assigned user to effect the changes."
Also, some field descriptions refer to "this" change request - is this easy to change to change notice? I understand that in this case we can interpret "change request" as referring to the parent class. Which BTW when I look at the diagram in section 1 (Introduction) I see that change notice is not a child of change request.
Similarly the rdf:type description refers to change request not change notice.

> 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

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