[OASIS Issue Tracker] (OSLCCCM-29) References to before and after states of affected resources

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

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

Martin Sarabura commented on OSLCCCM-29:
----------------------------------------

1.	Where is the shape for config#Configuration?
2.	The oslc_config:selections property references oslc_config:ChangeSetSelections which is not specified
3.	https://tools.oasis-open.org/version-control/browse/wsvn/oslc-ccm/trunk/specs/config-mgt/config-resources.html#citemoperations
PUT: …. Might or might not … should be MAY …


Issue 29, https://tools.oasis-open.org/version-control/browse/wsvn/oslc-ccm/trunk/specs/config-mgt/config-resources.html#changesets
This issue is resolved by introducing the concept of change sets and the oslc_config:overrides property, however the verbiage could use some tightening up – along with points 1 and 2 above.
The configuration defined by a change set thus identifies both the 'before' state (the base configuration that is overridden by this change set), …

Do you really mean prov:wasDerivedFrom here? Isn’t this oslc_config:overrides?
When a change set is based on a stream (the prov:wasDerivedFrom property on an instance of an oslc_config:ChangeSet…
Providers can avoid this lack of precision by ensuring either that all changes made to a stream are either captured….
… or that the selections resource of the stream stream’s oslc_config:selections property …
The bottom half of the paragraph is OK but it is really tough to parse. I think my recommendations may be enough.

Is this normative?
Systems that allow a single change set to be applied to multiple base configurations must represent that internal change set by …


> References to before and after states of affected resources
> -----------------------------------------------------------
>
>                 Key: OSLCCCM-29
>                 URL: https://issues.oasis-open.org/browse/OSLCCCM-29
>             Project: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
>          Issue Type: Bug
>          Components: Configuration Management
>            Reporter: Martin Sarabura
>
> Our PTC tools have a usability feature that allows the end user to see the state of the affected resources prior to and after the requested changes have been implemented. This allows a reviewer to easily ascertain that the implemented changes are consistent with the request, even if other changes had been introduced by other change requests concurrently. The alternative approach - which is supported by the current spec - is to review every change in the list of change sets. This approach adds cognitive load if more than one change set was created and/or if the same resource is represented more than once in the change sets.



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