This part of the OSLC Configuration Management Specification defines the representation and behavior of versioned resources.
This part of the OSLC Configuration Management Specification defines the representation and behavior of versioned resources - resources that have multiple versions.
As described in OSLC Configuration Management - Concept resources, version resources, and configuration contexts, the major “Artifacts” or “Entities” in OSLC domains are concept resources.
The state (including the properties) of a concept resource can vary over time, or for other reasons. A versioned resource is a concept resource that keeps track of different states; a version resource is one specific state of a versioned resource.
Versioned resources are typically used in configurations - where they are often called configuration items.
A version resource defines a particular version of the state of a concept resource. Not every past state is necessarily kept. A server MAY elide or discard states.
A version resource URI identifies a specific version of a concept resource with no further configuration context required.
A version resource MUST have a type of oslc_config:VersionResource.
A version resource MUST be related to its concept resource using the dcterms:isVersionOf property.
Version resources SHOULD be compliant with [[!LDP]].
Version resources SHOULD have an oslc_config:versionId property.
Servers MAY provide other properties that distinguish between major changes or revisions, and minor changes or iterations.
A versioned resource server MUST support the following operations on version resources:
A versioned resource server MAY support the following operations on version resources:
A versioned resource server MAY provide delegated user interface dialogs for creation of new concept resources or new version resources.
A versioned resource server SHOULD provide delegated user interface dialogs for selection of concept resources. A versioned resource server MAY provide delegated user interface dialogs for selection of version resources, but such selection is typically performed in a configuration context to find the appropriate version.
A versioned resource server SHOULD implement compact rendering, both for concept resources and version resources. See Compact Rendering for the handling of configuration context in such rendering.
A versioned resource server MAY publish version resources in a Tracked Resource Set; the URIs in the base and change log MUST be the version resource URIs, not the concept resource URIs. All Tracked Resource Sets for version resources MUST be compliant with [[!TRS]].