ORE User Guide - Resource Map Implementation in RDF/XML

Abstract

Open Archives Initiative Object Reuse and Exchange (OAI-ORE) defines standards for the description and exchange of Aggregations of Web resources. OAI-ORE introduces the notion of a Resource Map, a named RDF Graph [RDF Concepts] which describes the Aggregation, the Aggregated Resources of which it is composed, and the relationships between them (and/or the relationships between these and other resources). Since a Resource Map is an RDF Graph, it can be serialized using any RDF syntax. This document outlines the use of one such syntax for the serialization of Resource Maps: RDF/XML [RDF/XML]. A companion document outlines the serialization of Resource Maps in RDFa [RDFa Syntax]. This is one of several documents comprising the OAI-ORE specification and user guide.

1. Introduction

The Open Archives Initiative Object Reuse and Exchange (OAI-ORE) [Abstract Data Model] introduces the notion of a Resource Map, a named RDF Graph [RDF Concepts, Named Graph] which describes an Aggregation, the Aggregated Resources of which it is composed, and the relationships between them (and/or the relationships between these and other resources). Since a Resource Map is an RDF Graph, it can be serialized using any RDF syntax. This document outlines the use of one such syntax for the serialization of Resource Maps: RDF/XML [RDF/XML]. The Internet media type / MIME type for RDF/XML is application/rdf+xml. Where RDF/XML is used to provide representations of ORE Resource Maps that media type MUST be used.

The RDF/XML specification [RDF/XML] describes an XML format for serializing RDF graphs. In order to represent an RDF Graph as an XML document the constructs of the RDF Graph (triples made up of subjects, predicates and objects) have to be represented as components in that XML document, i.e. as XML elements and XML attributes, XML element names and XML attribute names, and as XML element content and XML attribute values. The RDF/XML specification describes such a mapping between the RDF Graph and the XML Infoset [XML Infoset].

For some features of the RDF Graph, the RDF/XML syntax permits the encoding of a single feature in multiple ways in XML. The aim of this document is to provide a RECOMMENDED profile of RDF/XML for encoding an ORE Resource Map. However, It is possible to use RDF/XML to encode the same ORE Resource Map using a different set of conventions permitted by RDF/XML. A consumer of ORE Resource Maps encoded in RDF/XML MUST support all of the syntactic conventions defined by RDF/XML. This allowance for different syntactic conventions is supported by conformant RDF/XML parsers.

1.1 Notational Conventions

The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [IETF RFC 2119].

This specification uses the common term URI to mean both IRI [RFC3987] and URI [RFC3986].

1.2 Namespaces

This specification uses the following namespaces and prefixes to indicate those namespaces:

Prefix	Namespace URI	Description
`dc`	`http://purl.org/dc/elements/1.1/`	Dublin Core elements
`dcterms`	`http://purl.org/dc/terms/`	Dublin Core terms
`foaf`	`http://xmlns.com/foaf/0.1/`	FOAF vocabulary terms
`marcrel`	`http://www.loc.gov/loc.terms/relators/`	MARC Relator vocabulary terms
`ore`	`http://www.openarchives.org/ore/terms/`	ORE vocabulary terms
`rdf`	`http://www.w3.org/1999/02/22-rdf-syntax-ns#`	RDF vocabulary terms
`rdfs`	`http://www.w3.org/2000/01/rdf-schema#`	RDFS vocabulary terms

2. Summary of Recommended ORE RDF/XML Syntax

The general convention used in RDF/XML is that the set of subject-predicate-object triples is represented as sequences of XML elements corresponding to the subject of one or more triples (node elements) containing child XML elements corresponding to predicates (property elements) the attributes and/or content of which correspond to the objects. Since the object of one triple may itself be the subject of another triple, that pattern can be repeated, with the consequence that this convention is sometimes referred to as "striping". Neither the order of node elements within the root element, nor the order of property elements within the node element, is significant.

