[OASIS Issue Tracker] (OSLCCCM-14) How should previousBaseline behave when an intermediate baseline is deleted?

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

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

David Honey commented on OSLCCCM-14:
------------------------------------

One of the issues is that we agreed that archived resources should be treated as 404 NOT_FOUND for GET requests. So even leaving a vestigial stub resource, specifying it must be marked as oslc:archived "true"^^xsd:boolean means a user still cannot traverse the predecessor chain. I think the spec should suggest a way of satisfying a requirement to be able to traverse the predecessor chain.

> How should previousBaseline behave when an intermediate baseline is deleted?
> ----------------------------------------------------------------------------
>
>                 Key: OSLCCCM-14
>                 URL: https://issues.oasis-open.org/browse/OSLCCCM-14
>             Project: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
>          Issue Type: Bug
>          Components: Configuration Management
>            Reporter: Nick Crossley
>            Assignee: Nick Crossley
>            Priority: Minor
>
> When a baseline is deleted, should existing baselines derived from the deleted one have their oslc_config:previousBaseline property updated to point to the previousBaseline of the one being deleted, to maintain the provenance chain? Or would this break things like digital signatures?



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