[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:all-tabpanel ]

Nick Crossley updated OSLCCCM-14:
---------------------------------

    Proposal: 
Modifying links leads to complications if the data is restored from an archive, so we will not require any such change. Instead, add a non-normative note:

Since providers may support deletion of baselines, clients must not assume that references to baselines can be resolved; like any other resource, clients must be prepared to handle 404 errors. Since baselines are normally linked into a provenance chain using the oslc_config:previousBaseline property, servers may elect to leave a stub resource (one with a minimal set of properties) behind instead of truly deleting a baseline. Servers SHOULD add the property oslc:archived=TRUE on a reduced form of a partially deleted baseline.


  was:
Modifying links leads to complications if the data is restored from an archive, so we will not require any such change. Instead, add a non-normative note:

Since providers may support deletion of baselines, clients must not assume that references to baselines can be resolved; like any other resource, clients must be prepared to handle 404 errors. Since baselines are normally linked into a provenance chain using the oslc_config:previousBaseline property, servers may elect to leave a stub resource (one with a minimal set of properties) behind instead of truly deleting a baseline.



> 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
>              Labels: ready-for-vote
>
> 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)