This document describes a convention for encoding Resource Maps in RDF/XML where this striping is limited to one "level" i.e. a node element contains child property elements but those property elements do not contain further node elements. The exception to this one level striping is when the object of a triple is a "blank node", or "bNode". In this case any subsequent triples where that object bNode is a subject are nested in the "stripe" corresponding to the subject of the original triple. Note that bNodes are not mandated by the ORE data model, but MAY occur in some triples, for example when asserting the creator of a Resource Map, where no URI is available for the specified agent.

Also, in the conventions used here, a node element always has the XML expanded name ("http://www.w3.org/1999/02/22-rdf-syntax-ns#", "Description"), typically represented by the QName rdf:Description, where the prefix rdf is associated via an XML namespace declaration with the namespace name http://www.w3.org/1999/02/22-rdf-syntax-ns#. In other words, these examples do not make use of RDF/XML's "typed node element" convention: triples with the predicate http://www.w3.org/1999/02/22-rdf-syntax-ns#type are always represented using property elements.

In the remainder of this document, the names of XML elements are cited as XML QNames. An XML QName is an abbreviation for an expanded name, a pair consisting of an XML Namespace Name (a URI) and a local name. The prefix part of the XML QName is bound to an XML Namespace Name through an XML Namespace declaration; where an XML QName has no prefix, the XML Namespace Name is obtained from the default namespace declaration. Where an XML QName is used to represent a URI in RDF/XML, the URI is determined by appending the local name part of the QName to the XML Namespace Name. For example, using the mapping provided in the section above on Namepaces, the QName ore:describes maps to the URI http://www.openarchives.org/ore/terms/describes. Note that the prefix used in the QNames in this document should not be interpreted as significant; any prefix can be used as long as the QName corresponds to the XML expanded name would be generated using the prefix/namespace name pairs listed in the section above on Namepaces.

As demonstrated by the examples in the remainder of this document the recommended rules for encoding a Resource Map in RDF/XML are:

Create a root element with the QName rdf:RDF
SubjectRule: For each distinct subject in the Resource Map that is not a bNode:
- Create a node element (i.e. an XML element with the QName rdf:Description) as child element of the root element and add an attribute with the QName rdf:about and make the value of this attribute a URI reference corresponding to the subject
- ObjectRule: For each triple in the Resource Map with this subject
  - ObjectRule: Create a property element as child element of the node element. The name of the property element is derived from the URI reference which forms the predicate of the triple, following the URI-QName mapping convention described in section 2.1 of the RDF/XML specification.
  - If the object of the triple is a URI reference, add an attribute with the QName rdf:resource and make the value of this attribute a URI reference corresponding to the object. In this case, the property element is empty.
  - If the object of the triple is a literal
    - For a plain literal, make the lexical form the content of the property element. If a language tag is present, add an attribute with the QName xml:lang and make the value of this attribute the language tag
    - For a typed literal, make the lexical form the content of the property element, and add an attribute with the QName rdf:datatype and make the value of this attribute a URI reference corresponding to the URI of the datatype
    - For an XML literal i.e. a typed literal with the datatype http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral, make the lexical form the content of the property element, and add an attribute with the QName rdf:parseType and make the value of this attribute the string "Literal"
  - If the object of the triple is a bNode
    - Add an attribute to the property element with the QName rdf:parseType and make the value of this attribute the string "Resource".
    - Follow ObjectRule above, with the bNode as subject.

3. Examples of Resource Maps Encoded in RDF/XML

The remainder of this section uses the an e-print in arXiv with a "splash page" at http://arxiv.org/abs/astro-ph/0601007 to illustrate the RECOMMENDED RDF/XML encoding of a Resource Map. This is an interesting example because it has multiple identifiers, versions, formats, mirrors and external relationships. For illustrative purposes, the example diverges from the real e-print in arXiv in the manner that it associates an aggregation of data with the e-print.

These examples use the following URIs for the Aggregation (URI-A) and Resource Map (URI-R). As specified, the URI-A of an Aggregation should be distinct from the URI of a splash page.

URI-A: http://arxiv.org/astro-ph/0601007#aggregation
URI-R: http://arxiv.org/astro-ph/0601007/foo.rdf

