Open Services for Lifecycle Collaboration Core Specification Version 2.0 Appendix A: Common Properties

This Version

• http://open-services.net/bin/view/Main/OSLCCoreSpecAppendixA

• http://open-services.net/bin/view/Main/OSLCCoreSpecAppendixA

• Dave Johnson

• The OSLC Core Specification Workgroup

Table of Contents

Overview

This is a list of common properties and resources defined by or used by the Core spec. Unlike the rest of the Core specification, this Appendix will change and grow as new common properties are added by the Core workgroup. The properties that we list here are available for use in OSLC specification in defining OSLC resources, but this does not mean that they are required to be in OSLC resources. OSLC domain specifications decide which properties are allowed and required for each resource use case.

Dublin Core Properties

These are the Dublin Core Metadata Element Set properties that are considered common (reference: Dublin Core).

• Namespace URI: http://purl.org/dc/terms/
• Suggested Namespace Prefix: dcterms

RDF Properties

These are the RDF/XML properties that are considered common.

• Namespace URI: http://www.w3.org/1999/02/22-rdf-syntax-ns#
• Suggested Namespace Prefix: rdf

RDFS Properties

These are the RDFS properties that are considered common.

• Namespace URI: http://www.w3.org/2000/01/rdf-schema#
• Suggested Namespace Prefix: rdf

OSLC Properties

These are the OSLC defined properties that are considered common.

• Namespace URI: http://open-services.net/ns/core#
• Suggested Namespace Prefix: oslc

foaf:Person Resource

Person is a common resource because a Person resource is required as the value for a dcterms:creator or dcterms:contributor property.

• Resource: foaf:Person
• Namespace URI: http://xmlns.com/foaf/0.1/ (reference: FOAF)
• Suggested Namespace Prefix: foaf

OSLC adds one additional constraint for foaf:Person. Each foaf:Person resource SHOULD specify either a non-empty foaf:name value or both a non-empty foaf:givenName and foaf:familyName values.

oslc:ResourceShape Resource

In some cases, to create resources and to query those that already exist within an OSLC Service, OSLC clients needs a way to learn which properties are commonly used in or required by the service. Resource Shape Resources meet this need by providing a machine-readable definition of an OSLC resource type. An OSLC Creation Factory MAY provide a Resource Shape so that you know what properties are allowed and required to create a resource. An OSLC Query Capability MAY provide a Resource Shape so that you know what properties are available for query. Within a Resource Shape, a resource value-type MAY provide its own Resource Shape.

Resource Shapes are intended to provide simple "hints" to clients at resource creation, update or query time. They are not intended to form a rigid constraint system for validating inputs or a schema system that can be used for generating "bindings" for programming languages.

OSLC implementations that provide Resource Shapes representing resources defined by OSLC specifications SHOULD provide the very same information provided in the specifications without changing or removing any of the Properties specified. Resource Shapes MAY include new implementation specific properties as long as such "custom" properties are defined in non-OSLC namespaces (i.e. not rooted at http://open-services.net).

Conceptual Model

A Resource Shape describes the properties that are allowed or required by one type of resource. It does not define the properties, but it does tell how the properties are to be used in OSLC for one or more specific scenarios: the value-type to be used for the property, the number of times the property is expected to occur and whether the property is required. As you can see in the exemplary diagram below a Resource Shape provides Properties, and Properties which have Resource value-types can specify their own shapes.

The next sections define the Resource Shape and Property resources.

Resource: Resource Shape

A Resource Shape resource can have a title and a type.

• Resource: oslc:ResourceShape
• Namespace URI: http://open-services.net/ns/core#
• Suggested Namespace Prefix: oslc

Resource: Allowed Values

Allowed values for one property.

• Resource: oslc:AllowedValues
• Namespace URI: http://open-services.net/ns/core#
• Suggested Namespace Prefix: oslc

Value-type: Property

A Property resource describes one allowed or required property of a resource.

• Resource: oslc:Property
• Namespace URI: http://open-services.net/ns/core#
• Suggested Namespace Prefix: oslc

Allowed values for oslc:valueType:

• Literal value-types
  • Boolean - http://www.w3.org/2001/XMLSchema#boolean
  • DateTime - http://www.w3.org/2001/XMLSchema#dateTime
  • Decimal - http://www.w3.org/2001/XMLSchema#decimal
  • Double - http://www.w3.org/2001/XMLSchema#double
  • Float - http://www.w3.org/2001/XMLSchema#float
  • Integer - http://www.w3.org/2001/XMLSchema#integer
  • String - http://www.w3.org/2001/XMLSchema#string
  • XMLLiteral - http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral
• Resource value-types
  • Resource - http://open-service.net/ns/core#Resource
  • Local Resource - http://open-service.net/ns/core#LocalResource
  • Either Resource or Local Resource - http://open-service.net/ns/core#AnyResource

oslc:Comment Resource

A Comment resource represents a single note, or comment, in a discussion thread.

• Resource: oslc:Comment
• Namespace URI: http://open-services.net/ns/core#
• Suggested Namespace Prefix: oslc

oslc:Discussion Resource

A Discussion resource is intended to represent a sequence of comments or notes regarding the associated resource.

• Resource: oslc:Discussion
• Namespace URI: http://open-services.net/ns/core#
• Suggested Namespace Prefix: oslc