Purpose

This specification describes how the XML format is used to represent OSLC resources and collection of resources.

Notation and Conventions

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC2119. Domain name examples use RFC2606.

Terminology

Intro

Overall Structure

The XML format follows these RDF conventions so that it can be parsed by RDF-XML parsers:

• rdf.about on root element (which references itself),
• instead of the "href" attribute the "rdf.resource" attribute is used,
• when inlining resources, an intermediate "Type" attribute is introduced.

Collections

Collections of resources like the result set returned from a query are represented as an JSON array of JSON dictionaries. To allow for the next and previous links used in paged query result, the array is embedded in one additional JSON dictionary.

Examples

The following examples were produced by RTC 2.0 M3D1? . The corresponding JSON version is shown at the bottom of this page? .

This example shows a non-inlined RTC work item in XML format.

For the second example inlining was requested for all first level reference attributes.

-- AndreWeinand - 24 Mar 2009