The ordering of the following subsections correspond to that used to introduce features in the Abstract Data Model Specification [Abstract Data Model]. Each section header links to the corresponding Abstract Data Model section. The examples are not intended to be exhaustive, but sufficient to demonstrate the recommended RDF/XML syntax.

This complete example is illustrated in the following figure. The table after the figure lists the URIs of Resources in the example.

3.1 Relationship between a Resource Map and an Aggregation

A Resource Map MUST include one triple with an ore:describes predicate. The subject of this triple MUST be the URI-R of the Resource Map. The object is the URI-A of the Aggregation described by the Resource Map.

The triples corresponding to the example are:

Subject	Predicate	Object
http://arxiv.org/astro-ph/0601007/foo.rdf	`ore:describes`	http://arxiv.org/astro-ph/0601007#aggregation
http://arxiv.org/astro-ph/0601007#aggregation	`ore:isDescribedy`	http://arxiv.org/astro-ph/0601007/foo.atom

These triples SHOULD be serialized in RDF/XML as follows:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
        xmlns:ore="http://www.openarchives.org/ore/terms/">
  <rdf:Description rdf:about="http://arxiv.org/astro-ph/0601007/foo.rdf">
    <ore:describes rdf:resource="http://arxiv.org/astro-ph/0601007#aggregation" />
  </rdf:Description>
  <rdf:Description rdf:about="http://arxiv.org/astro-ph/0601007#aggregation">
    <ore:isDescribedBy rdf:resource="http://arxiv.org/astro-ph/0601007/foo.atom" />
  </rdf:Description>
</rdf:RDF>

[RDF/XML, NTriples via Triplr]

Note: The use of bold in the RDF/XML above indicates the segment of the XML that corresponds to the triples in the table that immediately preceeds the example. This visual cue will be used throughout this document.

3.2 Metadata about the Resource Map and Aggregation

A Resource Map MUST include triples expressing minimal metadata properties about the Resource Map. It MAY include triples expressing additional metadata properties about the Resource Map. Finally it MAY include triples expressing metadata properties about the Aggregation.

The triples corresponding to the example are:

Subject	Predicate	Object
http://arxiv.org/astro-ph/0601007/foo.rdf	`dcterms:creator`	`http://my.example.org/agents/AgencyX`
`http://my.example.org/agents/AgencyX`	foaf:name	"The best ReM Agent"
http://arxiv.org/astro-ph/0601007/foo.rdf	`dcterms:modified`	`"2008-02-12"^^ http://www.w3.org/2001/XMLSchema#date`
http://arxiv.org/astro-ph/0601007#aggregation	`dcterms:creator`	bNode
bNode	foaf:name	"Hui Li"

Note the introduction of a bnode for the dcterms:creator of the aggregation - where there is no available URI for the agent "Hui Li".

These triples SHOULD be serialized in RDF/XML as follows:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:ore="http://www.openarchives.org/ore/terms/" xmlns:dcterms="http://purl.org/dc/terms/"
         xmlns:foaf="http://xmlns.com/foaf/0.1/">
    <rdf:Description rdf:about="http://arxiv.org/astro-ph/0601007/foo.rdf">
        <ore:describes rdf:resource="http://arxiv.org/astro-ph/0601007#aggregation"/>
        <dcterms:creator rdf:resource="http://my.example.org/agents/AgencyX"/>
        <dcterms:modified rdf:datatype="http://www.w3.org/2001/XMLSchema#date"
          >2008-02-12</dcterms:modified>
    </rdf:Description>
    <rdf:Description rdf:about="http://arxiv.org/astro-ph/0601007#aggregation">
        <ore:isDescribedBy rdf:resource="http://arxiv.org/astro-ph/0601007/foo.atom"/>
        <dcterms:creator rdf:parseType="Resource">
            <foaf:name>Hui Li</foaf:name>
        </dcterms:creator>
    </rdf:Description>
    <rdf:Description rdf:about="http://my.example.org/agents/AgencyX">
        <foaf:name>The Best ReM Agent</foaf:name>
    </rdf:Description>
</rdf:RDF>

[RDF/XML, NTriples via Triplr]

3.3 Aggregated Resources and Aggregation Graph

A Resource Map MAY include one or more triples describing the relationship between the Aggregation and Aggregated Resources.

