This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.

OSLC Core Appendix A: Common Properties DRAFT

By: The OSLC Core Workgroup

Overview

This is a list of common properties and resources defined by the Core spec for use in OSLC Defined Resources. OSLC Workgroups are encouraged to consult this list when defining new resources and make use of common properties where appropriate.

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: dc

Prefixed Name Type Typically Occurs Title Description
dc:title XMLLiteral exactly-one Title Title (reference: Dublin Core) of the resource represented as rich text in XHTML content. SHOULD include only content that is valid inside an XHTML <span> element.
dc:description XMLLiteral at-most-one Description 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.
dc:identifier String exactly-one Identifier A unique identifier for a resource. Typically read-only and assigned by the service provider when a resource is created. Not typically intended for end-user display -- it is often accompanied by a dc:name property.
dc:name XMLLiteral at-most-one Name Short name identifying a resource, often used as an abbreviated identifier for presentation to end-users. SHOULD include only content that is valid inside an XHTML <span> element.
dc:subject String zero-or-many Subject Tag or keyword for a resource. Each occurrence of a dc:subject property denotes an additional tag for the resource.
dc:creator Resource or Local Inline Resource of type foaf:Person zero-or-many Creator Creator or creators of resource (reference: Dublin Core)
dc:contributor Resource or Local Inline Resource of type foaf:Person zero-or-many Contributor Contributor or contributors to resource (reference: Dublin Core)
dc:created Date Time at-most-one Created Timestamp of resource creation (reference: Dublin Core)
dc:modified Date Time at-most-one Modified Timestamp last latest resource modification (reference: Dublin Core)

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

Prefixed Name Type Typically Occurs Title Description
rdf:type Resource one-or-many Type The resource type URIs

OSLC Properties

These are the OSLC defined properties that are considered common.

  • Namespace URI: http://open-services.net/xmlns/oslc#
  • Suggested Namespace Prefix: <font face="'Courier New', courier, monaco, monospace" style="font-size: 16px" class="Apple-style-span" size="4">oslc</font>

Prefixed Name Type Typically Occurs Title Description
oslc:serviceProvider Resource of type ServiceProvider zero-or-many Service Provider The scope of a resource is a link to the resource's OSLC Service Provider.
oslc:instanceShape Resource of type ResourceShape at-most-one Instance Shape Resource Shape that specifies allowed and required fields.

Common Resource definitions

The OSLC Core specification may define common resource definitions, available for use in OSLC domain specifications as value-types. Currently, there is only one common resource: Person. Person is a common resource because a Person resource is required as the value for a dc:creator or dc:contributor property.

  • Name: Person
  • Suggested Prefix: foaf
  • Namespace URI: http://xmlns.com/foaf/0.1/ (reference: FOAF)
  • Properties
    • foaf:name (String, zero-or-one) - the full name of a person expressed as simple text string.
    • foaf:givenName (String, zero-or-one) - given name of person expressed as simple text string.
    • foaf:familyName (String, zero-or-one) - family name of person expressed as simple text string.
    • Other properties MAY be specified by OSLC Services

There is an additional constraint for foaf:Person. Implementations MUST specify either a non-empty foaf:name value or both a non-empty foaf:givenName and foaf:familyName values.

Edit | Attach | Print version | History: r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 07 May 2010 - 16:34:23 - ScottBosworth
Main.OslcCoreSpecDRAFTCommonProperties moved from Main.OSLCCoreSpecDRAFTCommonProperties on 07 May 2010 - 16:34 by ScottBosworth - put it back
 
This site is powered by the TWiki collaboration platform Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback