History   View   Links to this page Revision from: 2012 September 11 | 09:49 am
This is the revision from 2012 September 11 at 09:49 am   View the current live version of the article.

OSLC Core properties used by all Configuration Management resources

Prefixed Name Occurs Read-only Value-type Representation Range Description
OSLC Core: Common Properties
rdf:type one-or-many unspecified Resource Reference n/a The resource type URIs.
dcterms:contributor zero-or-many unspecified AnyResource Either any Contributor or contributors to resource (reference: Dublin Core). It is likely that the target resource will be an foaf:Person but that is not necessarily the case.
dcterms:created zero-or-one True DateTime n/a n/a Timestamp of resource creation (reference: Dublin Core)
dcterms:creator zero-or-many unspecified AnyResource Either any Creator or creators of resource (reference: Dublin Core). It is likely that the target resource will be an foaf:Person but that is not necessarily the case.
dcterms:description zero-or-one unspecified XMLLiteral n/a n/a Descriptive text (reference: Dublin Core) about resource represented as rich text in XHTML content. SHOULD include only content that is valid and suitable inside an XHTML <div> element.
dcterms:identifier exactly-one True String n/a n/a A unique identifier for a resource. Assigned by the service provider when a resource is created. Not necessarily intended for end-user display.
dcterms:modified zero-or-one True DateTime n/a n/a Timestamp of latest resource modification (reference: Dublin Core)
dcterms:subject zero-or-many unspecified String n/a n/a Tag or keyword for a resource. Each occurrence of a dc:subject property denotes an additional tag for the resource.
dcterms:title exactly-one unspecified XMLLiteral n/a n/a Title (reference: Dublin Core) of the resource represented as rich text in XHTML content.

Configuration

Additional properties to be discussed - may include:

  • A way to identify different configurations of the same ‘thing’ - same resource set, same component, …
  • Sub-configurations (configurations contained in this configuration)
  • Dependencies (configurations on which this configuration depends)
  • Baselines created from this configuration
  • Baselines merged into this configuration
  • dcterms:replaces to define predecessor

Baseline

Additional properties to be discussed - may include:

  • A way to identify different baselines of the same ‘thing’ - same resource set, same component, …
  • Sub-baselines (baselines contained in this baseline)
  • Dependencies (baselines on which this baseline depends)
  • Resource set (a Basic Profile Container defining the resources in this baseline)

Note that configurations and baselines do not have status or lifecycle properties; instead, we expect other resources that define such status to link to configurations and baselines. These other resources might be Change Requests, or resources from some as-yet undefined OSLC Lifecycle or Process Domain.