The triples corresponding to the example are:

Subject	Predicate	Object
http://arxiv.org/astro-ph/0601007#aggregation	`ore:aggregates`	http://arxiv.org/ps/astro-ph/0601007
http://arxiv.org/astro-ph/0601007#aggregation	`ore:aggregates`	http://arxiv.org/pdf/astro-ph/0601007
http://arxiv.org/astro-ph/0601007#aggregation	`ore:aggregates`	http://arxiv.org/e-print/astro-ph/0601007

These triples SHOULD be serialized in RDF/XML as follows:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:ore="http://www.openarchives.org/ore/terms/" xmlns:dcterms="http://purl.org/dc/terms/"
    xmlns:foaf="http://xmlns.com/foaf/0.1/">
    <rdf:Description rdf:about="http://arxiv.org/astro-ph/0601007/foo.rdf">
        <ore:describes rdf:resource="http://arxiv.org/astro-ph/0601007#aggregation"/>
        <dcterms:creator rdf:resource="http://my.example.org/agents/AgencyX"/>
        <dcterms:modified rdf:datatype="http://www.w3.org/2001/XMLSchema#date"
        >2008-02-12</dcterms:modified>
    </rdf:Description>
    <rdf:Description rdf:about="http://arxiv.org/astro-ph/0601007#aggregation">
        <ore:isDescribedBy rdf:resource="http://arxiv.org/astro-ph/0601007/foo.atom"/>
        <dcterms:creator rdf:parseType="Resource">
            <foaf:name>Hui Li</foaf:name>
        </dcterms:creator>
        <ore:aggregates rdf:resource="http://arxiv.org/ps/astro-ph/0601007"/>
        <ore:aggregates rdf:resource="http://arxiv.org/pdf/astro-ph/0601007"/>
        <ore:aggregates rdf:resource="http://arxiv.org/e-print/astro-ph/0601007"/>
    </rdf:Description>
    <rdf:Description rdf:about="http://my.example.org/agents/AgencyX">
        <foaf:name>The Best ReM Agent</foaf:name>
    </rdf:Description>
</rdf:RDF>

[RDF/XML, NTriples via Triplr]

3.4 Relationships between the Aggregation and Similar Resources

A Resource Map MAY include one or more triples, with URI-A as the subject, which assert that the Aggregation is a Resource with content that is similar to another Resource. The predicate MAY be either rdfs:seeAlso or its sub-property ore:similarTo.

The triples corresponding to the example are:

Subject	Predicate	Object
http://arxiv.org/astro-ph/0601007#aggregation	`rdfs:seeAlso`	`info:arXiv/astro-ph/0601007v2`
http://arxiv.org/astro-ph/0601007#aggregation	`ore:similarTo`	`info:doi/10.1142/S0217732306019475`

These triples SHOULD be serialized in RDF/XML as follows:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:ore="http://www.openarchives.org/ore/terms/" xmlns:dcterms="http://purl.org/dc/terms/"
    xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
    <rdf:Description rdf:about="http://arxiv.org/astro-ph/0601007/foo.rdf">
        <ore:describes rdf:resource="http://arxiv.org/astro-ph/0601007#aggregation"/>
        <dcterms:creator rdf:resource="http://my.example.org/agents/AgencyX"/>
        <dcterms:modified rdf:datatype="http://www.w3.org/2001/XMLSchema#date"
        >2008-02-12</dcterms:modified>
    </rdf:Description>
    <rdf:Description rdf:about="http://arxiv.org/astro-ph/0601007#aggregation">
        <ore:isDescribedBy rdf:resource="http://arxiv.org/astro-ph/0601007/foo.atom"/>
        <dcterms:creator rdf:parseType="Resource">
            <foaf:name>Hui Li</foaf:name>
        </dcterms:creator>
        <ore:aggregates rdf:resource="http://arxiv.org/ps/astro-ph/0601007"/>
        <ore:aggregates rdf:resource="http://arxiv.org/pdf/astro-ph/0601007"/>
        <ore:aggregates rdf:resource="http://arxiv.org/e-print/astro-ph/0601007"/>
        <rdfs:seeAlso rdf:resource="info:arXiv/astro-ph/0601007v2"/>
        <ore:similarTo rdf:resource="info:doi/10.1142/S0217732306019475"/>
    </rdf:Description>
    <rdf:Description rdf:about="http://my.example.org/agents/AgencyX">
        <foaf:name>The Best ReM Agent</foaf:name>
    </rdf:Description>
