[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=63838#comment-63838 ] 

Nick Crossley commented on OSLCCCM-14:
--------------------------------------

The agreement that a normal GET on an archived resource should result in a 404 is an IBM one, not necessarily an OSLC one. The Core spec simply says:

"Archived Resource: A resource in which an explicit action has been performed to mark the resource as no longer active and may be removed from typical user interactions.  As a consequence, an archived resource should be considered immutable."
...
"Another use [of archiving]may be to indicate that a resource has been deleted, but is saved by the system for historical or legal reasons. Having a consistent way to indicate that a resource, or a set of them, has been archived helps when defining certain views of the resources or queries. Archived Resources may be identified by having a property <code>oslc:archived</code>, with value <code>true</code>."

So there is no OSLC requirement about returning 404; rather, an archived resource is still an accessible resource with the oslc:archived property. The proposed text for the Config Mgmt spec is completely in line with that.

For IBM implementations, accessing the archived resource may need an additional header. If you think that header to make archived resources visible should be standard, then that should be raised as a  Core spec issue.


> 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)