[OASIS Issue Tracker] (OSLCCCM-17) Potential confusion about oslc_config:previousBaseline

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

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

Geoffrey Clemm commented on OSLCCCM-17:
---------------------------------------

As the original author of the text on which this definition was based, I can confirm that David is correct ... the current text is not what was intended.  Suggested new wording:

"The latest baseline that has been created in the stream or used to update the stream is a previous baseline of the stream.  If no baselines have been created in the stream or used to update the stream, then the baseline from which the stream was created/initialized is a previous baseline of the stream.  If a baseline has been merged into the stream since the latest baseline that has been created in the stream or used to update the stream, than that is also a previous baseline of the stream.   When a "make-baseline" operation is applied to a stream, the previous baseline properties of the new baseline are set to be the previous baseline properties of the stream, and the previous baseline property of the stream is set to be the newly created baseline."

Note that this assumes every stream is created from some initial baseline, and therefore the previous baseline property is never empty.   If the specification does not require this, then we would need to add a clause stating that if the stream was not created from a baseline, and no baselines were created in the stream, and no baselines were used to update the stream, and no baselines were merged into the stream, then there will be no previous baseline property of the stream.


> Potential confusion about oslc_config:previousBaseline
> ------------------------------------------------------
>
>                 Key: OSLCCCM-17
>                 URL: https://issues.oasis-open.org/browse/OSLCCCM-17
>             Project: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
>          Issue Type: Improvement
>            Reporter: David Honey
>
> The description of oslc_config:previousBaseline for a stream in https://tools.oasis-open.org/version-control/browse/wsvn/oslc-ccm/trunk/specs/config-mgt/config-resources.html says this:
> "A reference to the immediately preceeding baseline of this stream. Multiple instances of this property imply the stream was merged from one or more baselines, and no baseline of the merged result has yet been taken. If the property is absent, no baseline of this stream has been taken."
> I believe the intent is that this predicate references the most recent baseline created from a stream, and not the configuration that the stream was copied from (which prov:wasDerivedFrom would describe). However, the description hints at both meanings, and I know of at least one implementation that has interpreted it as the latter, and a different implementation as the former.
> If I have understood the intent correctly, I suggest the following changed wording:
> "A reference to the most recent baseline created from this stream.  If the property is absent, no baseline of this stream has been taken. Multiple instances of this property imply the stream was merged from one or more baselines, and no baseline of the merged stream has yet been created."



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