</rdf:RDF>

[RDF/XML, NTriples via Triplr]

3.5 Relationships to other Resources and Types

A Resource Map MAY include additional triples that assert properties about the Resource Map, Aggregation, Aggregated Resources, or other related Resources or Literals.

The triples corresponding to the example are:

Subject	Predicate	Object
http://arxiv.org/astro-ph/0601007#aggregation	`dcterms:references`	`info:doi/10.1086/300499`
http://arxiv.org/astro-ph/0601007#aggregation	`dcterms:references`	info:doi/10.1103/PhysRevD.72.083511
http://arxiv.org/pdf/astro-ph/0601007	`rdf:type`	`http://purl.org/dc/dcmitype/Text`
http://arxiv.org/astro-ph/0601007#aggregation	rdf:type	http://purl.og/eprint/type/JournalArticle

These triples SHOULD be serialized in RDF/XML as follows:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:ore="http://www.openarchives.org/ore/terms/" xmlns:dcterms="http://purl.org/dc/terms/"
    xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
    <rdf:Description rdf:about="http://arxiv.org/astro-ph/0601007/foo.rdf">
        <ore:describes rdf:resource="http://arxiv.org/astro-ph/0601007#aggregation"/>
        <dcterms:creator rdf:resource="http://my.example.org/agents/AgencyX"/>
        <dcterms:modified rdf:datatype="http://www.w3.org/2001/XMLSchema#date"
        >2008-02-12</dcterms:modified>
    </rdf:Description>
    <rdf:Description rdf:about="http://arxiv.org/astro-ph/0601007#aggregation">
        <ore:isDescribedBy rdf:resource="http://arxiv.org/astro-ph/0601007/foo.atom"/>
        <dcterms:creator rdf:parseType="Resource">
            <foaf:name>Hui Li</foaf:name>
        </dcterms:creator>
        <ore:aggregates rdf:resource="http://arxiv.org/ps/astro-ph/0601007"/>
        <ore:aggregates rdf:resource="http://arxiv.org/pdf/astro-ph/0601007"/>
        <ore:aggregates rdf:resource="http://arxiv.org/e-print/astro-ph/0601007"/>
        <rdfs:seeAlso rdf:resource="info:arXiv/astro-ph/0601007v2"/>
        <ore:similarTo rdf:resource="info:doi/10.1142/S0217732306019475"/>
        <rdf:type rdf:resource="http://purl.og/eprint/type/JournalArticle"/>
        <dcterms:references rdf:resource="info:doi/10.1086/30049"/>
        <dcterms:references rdf:resource="info:doi/10.1103/PhysRevD.72.083511"/>
    </rdf:Description>
    <rdf:Description rdf:about="http://my.example.org/agents/AgencyX">
        <foaf:name>The Best ReM Agent</foaf:name>
    </rdf:Description>
    <rdf:Description rdf:about="http://arxiv.org/pdf/astro-ph/0601007">
        <rdf:type rdf:resource="http://purl.org/dc/dcmitype/Text"/>
    </rdf:Description>
</rdf:RDF>

[RDF/XML, NTriples via Triplr]

3.6 Asserting that an Aggregated Resource is a constituent of another Aggregation

A Resource Map MAY include one or more triples with the ore:isAggregatedBy predicate to assert that an Aggregated Resources is a constituent of other Aggregations.

The triple corresponding to the example is:

Subject	Predicate	Object
http://arxiv.org/ps/astro-ph/0601007	`ore:isAggregatedBy`	`http://your.example.org/aggregation-2`

These triples SHOULD be serialized in RDF/XML as follows:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:ore="http://www.openarchives.org/ore/terms/" xmlns:dcterms="http://purl.org/dc/terms/"
    xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
    <rdf:Description rdf:about="http://arxiv.org/astro-ph/0601007/foo.rdf">
        <ore:describes rdf:resource="http://arxiv.org/astro-ph/0601007#aggregation"/>
        <dcterms:creator rdf:resource="http://my.example.org/agents/AgencyX"/>
        <dcterms:modified rdf:datatype="http://www.w3.org/2001/XMLSchema#date"
            >2008-02-12</dcterms:modified>
    </rdf:Description>
    <rdf:Description rdf:about="http://arxiv.org/astro-ph/0601007#aggregation">
        <ore:isDescribedBy rdf:resource="http://arxiv.org/astro-ph/0601007/foo.atom"/>
        <dcterms:creator rdf:parseType="Resource">
            <foaf:name>Hui Li</foaf:name>
        </dcterms:creator>
        <ore:aggregates rdf:resource="http://arxiv.org/ps/astro-ph/0601007"/>
        <ore:aggregates rdf:resource="http://arxiv.org/pdf/astro-ph/0601007"/>
        <ore:aggregates rdf:resource="http://arxiv.org/e-print/astro-ph/0601007"/>
        <rdfs:seeAlso rdf:resource="info:arXiv/astro-ph/0601007v2"/>
        <ore:similarTo rdf:resource="info:doi/10.1142/S0217732306019475"/>
        <rdf:type rdf:resource="http://purl.og/eprint/type/JournalArticle"/>
        <dcterms:references rdf:resource="info:doi/10.1086/30049"/>
        <dcterms:references rdf:resource="info:doi/10.1103/PhysRevD.72.083511"/>
    </rdf:Description>
    <rdf:Description rdf:about="http://my.example.org/agents/AgencyX">
        <foaf:name>The Best ReM Agent</foaf:name>
    </rdf:Description>
    <rdf:Description rdf:about="http://arxiv.org/pdf/astro-ph/0601007">
        <rdf:type rdf:resource="http://purl.org/dc/dcmitype/Text"/>
    </rdf:Description>
    <rdf:Description rdf:about="http://arxiv.org/ps/astro-ph/0601007">
        <ore:isAggregatedBy rdf:resource="http://your.example.org/aggregation-2"/>
    </rdf:Description>
</rdf:RDF>

[RDF/XML, NTriples via Triplr]

3.7 Nesting Aggregations

A Resource Map that asserts another Aggregation as an Aggregated Resource MAY assert an ore:isDescribedBy relationship between this Aggregated Resource and a Resource Map describing the other Aggregation.

The triples corresponding to the example are:

Subject	Predicate	Object
http://arxiv.org/astro-ph/0601007#aggregation	`ore:aggregates`	http://mydata.org/dataSet
http://mydata.org/dataSet	ore:isDescribedBy	http://mydata.org/dataSet/rem.rdf

These triples SHOULD be serialized in RDF/XML as follows:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:ore="http://www.openarchives.org/ore/terms/" xmlns:dcterms="http://purl.org/dc/terms/"
    xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
    <rdf:Description rdf:about="http://arxiv.org/astro-ph/0601007/foo.rdf">
        <ore:describes rdf:resource="http://arxiv.org/astro-ph/0601007#aggregation"/>
        <dcterms:creator rdf:resource="http://my.example.org/agents/AgencyX"/>
        <dcterms:modified rdf:datatype="http://www.w3.org/2001/XMLSchema#date"
            >2008-02-12</dcterms:modified>
    </rdf:Description>
    <rdf:Description rdf:about="http://arxiv.org/astro-ph/0601007#aggregation">
        <ore:isDescribedBy rdf:resource="http://arxiv.org/astro-ph/0601007/foo.atom"/>
        <dcterms:creator rdf:parseType="Resource">
            <foaf:name>Hui Li</foaf:name>
        </dcterms:creator>
        <ore:aggregates rdf:resource="http://arxiv.org/ps/astro-ph/0601007"/>
        <ore:aggregates rdf:resource="http://arxiv.org/pdf/astro-ph/0601007"/>
        <ore:aggregates rdf:resource="http://arxiv.org/e-print/astro-ph/0601007"/>
        <ore:aggregates rdf:resource="http://mydata.org/dataSet"/>
        <rdfs:seeAlso rdf:resource="info:arXiv/astro-ph/0601007v2"/>
        <ore:similarTo rdf:resource="info:doi/10.1142/S0217732306019475"/>
        <rdf:type rdf:resource="http://purl.og/eprint/type/JournalArticle"/>
        <dcterms:references rdf:resource="info:doi/10.1086/30049"/>
        <dcterms:references rdf:resource="info:doi/10.1103/PhysRevD.72.083511"/>
    </rdf:Description>
    <rdf:Description rdf:about="http://my.example.org/agents/AgencyX">
        <foaf:name>The Best ReM Agent</foaf:name>
    </rdf:Description>
    <rdf:Description rdf:about="http://arxiv.org/pdf/astro-ph/0601007">
        <rdf:type rdf:resource="http://purl.org/dc/dcmitype/Text"/>
    </rdf:Description>
    <rdf:Description rdf:about="http://arxiv.org/ps/astro-ph/0601007">
        <ore:isAggregatedBy rdf:resource="http://your.example.org/aggregation-2"/>
    </rdf:Description>
    <rdf:Description rdf:about="http://mydata.org/dataSet">
        <ore:isDescribedBy rdf:resource="http://mydata.org/dataSet/rem.rdf"/>
    </rdf:Description>
</rdf:RDF>

[RDF/XML, NTriples via Triplr]

3.8 Proxies for Aggregated Resources

A Proxy is a Resource that "stands for" an Aggregated Resource in a manner that is specific to one Aggregation. A Resource Map MAY assert one Proxy for any Aggregated Resource asserted by the Resource Map.

The triples corresponding to the example are:

Subject	Predicate	Object
http://oreproxy.org/r?what=http://arxiv.org/ps/astro-ph/0601007&where=http://arxiv.org/rem/astro-ph/0601007%23aggregation	`ore:proxyFor`	http://arxiv.org/ps/astro-ph/0601007
http://oreproxy.org/r?what=http://arxiv.org/ps/astro-ph/0601007&where=http://arxiv.org/rem/astro-ph/0601007%23aggregation	`ore:proxyIn`	http://arxiv.org/astro-ph/0601007#aggregation

These triples SHOULD be serialized in RDF/XML as follows:

<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:ore="http://www.openarchives.org/ore/terms/" xmlns:dcterms="http://purl.org/dc/terms/"
    xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
    <rdf:Description rdf:about="http://arxiv.org/astro-ph/0601007/foo.rdf">
        <ore:describes rdf:resource="http://arxiv.org/astro-ph/0601007#aggregation"/>
        <dcterms:creator rdf:resource="http://my.example.org/agents/AgencyX"/>
        <dcterms:modified rdf:datatype="http://www.w3.org/2001/XMLSchema#date"
            >2008-02-12</dcterms:modified>
    </rdf:Description>
    <rdf:Description rdf:about="http://arxiv.org/astro-ph/0601007#aggregation">
        <ore:isDescribedBy rdf:resource="http://arxiv.org/astro-ph/0601007/foo.atom"/>
        <dcterms:creator rdf:parseType="Resource">
            <foaf:name>Hui Li</foaf:name>
        </dcterms:creator>
        <ore:aggregates rdf:resource="http://arxiv.org/ps/astro-ph/0601007"/>
        <ore:aggregates rdf:resource="http://arxiv.org/pdf/astro-ph/0601007"/>
        <ore:aggregates rdf:resource="http://arxiv.org/e-print/astro-ph/0601007"/>
        <ore:aggregates rdf:resource="http://mydata.org/dataSet"/>
        <rdfs:seeAlso rdf:resource="info:arXiv/astro-ph/0601007v2"/>
        <ore:similarTo rdf:resource="info:doi/10.1142/S0217732306019475"/>
        <rdf:type rdf:resource="http://purl.og/eprint/type/JournalArticle"/>
        <dcterms:references rdf:resource="info:doi/10.1086/30049"/>
        <dcterms:references rdf:resource="info:doi/10.1103/PhysRevD.72.083511"/>
    </rdf:Description>
    <rdf:Description rdf:about="http://my.example.org/agents/AgencyX">
        <foaf:name>The Best ReM Agent</foaf:name>
    </rdf:Description>
    <rdf:Description rdf:about="http://arxiv.org/pdf/astro-ph/0601007">
        <rdf:type rdf:resource="http://purl.org/dc/dcmitype/Text"/>
    </rdf:Description>
    <rdf:Description rdf:about="http://arxiv.org/ps/astro-ph/0601007">
        <ore:isAggregatedBy rdf:resource="http://your.example.org/aggregation-2"/>
    </rdf:Description>
    <rdf:Description rdf:about="http://mydata.org/dataSet">
        <ore:isDescribedBy rdf:resource="http://mydata.org/dataSet/rem.rdf"/>
    </rdf:Description>
    <rdf:Description rdf:about="http://oreproxy.org/r?what=http://arxiv.org/ps/astro-ph/0601007&amp;where=http://arxiv.org/rem/astro-ph/0601007%23aggregation">
        <ore:proxyFor rdf:resource="http://arxiv.org/ps/astro-ph/0601007"/>
        <ore:proxyIn rdf:resource="http://arxiv.org/astro-ph/0601007#aggregation"/>
    </rdf:Description>
</rdf:RDF>

[RDF/XML, NTriples via Triplr]

4. References

[Named Graph]: Named graphs, provenance and trust, J. Carroll, C. Bizer, P. Hayes, P. Stickler, Proceedings of the 14th international conference on World Wide Web, 2005.
[ORE Model]: ORE Specification - Abstract Data Model, C. Lagoze, H. Van de Sompel, M. Nelson, R. Sanderson, S. Warner, 2008-06-02. Available at http://www.openarchives.org/ore/0.9/datamodel.
[RDF Concepts]: Resource Description Framework (RDF): Concepts and Abstract Syntax, Graham Klyne and Jeremy J. Carroll, Editors, W3C Recommendation, 10 February 2004, http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/ . Latest version available at http://www.w3.org/TR/rdf-concepts/ .
[RDFa Syntax]: RDFa in XHTML: Syntax and Processing. A collection of attributes and processing rules for extending XHTML to support RDF , Ben Adida, Mark Birbeck, Shane McCarron and Steven Pemberton, Editors. W3C Editor's Draft, 01 May 2008,
http://www.w3.org/MarkUp/2008/ED-rdfa-syntax-20080501 .
Latest version available at http://www.w3.org/TR/rdfa-syntax/.
[RDFS]: RDF Vocabulary Description Language 1.0: RDF Schema, Dan Brickley and R.V. Guha, Editors. W3C Recommendation, 10 February 2004,
http://www.w3.org/TR/2004/REC-rdf-schema-20040210/ .
Latest version available at http://www.w3.org/TR/rdf-schema/.
[RDFXML]: RDF/XML Syntax Specification (Revised), Dave Beckett and Brian McBrde, Editors. W3C Recommendation, 10 February 2004,
http://www.w3.org/TR/2004/REC-rdf-syntax-grammar-20040210/ .
Latest version available at http://www.w3.org/TR/rdf-syntax-grammar/.
[RFC2119]: IETF RFC 2119: Key words for use in RFCs to Indicate Requirement Levels, S. Bradner, March 1997. Available at http://www.ietf.org/rfc/rfc2119.txt.
[RFC3986]: Uniform Resource Identifier (URI): Generic Syntax, T. Berners-Lee, R. Fielding, L. Masinter, IETF RFC3986, January 2005.
[RFC3987]: Internationalized Resource Identifiers (IRIs), M. Duerst & M. Suignard, IETF RFC3987, January 2005.
[Web Architecture]: Architecture of the World Wide Web, Volume One, I. Jacobs and N. Walsh, Editors, World Wide Web Consortium, 15 January 2004.

Date	Editor	Description
2008-06-02	johnston/lagoze	public beta 0.9 release
2008-02-29	johnston	public alpha 0.2 release (then part of rdfsyntax document)