DO NOT USE, SEE CURRENT ORE SPECIFICATIONS

ORE User Guide - Resource Map Implementation in RDFa

2 June 2008

DO NOT USE THIS SPECIFICATION, see instead the CURRENT ORE SPECIFICATIONS.

This document was part of a beta release and has been superseded.

This version:
http://www.openarchives.org/ore/0.9/rdfa
Latest version:
http://www.openarchives.org/ore/rdfa
Previous version:
http://www.openarchives.org/ore/0.3/rdfsyntax
Editors (OAI Executive)
Carl Lagoze, Cornell University Information Science
Herbert Van de Sompel, Los Alamos National Laboratory
Editors (ORE Technical Committee)
Pete Johnston, Eduserv Foundation
Michael Nelson, Old Dominion University
Robert Sanderson, University of Liverpool
Simeon Warner, Cornell University Information Science

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 RDFa [RDFa Syntax] to serialize Resource Maps. This specification is one of several documents comprising the OAI-ORE specification and user guide.

Table of Contents

1. Introduction
    1.1 Notational Conventions
    1.2 Namespaces
2. Summary of Recommended RDFa Syntax
    2.1 URIs in RDFa
    2.2 Choice of URIs in the Splash Page Scenario
3. Example of a Resource Map Serialized RDFa
    3.1 Relationship between Resource Map and Aggregation
    3.2 Typing of Resource Map
    3.3 Metadata about Resource Map (Required)
    3.4 Metadata about Resource Map (Optional)
    3.5 Metadata about Creator of Resource Map (Optional)
    3.6 Relationship between Aggregation and aggregated Resource(s)
    3.7 Typing of Aggregation
    3.8 Relationships between the Aggregation and Similar Resources
    3.9 Relationships between Aggregation and Other Resources
    3.10 Relationships between aggregated Resources and Other Resources
    3.11 Aggregated Resource as constituent of another Aggregation
    3.12 Nesting Aggregations
    3.13 Additional Relationships in the Resource Map
4. References

Appendices

A. Acknowledgements
B. Change Log

1. Introduction

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, Named Graph] 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 RDFa [RDFa Syntax] to serialize Resource Maps.

The RDFa in XHTML specification [RDFa Syntax] describes how to encode an RDF Graph within an HTML or XHTML document using a set of attributes. RDFa makes use of existing HTML/XHTML markup and content so that the same data which is typically rendered to a human reader is used as the basis of the content of the RDF Graph and the need to repeat content is minimised.

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 RDFa Syntax

The concept of the Resource Map is defined by the ORE Abstract Data Model [ORE_Model]: it is a named RDF Graph, as defined by RDF [RDF Concepts], and the characteristics of an RDF Graph that acts as a Resource Map are described by the ORE Abstract Data Model.

The RDFa syntax [RDFa Syntax] provides some flexibility in the way an RDF Graph is encoded. The aim of this section is not to provide a full description of the RDFa syntax, but rather to provide some recommendations on how the RDFa syntax can be used to encode an ORE Resource Map. It is not a requirement that this particular set of conventions is used. To encode an ORE Resource Map, a provider of ORE Resource Maps MAY use any of the syntactic conventions defined by RDFa. A consumer of ORE Resource Maps encoded in RDFa MUST support all of the syntactic conventions defined by RDFa.

Where an XHTML document containing RDFa is used to serialize an ORE Resource Map, that XHTML+RDFa document MUST be a strictly conforming XHTML+RDFa document as described in section 4 of the RDFa in XHTML specification, i.e.

Simplifying considerably, in RDFa:

The following example is an XHTML+RDFa document (adapted from [RDFa Primer]) constructed according to the rules above.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN"
                      "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:dc="http://purl.org/dc/elements/1.1/"
      xmlns:dcterms="http://purl.org/dc/terms/"
      xmlns:foaf="http://xmlns.com/foaf/0.1/"
      xmlns:cc="http://creativecommons.org/ns#"
      xml:lang="en">
<head profile="http://www.w3.org/1999/xhtml/vocab">
  <title>Alice's Weblog</title>
</head>

<body>
  <div>
    <p>All content on this site is licensed under a <a rel="cc:license" href="http://creativecommons.org/licenses/by/3.0/">Creative Commons License</a>.</p>

    <div class="blog-entry" about="/posts/trouble_with_bob">
      <h2 property="dc:title">The trouble with Bob</h2>

      The trouble with Bob is that he takes much better photos than I do:

      <div about="http://example.com/bob/photos/sunset.jpg">
        <img src="http://example.com/bob/photos/sunset.jpg" />
        <span property="dc:title">Beautiful Sunset</span>
        by <span rel="dcterms:creator">
             <span property="foaf:name">Bob</span>
           </span>.
      </div>
   </div>
  </div>
</body>
</html>

XHTML+RDFa, RDF/XML via RDFa Distiller, NTriples via RDFa Distiller

The XHTML+RDFa document encodes the following RDF triples (assuming the URI of the document is http://example.org/blog/):

Subject Predicate Object
<http://example.org/blog/> cc:license <http://creativecommons.org/licenses/by/3.0/>
<http://example.org/posts/trouble_with_bob> dc:title "The trouble with Bob"
<http://example.com/bob/photos/sunset.jpg> dc:title "Beautiful Sunset"
<http://example.com/bob/photos/sunset.jpg> dcterms:creator <_:bnode1>
<_:bnode1> foaf:name "Bob"

The subject URI of the first triple is the URI of the document; for the three subsequent triples, the subject is determined from the value of the about attribute. The predicates are determined from the values of the rel attribute (in the first and third cases) and the property attribute in the other. The objects are determined from the value of the href attribute (in the first case) and the content of the element with the property attribute in the subsequent cases.

The last two triples illustrate the use of a "blank node" (or "bnode"). Blank nodes MAY occur in ORE Resource Maps when asserting the creator of the Resource Map or contributors to the Aggregation or Aggregated Resources. In the example shown, the creator of the photograph is "Bob", but Bob has no associated URI. Instead the special "_" (underscore) prefix (and an arbitrary local part with no global meaning, in this case bnode1) is used to identify the blank node in the fourth and fifth lines in the table of triples.

Note that this is not intended to be a full description of the RDFa processing rules; for that information, see RDFa in XHTML: Syntax and Processing [RDFa Syntax].

2.1 URIs in RDFa

In RDFa, an RDF URI reference is always encoded as the value of an XML attribute.

The attribute values may take the form of a URI in full or of a relative reference, to be resolved relative to a base URI, either a URI provided by the use of the XHTML base element, or the URI of the document itself.

Some of the attributes used in RDFa also support the encoding of a URI in an abbreviated form as a CURIE or "compact URI". The use of a CURIE allows the author to replace the leading section of a URI with a substitution token which is mapped to a URI. The full URI represented by a CURIE is obtained by concatenating the second part of the CURIE onto the URI to which the substitution token is mapped. The mapping of substitution token to URI is expressed using an XML Namespace declaration. This mechanism is quite similar to that used in RDF/XML to map URIs to XML QNames, with the important difference that the lexical constraints on CURIEs are less stringent than those on QNames, so that any URI can be abbreviated as a CURIE, whereas, as noted above, there are some URIs which can not be mapped to QNames.

The attributes used by RDFa vary in their support for these different ways of representing URIs:

The following three examples (extracted from the RDFa in XHTML Syntax and Processing document [RDFa Syntax]), illustrate three different ways of encoding the URI http://dbpedia.org/resource/Albert_Einstein as the value of the about attribute, in the first case as a URI represented in full, and in the latter two cases as a CURIE

  <div>
    <div about="http://dbpedia.org/resource/Albert_Einstein">

    </div>
  </div>

 

  <div xmlns:db="http://dbpedia.org/">
    <div about="[db:resource/Albert_Einstein]">

    </div>
  </div>

 

  <div xmlns:dbr="http://dbpedia.org/resource/">
    <div about="[dbr:Albert_Einstein]">

    </div>
  </div>

For a full description of the mechanism for mapping CURIEs to URIs, see the section "CURIE and URI Processing" in RDFa in XHTML: Syntax and Processing [RDFa Syntax].

2.2 Choice of URIs in the Splash Page Scenario

One application for RDFa is to encode a Resource Map within a human readable XHTML page describing an Aggregation. In repositories of scholarly documents and other applications, such pages are often referred to as Splash Pages. It is also possible the the Splash Page be included as one of the Aggregated Resources of the Aggregation.

Within the ORE Model, the URI of the Resource Map (URI-R) MUST be distinct from the URI of the Aggregation (URI-A). Similarly the URI of a Splash Page (URI-S) MUST be distinct from the URI of the Aggregation (URI-A).

It is RECOMMENDED that the URI of a Splash Page be distinct from the URI of the Resource Map if the Splash Page is itself an Aggregated Resource. One solution is to extend the use of fragment identifiers from the simple implementation without server support scenario described in [ORE HTTP]. In the example set of URIs below, the fragment identifier #rem is used to distinguish the Resource Map from the Splash Page:

Splash Page:   S-1   = http://example.org/foo.html
Aggregation:   A-1   = http://example.org/foo.html#aggregation
Resource Map:  ReM-1 = http://example.org/foo.html#rem

For further discussion of URI choice with RDFa serialization, see implementation with RDFa or microformats in [ORE HTTP].

3. Example of a Resource Map Serialized RDFa

This section illustrates the use of RDFa by describing elements of the serialization of Resource Map shown as an RDF graph in the figure below.

Example RDF Graph

3.1 Relationship between Resource Map and Aggregation

The relationship between Resource Map and Aggregation is expressed by a single (required) triple in which the subject is the URI of the Resource Map, the predicate is the URI http://www.openarchives.org/ore/terms/describes and the object is the URI of the Aggregation.

In RDFa, this can be expressed using an XHTML element with an about attribute (the value of which provides the subject, the URI of the Resource Map), and nested within that element an a element with a rel attribute with a CURIE value corresponding to the predicate (typically ore:describes) and an href attribute, the value of which provides the object, the URI of the Aggregation).

For the example described in section 3, the relevant triples are:

Subject Predicate Object
http://my.example.org/rem ore:describes http://my.example.org/aggregation
http://my.example.org/aggregation ore:isDescribedBy http://my.example.org/rem

These triples could be expressed in XHTML+RDFa as follows:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN"
                      "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:ore="http://www.openarchives.org/ore/terms/"
      xml:lang="en">
<head profile="http://www.w3.org/1999/xhtml/vocab">
  <title>Resource Map http://my.example.org/rem</title>
</head>

<body>
  <div about="http://my.example.org/rem"
    class="ResourceMap">
    <h1>Resource Map http://my.example.org/rem</h1>

    <p>Described Aggregation: <a rel="ore:describes"
      href="http://my.example.org/aggregation">
      http://my.example.org/aggregation</a></p>

  </div>
</body>
</html>

XHTML+RDFa, RDF/XML via RDFa Distiller, NTriples via RDFa Distiller

The about and href attribute values could be relative references to be resolved relative to a base URI, e.g.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN"
            "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
         xmlns:ore="http://www.openarchives.org/ore/terms/"
         xml:lang="en">
  <head profile="http://www.w3.org/1999/xhtml/vocab">
    <base href="http://my.example.org/rem" />
    <title>Resource Map http://my.example.org/rem</title>
  </head>

  <body>
    <div class="ResourceMap">
      <h1>Resource Map http://my.example.org/rem</h1>

      <p>Described Aggregation: <a rel="ore:describes"
        href="aggregation">
        http://my.example.org/aggregation</a></p>

    </div>
  </body>
</html>

XHTML+RDFa, RDF/XML via RDFa Distiller, NTriples via RDFa Distiller

The base URI may be the URI of the document e.g. if the URI of the document is the URI of the Resource Map http://my.example.org/rem then the example might be represented as:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN"
                  "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
         xmlns:ore="http://www.openarchives.org/ore/terms/"
         xml:lang="en">
  <head profile="http://www.w3.org/1999/xhtml/vocab">
    <title>Resource Map http://my.example.org/rem</title>
  </head>

  <body>
    <div class="ResourceMap">
      <h1>Resource Map http://my.example.org/rem</h1>

      <p>Described Aggregation: <a rel="ore:describes"
        href="aggregation">
        http://my.example.org/aggregation</a></p>

    </div>
  </body>
</html>

XHTML+RDFa, RDF/XML via RDFa Distiller, NTriples via RDFa Distiller

For reasons of brevity, these variants are not repeated in the remaining examples below, which all use the form of the first example above, with absolute URIs provided.

3.2 Typing of Resource Map

The type of a Resource Map is expressed by a single (optional) triple in which the subject is the URI of the Resource Map, the predicate is the URI http://www.w3.org/1999/02/22-rdf-syntax-ns#type, and the object is the URI http://www.openarchives.org/ore/terms/ResourceMap.

In RDFa, this can be expressed using an XHTML element with an about attribute (the value of which provides the subject, the URI of the Resource Map), and also a typeof attribute with a CURIE value corresponding to the predicate (typically ore:ResourceMap).

For the example described in section 3, the relevant triple is:

Subject Predicate Object
http://my.example.org/rem rdf:type http://www.openarchives.org/ore/terms/ResourceMap

This triple could be expressed in XHTML+RDFa as follows:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN"
                      "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
      xmlns:ore="http://www.openarchives.org/ore/terms/"
      xml:lang="en">
  <head profile="http://www.w3.org/1999/xhtml/vocab">
    <title>Resource Map http://my.example.org/rem</title>
  </head>
  <body>

    <div about="http://my.example.org/rem"
      typeof="ore:ResourceMap" class="ResourceMap">
      <h1>Resource Map http://my.example.org/rem</h1>

      <p>Described Aggregation: <a rel="ore:describes"
        href="http://my.example.org/aggregation">
        http://my.example.org/aggregation</a></p>

    </div>
  </body>
</html>

XHTML+RDFa, RDF/XML via RDFa Distiller, NTriples via RDFa Distiller

3.3 Metadata about Resource Map (Required)

A Resource Map must provide some basic metadata about the Resource Map. This metadata takes the form of

In RDFa, this can be expressed using an XHTML element with an about attribute (the value of which provides the subject, the URI of the Resource Map), and nested within that element

For the example described in section 3, the relevant triples are:

Subject Predicate Object
http://my.example.org/rem dcterms:creator http://my.example.org/agents/AgencyX
http://my.example.org/rem dcterms:modified "2008-02-12"^^
http://www.w3.org/2001/XMLSchema#date

These triples could be expressed in RDFa as follows:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN"
"http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
      xmlns:ore="http://www.openarchives.org/ore/terms/"
      xmlns:dc="http://purl.org/dc/elements/1.1/"
      xmlns:dcterms="http://purl.org/dc/terms/"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
      xml:lang="en">
  <head profile="http://www.w3.org/1999/xhtml/vocab">
    <title>Resource Map http://my.example.org/rem</title>
  </head>
  <body>

    <div about="http://my.example.org/rem"
      typeof="ore:ResourceMap" class="ResourceMap">
      <h1>Resource Map http://my.example.org/rem</h1>

      <p>Described Aggregation: <a rel="ore:describes"
        href="http://my.example.org/aggregation">
        http://my.example.org/aggregation</a></p>

      <p>Creator: 
        <a rel="dcterms:creator"
        href="http://my.example.org/agents/AgencyX">Agency X</a>.</p>
      <p>Modification date: 
        <span property="dcterms:modified"
        datatype="xsd:date" content="2008-02-12">12 February 2008</span>.</p>

    </div>
  </body>
</html>

XHTML+RDFa, RDF/XML via RDFa Distiller, NTriples via RDFa Distiller

3.4 Metadata about Resource Map (Optional)

A Resource Map can also provide additional metadata about the Resource Map. This metadata takes the form of triples in which

The first class of triple is expressed as in the previous sections, using an element with an about attribute (the value of which provides the subject, the URI of the Resource Map), and nested within that element, for each triple:

The second class of triple is expressed similarly, using an element with an about attribute (the value of which here provides the object, the URI of the Resource Map), and nested within that element, for each triple an element with a rev attribute with a CURIE value corresponding to the predicate and an href attribute, the value of which provides the subject.

For the example described in section 3, the relevant triples are:

Subject Predicate Object
http://my.example.org/rem dc:rights http://example.org/docs/doc123/
http://my.example.org/rem dcterms:created "2008-02-07"^^
http://www.w3.org/2001/XMLSchema#date
http://my.example.org/rem marcrel:OWN http://my.example.org/agents/AgencyY
http://example.org/docs/doc456/ dcterms:references http://my.example.org/rem

These triples could be expressed in RDFa as follows:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN"
"http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
      xmlns:ore="http://www.openarchives.org/ore/terms/"
      xmlns:dc="http://purl.org/dc/elements/1.1/"
      xmlns:dcterms="http://purl.org/dc/terms/"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
      xmlns:marcrel="http://www.loc.gov/loc.terms/relators/"
      xml:lang="en">
  <head profile="http://www.w3.org/1999/xhtml/vocab">
    <title>Resource Map http://my.example.org/rem</title>
  </head>
  <body>

    <div about="http://my.example.org/rem"
      typeof="ore:ResourceMap" class="ResourceMap">
      <h1>Resource Map http://my.example.org/rem</h1>

      <p>Described Aggregation: <a rel="ore:describes"
        href="http://my.example.org/aggregation">
        http://my.example.org/aggregation</a></p>

      <p>Creator: <a rel="dcterms:creator"
        href="http://my.example.org/agents/AgencyX">Agency X</a>.</p>
      <p>Modification date: <span property="dcterms:modified" datatype="xsd:date"
        content="2008-02-12">12 February 2008</span>.</p>

      <p>Rights Statement:  <a rel="dc:rights"
        href="http://example.org/docs/doc123/">Rights Statement 123</a>.</p>
      <p>Creation date: <span property="dcterms:created" datatype="xsd:date"
        content="2008-02-07">07 February 2008</span>.</p>
      <p>Owner: <a rel="marcrel:OWN"
        href="http://my.example.org/agents/AgencyY">Agency Y</a>.</p>
      <p>Referenced by: <a rev="dcterms:references"
        href="http://example.org/docs/doc456/">Document 456</a>.</p>

    </div>
  </body>
</html>

XHTML+RDFa, RDF/XML via RDFa Distiller, NTriples via RDFa Distiller

3.5 Metadata about Creator of Resource Map (Optional)

A Resource Map can also provide simple metadata about the creator of a Resource Map. This metadata takes the form of:

For the example described in section 3, the relevant triples are:

Subject Predicate Object
http://my.example.org/agents/AgencyX foaf:name "Agency X"
http://my.example.org/agents/AgencyX foaf:mbox mailto:agencyx@example.org

These triples could be expressed in RDFa as follows:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN"
"http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
      xmlns:ore="http://www.openarchives.org/ore/terms/"
      xmlns:dc="http://purl.org/dc/elements/1.1/"
      xmlns:dcterms="http://purl.org/dc/terms/"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
      xmlns:marcrel="http://www.loc.gov/loc.terms/relators/"
      xmlns:foaf="http://xmlns.com/foaf/0.1/"
      xml:lang="en">
<head profile="http://www.w3.org/1999/xhtml/vocab">
    <title>Resource Map http://my.example.org/rem</title>
  </head>
  <body>

    <div about="http://my.example.org/rem"
      typeof="ore:ResourceMap" class="ResourceMap">
      <h1>Resource Map http://my.example.org/rem</h1>

      <p>Described Aggregation: <a rel="ore:describes"
        href="http://my.example.org/aggregation">
        http://my.example.org/aggregation</a></p>
      <p>Creator: <a rel="dcterms:creator"
        href="http://my.example.org/agents/AgencyX">Agency X</a>.</p>

      <div about="http://my.example.org/agents/AgencyX" class="Agent">
        <p>Name <span property="foaf:name">Agency X</span>.</p>
        <p>Email: <a rel="foaf:mbox"
          href="mailto:agencyx@example.org">mailto:agencyx@example.org</a>.</p>
      </div>

      <p>Modification date: <span property="dcterms:modified" datatype="xsd:date"
        content="2008-02-12">12 February 2008</span>.</p>
      <p>Rights Statement:  <a rel="dc:rights"
        href="http://example.org/docs/doc123/">Rights Statement 123</a>.</p>

      <p>Creation date: <span property="dcterms:created" datatype="xsd:date"
        content="2008-02-07">07 February 2008</span>.</p>
      <p>Owner: <a rel="marcrel:OWN"
        href="http://my.example.org/agents/AgencyY">Agency Y</a>.</p>
      <p>Referenced by: <a rev="dcterms:references"
        href="http://example.org/docs/doc456/">Document 456</a>.</p>

    </div>

  </body>
</html>

XHTML+RDFa, RDF/XML via RDFa Distiller, NTriples via RDFa Distiller

3.6 Relationship between Aggregation and aggregated Resource(s)

The relationship between an Aggregation and its component aggregated Resources is expressed by one or more triples in which the subject is the URI of the Aggregation, the predicate is the URI http://www.openarchives.org/ore/terms/aggregates and the object is the URI of the aggregated Resource.

In RDFa, this can be expressed using an XHTML element with an about attribute (the value of which provides the subject, the URI of the Aggregation), and nested within that element, for each aggregated Resource, an a element with a rel attribute with a CURIE value corresponding to the predicate (typically ore:aggregates) and an href attribute, the value of which provides the object, the URI of the aggregated Resource).

For the example described in section 3, the relevant triples are:

Subject Predicate Object
http://my.example.org/aggregation ore:aggregates http://my.example.org/doc.html
http://my.example.org/aggregation ore:aggregates http://my.example.org/doc1.html
http://my.example.org/aggregation ore:aggregates http://my.example.org/doc1.pdf

These triples could be expressed in RDFa as follows:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN"
                      "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
      xmlns:ore="http://www.openarchives.org/ore/terms/"
      xmlns:dc="http://purl.org/dc/elements/1.1/"
      xmlns:dcterms="http://purl.org/dc/terms/"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
      xmlns:marcrel="http://www.loc.gov/loc.terms/relators/"
      xmlns:foaf="http://xmlns.com/foaf/0.1/"
      xml:lang="en">
  <head profile="http://www.w3.org/1999/xhtml/vocab">
    <title>Resource Map http://my.example.org/rem</title>
  </head>
  <body>

    <div about="http://my.example.org/rem"
      typeof="ore:ResourceMap" class="ResourceMap">
      <h1>Resource Map http://my.example.org/rem</h1>

      <p>Described Aggregation: <a rel="ore:describes"
        href="http://my.example.org/aggregation">
        http://my.example.org/aggregation</a></p>
      <p>Creator: <a rel="dcterms:creator"
        href="http://my.example.org/agents/AgencyX">Agency X</a>.</p>

      <div about="http://my.example.org/agents/AgencyX" class="Agent">
        <p>Name <span property="foaf:name">Agency X</span>.</p>
        <p>Email: <a rel="foaf:mbox"
          href="mailto:agencyx@example.org">mailto:agencyx@example.org</a>.</p>
      </div>

      <p>Modification date: <span property="dcterms:modified" datatype="xsd:date"
        content="2008-02-12">12 February 2008</span>.</p>
      <p>Rights Statement:  <a rel="dc:rights"
        href="http://example.org/docs/doc123/">Rights Statement 123</a>.</p>

      <p>Creation date: <span property="dcterms:created" datatype="xsd:date"
        content="2008-02-07">07 February 2008</span>.</p>
      <p>Owner: <a rel="marcrel:OWN" href="http://my.example.org/agents/AgencyY">Agency Y</a>.</p>
      <p>Referenced by: <a rev="dcterms:references"
        href="http://example.org/docs/doc456/">Document 456</a>.</p>

      <div about="http://my.example.org/aggregation"
        class="Aggregation">
        <h2>Aggregation http://my.example.org/aggregation</h2>

        <p>Components/members of Aggregation: </p>
        <ul>
          <li><a rel="ore:aggregates"
            href="http://my.example.org/doc.html">
            http://my.example.org/doc.html</a>.</li>
          <li><a rel="ore:aggregates"
            href="http://my.example.org/doc1.html">
            http://my.example.org/doc1.html</a>.</li>
          <li><a rel="ore:aggregates"
            href="http://my.example.org/doc1.pdf">
            http://my.example.org/doc1.pdf</a>.</li>
        </ul>

      </div>

    </div>

  </body>
</html>

XHTML+RDFa, RDF/XML via RDFa Distiller, NTriples via RDFa Distiller

3.7 Typing of Aggregation

The type of an Aggregation is expressed by a single (optional) triple in which the subject is the URI of the Aggregation, the predicate is the URI http://www.w3.org/1999/02/22-rdf-syntax-ns#type, and the object is the URI http://www.openarchives.org/ore/terms/Aggregation.

In RDFa, this can be expressed using an XHTML element with an about attribute (the value of which provides the subject, the URI of the Aggregation), and also a typeof attribute with a CURIE value corresponding to the predicate (typically ore:Aggregation).

For the example described in section 3, the relevant triples are:

Subject Predicate Object
http://my.example.org/aggregation rdf:type http://www.openarchives.org/ore/terms/Aggregation

These triples could be expressed in RDFa as follows:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN"
                      "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
      xmlns:ore="http://www.openarchives.org/ore/terms/"
      xmlns:dc="http://purl.org/dc/elements/1.1/"
      xmlns:dcterms="http://purl.org/dc/terms/"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
      xmlns:marcrel="http://www.loc.gov/loc.terms/relators/"
      xmlns:foaf="http://xmlns.com/foaf/0.1/"
      xml:lang="en">
  <head profile="http://www.w3.org/1999/xhtml/vocab">
    <title>Resource Map http://my.example.org/rem</title>
  </head>
  <body>

    <div about="http://my.example.org/rem"
      typeof="ore:ResourceMap" class="ResourceMap">
      <h1>Resource Map http://my.example.org/rem</h1>

      <p>Described Aggregation: <a rel="ore:describes"
        href="http://my.example.org/aggregation">
        http://my.example.org/aggregation</a></p>
      <p>Creator: <a rel="dcterms:creator"
        href="http://my.example.org/agents/AgencyX">Agency X</a>.</p>

      <div about="http://my.example.org/agents/AgencyX" class="Agent">
        <p>Name <span property="foaf:name">Agency X</span>.</p>
        <p>Email: <a rel="foaf:mbox"
          href="mailto:agencyx@example.org">mailto:agencyx@example.org</a>.</p>
      </div>

      <p>Modification date: <span property="dcterms:modified" datatype="xsd:date"
        content="2008-02-12">12 February 2008</span>.</p>
      <p>Rights Statement:
        <a rel="dc:rights" href="http://example.org/docs/doc123/">Rights Statement 123</a>.</p>

      <p>Creation date: <span property="dcterms:created" datatype="xsd:date"
        content="2008-02-07">07 February 2008</span>.</p>
      <p>Owner: <a rel="marcrel:OWN" href="http://my.example.org/agents/AgencyY">Agency Y</a>.</p>
      <p>Referenced by:
        <a rev="dcterms:references" href="http://example.org/docs/doc456/">Document 456</a>.</p>

      <div about="http://my.example.org/aggregation"
        typeof="ore:Aggregation" class="Aggregation">
        <h2>Aggregation http://my.example.org/aggregation</h2>

        <p>Components/members of Aggregation: </p>
        <ul>
          <li><a rel="ore:aggregates"
            href="http://my.example.org/doc.html">
            http://my.example.org/doc.html</a>.</li>
          <li><a rel="ore:aggregates"
            href="http://my.example.org/doc1.html">
            http://my.example.org/doc1.html</a>.</li>
          <li><a rel="ore:aggregates"
            href="http://my.example.org/doc1.pdf">
            http://my.example.org/doc1.pdf</a>.</li>
      </ul>

      </div>

    </div>
  </body>
</html>

XHTML+RDFa, RDF/XML via RDFa Distiller, NTriples via RDFa Distiller

3.8 Relationships between the Aggregation and Similar Resources

A Resource Map can also provide information about the relationships between an Aggregation and similar resources. This metadata takes the form of either zero or more triples in which the subject is the URI of the Aggregation, the predicate is the URI http://www.w3.org/2000/01/rdf-schema#seeAlso and the object is a URI which identifies some other resource. The Abstract Data Model also permits a Resource Map to provide information about resources which are similar in intellectual content to an Aggregation. This metadata takes the form of zero or more triples in which the subject is the URI of the Aggregation, the predicate is the URI http://www.openarchives.org/ore/similarTo and the object is a URI of another resource.

In RDFa, this can be expressed using an XHTML element with an about attribute (the value of which provides the subject, the URI of the Aggregation), and nested within that element, for each similar resource, an a element with a rel attribute with a CURIE value corresponding to the predicate (typically rdfs:seeAlso or ore:similarTo) and an href attribute, the value of which provides the object, the URI of the aggregated Resource).

For the example described in section 3, the relevant triples are:

Subject Predicate Object
http://my.example.org/aggregation rdfs:seeAlso http://your.example.org/aggregation-1
http://my.example.org/aggregation ore:similarTo info:doi/10.1045/february-2006-smith

These triples could be expressed in RDFa as follows:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN"
                      "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
      xmlns:ore="http://www.openarchives.org/ore/terms/"
      xmlns:dc="http://purl.org/dc/elements/1.1/"
      xmlns:dcterms="http://purl.org/dc/terms/"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
      xmlns:marcrel="http://www.loc.gov/loc.terms/relators/"
      xmlns:foaf="http://xmlns.com/foaf/0.1/"
      xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
      xml:lang="en">
  <head profile="http://www.w3.org/1999/xhtml/vocab">
    <title>Resource Map http://my.example.org/rem</title>
  </head>
  <body>

    <div about="http://my.example.org/rem"
      typeof="ore:ResourceMap" class="ResourceMap">
      <h1>Resource Map http://my.example.org/rem</h1>

      <p>Described Aggregation: <a rel="ore:describes"
        href="http://my.example.org/aggregation">
        http://my.example.org/aggregation</a></p>

      <p>Creator: <a rel="dcterms:creator"
        href="http://my.example.org/agents/AgencyX">Agency X</a>.</p>

      <div about="http://my.example.org/agents/AgencyX" class="Agent">
        <p>Name <span property="foaf:name">Agency X</span>.</p>
        <p>Email: <a rel="foaf:mbox"
          href="mailto:agencyx@example.org">mailto:agencyx@example.org</a>.</p>
      </div>

      <p>Modification date: <span property="dcterms:modified" datatype="xsd:date"
        content="2008-02-12">12 February 2008</span>.</p>

      <p>Rights Statement:
        <a rel="dc:rights" href="http://example.org/docs/doc123/">Rights Statement 123</a>.</p>
      <p>Creation date: <span property="dcterms:created" datatype="xsd:date"
        content="2008-02-07">07 February 2008</span>.</p>
      <p>Owner: <a rel="marcrel:OWN" href="http://my.example.org/agents/AgencyY">Agency Y</a>.</p>
      <p>Referenced by:
        <a rev="dcterms:references" href="http://example.org/docs/doc456/">Document 456</a>.</p>

      <div about="http://my.example.org/aggregation"
        typeof="ore:Aggregation" class="Aggregation">
        <h2>Aggregation http://my.example.org/aggregation</h2>

        <p>Components/members of Aggregation: </p>
        <ul>
          <li><a rel="ore:aggregates"
            href="http://my.example.org/doc.html">
            http://my.example.org/doc.html</a>.</li>
          <li><a rel="ore:aggregates"
            href="http://my.example.org/doc1.html">
            http://my.example.org/doc1.html</a>.</li>
          <li><a rel="ore:aggregates"
            href="http://my.example.org/doc1.pdf">
            http://my.example.org/doc1.pdf</a>.</li>
        </ul>

        <p>See also:  <a rel="rdfs:seeAlso"
          href="http://your.example.org/aggregation-1">
          http://your.example.org/aggregation-1</a>.</p>
        <p>Similar to:  <a rel="ore:similarTo"
          href="info:doi/10.1045/february-2006-smith">
          info:doi/10.1045/february-2006-smith</a>.</p>

      </div>

    </div>
  </body>
</html>

XHTML+RDFa, RDF/XML via RDFa Distiller, NTriples via RDFa Distiller

3.9 Relationships between Aggregation and Other Resources

A Resource Map can also provide additional metadata about the Aggregation, describing relationships between the Aggregation and other resources, in a similar way to the case of the Resource Map itself. This metadata takes the form of triples in which

The first class of triple is expressed as in the previous sections, using an element with an about attribute (the value of which provides the subject, the URI of the Aggregation), and nested within that element, for each triple:

The second class of triple is expressed similarly, using an element with an about attribute (the value of which here provides the object, the URI of the Aggregation), and nested within that element, for each triple an element with a rev attribute with a CURIE value corresponding to the predicate and an href attribute, the value of which provides the subject.

For the example described in section 3, the relevant triple is:

Subject Predicate Object
http://example.org/docs/doc789/ dcterms:references http://my.example.org/aggregation

This triple could be expressed in RDFa as follows:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN"
                      "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
      xmlns:ore="http://www.openarchives.org/ore/terms/"
      xmlns:dc="http://purl.org/dc/elements/1.1/"
      xmlns:dcterms="http://purl.org/dc/terms/"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
      xmlns:marcrel="http://www.loc.gov/loc.terms/relators/"
      xmlns:foaf="http://xmlns.com/foaf/0.1/"
      xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
      xml:lang="en">

  <head profile="http://www.w3.org/1999/xhtml/vocab">
    <title>Resource Map http://my.example.org/rem</title>
  </head>
  <body>

    <div about="http://my.example.org/rem"
      typeof="ore:ResourceMap" class="ResourceMap">
      <h1>Resource Map http://my.example.org/rem</h1>

      <p>Described Aggregation: <a rel="ore:describes"
        href="http://my.example.org/aggregation">
        http://my.example.org/aggregation</a></p>

      <p>Creator: <a rel="dcterms:creator"
        href="http://my.example.org/agents/AgencyX">Agency X</a>.</p>

      <div about="http://my.example.org/agents/AgencyX" class="Agent">
        <p>Name <span property="foaf:name">Agency X</span>.</p>
        <p>Email: <a rel="foaf:mbox"
          href="mailto:agencyx@example.org">mailto:agencyx@example.org</a>.</p>
      </div>

      <p>Modification date: <span property="dcterms:modified" datatype="xsd:date"
        content="2008-02-12">12 February 2008</span>.</p>

      <p>Rights Statement:
        <a rel="dc:rights" href="http://example.org/docs/doc123/">Rights Statement 123</a>.</p>
      <p>Creation date: <span property="dcterms:created" datatype="xsd:date"
        content="2008-02-07">07 February 2008</span>.</p>
      <p>Owner: <a rel="marcrel:OWN" href="http://my.example.org/agents/AgencyY">Agency Y</a>.</p>
      <p>Referenced by:
        <a rev="dcterms:references" href="http://example.org/docs/doc456/">Document 456</a>.</p>

      <div about="http://my.example.org/aggregation"
        typeof="ore:Aggregation" class="Aggregation">
        <h2>Aggregation http://my.example.org/aggregation</h2>

        <p>Components/members of Aggregation: </p>
        <ul>
          <li><a rel="ore:aggregates"
            href="http://my.example.org/doc.html">
            http://my.example.org/doc.html</a>.</li>
          <li><a rel="ore:aggregates"
            href="http://my.example.org/doc1.html">
            http://my.example.org/doc1.html</a>.</li>
          <li><a rel="ore:aggregates"
            href="http://my.example.org/doc1.pdf">
            http://my.example.org/doc1.pdf</a>.</li>
        </ul>

        <p>See also:  <a rel="rdfs:seeAlso"
          href="http://your.example.org/aggregation-1">
          http://your.example.org/aggregation-1</a>.</p>
        <p>Similar to:  <a rel="ore:similarTo"
          href="info:doi/10.1045/february-2006-smith">
          info:doi/10.1045/february-2006-smith</a>.</p>

        <p>Referenced by: <a rev="dcterms:references"
          href="http://example.org/docs/doc/789/">
          http://example.org/docs/doc/789/</a>.</p>

      </div>

    </div>

  </body>
</html>

XHTML+RDFa, RDF/XML via RDFa Distiller, NTriples via RDFa Distiller

3.10 Relationships between Aggregated Resources and Other Resources

A Resource Map can also provide additional metadata about the Aggregated Resources, describing relationships between an Aggregated Resource and another resource, in a similar way to the cases of the Resource Map (section 3.4) and the Aggregation (section 3.9). This may includes triples relationships between two Aggregated Resources within the Aggregation described by the current Resource Map. This metadata takes the form of triples in which

The first class of triple is expressed as in the previous sections, using an element with an about attribute (the value of which provides the subject, the URI of the Aggregated Resource), and nested within that element, for each triple:

The second class of triple is expressed similarly, using an element with an about attribute (the value of which here provides the object, the URI of the Aggregated Resource), and nested within that element, for each triple an element with a rev attribute with a CURIE value corresponding to the predicate and an href attribute, the value of which provides the subject.

For the example described in section 3, the relevant triples - note that the first of the three describes a relationship between two Aggregated Resources within the current Aggregation - are:

Subject Predicate Object
http://my.example.org/doc1.html dcterms:hasFormat http://my.example.org/doc1.pdf
http://my.example.org/doc1.pdf rdf:type http://purl.org/dc/dcmitype/Text
http://example.org/docs/docABC/ dcterms:references http://my.example.org/doc.html

These triples could be expressed in RDFa as follows:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN"
                  "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">

<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
      xmlns:ore="http://www.openarchives.org/ore/terms/"
      xmlns:dc="http://purl.org/dc/elements/1.1/"
      xmlns:dcterms="http://purl.org/dc/terms/"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
      xmlns:marcrel="http://www.loc.gov/loc.terms/relators/"
      xmlns:foaf="http://xmlns.com/foaf/0.1/"
      xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
      xml:lang="en">

  <head profile="http://www.w3.org/1999/xhtml/vocab">
    <title>Resource Map http://my.example.org/rem</title>
  </head>
  <body>

    <div about="http://my.example.org/rem"
      typeof="ore:ResourceMap" class="ResourceMap">
      <h1>Resource Map http://my.example.org/rem</h1>

      <p>Described Aggregation: <a rel="ore:describes"
        href="http://my.example.org/aggregation">
        http://my.example.org/aggregation</a></p>

      <p>Creator: <a rel="dcterms:creator"
        href="http://my.example.org/agents/AgencyX">Agency X</a>.</p>

      <div about="http://my.example.org/agents/AgencyX" class="Agent">
        <p>Name <span property="foaf:name">Agency X</span>.</p>
        <p>Email: <a rel="foaf:mbox"
          href="mailto:agencyx@example.org">mailto:agencyx@example.org</a>.</p>
      </div>

      <p>Modification date: <span property="dcterms:modified" datatype="xsd:date"
        content="2008-02-12">12 February 2008</span>.</p>

      <p>Rights Statement:
        <a rel="dc:rights" href="http://example.org/docs/doc123/">Rights Statement 123</a>.</p>
      <p>Creation date: <span property="dcterms:created" datatype="xsd:date"
        content="2008-02-07">07 February 2008</span>.</p>
      <p>Owner: <a rel="marcrel:OWN" href="http://my.example.org/agents/AgencyY">Agency Y</a>.</p>
      <p>Referenced by:
        <a rev="dcterms:references" href="http://example.org/docs/doc456/">Document 456</a>.</p>

      <div about="http://my.example.org/aggregation"
        typeof="ore:Aggregation" class="Aggregation">
        <h2>Aggregation http://my.example.org/aggregation</h2>

        <p>Components/members of Aggregation: </p>
        <ul>
          <li><a rel="ore:aggregates"
            href="http://my.example.org/doc.html">
            http://my.example.org/doc.html</a>.</li>
          <li><a rel="ore:aggregates"
            href="http://my.example.org/doc1.html">
            http://my.example.org/doc1.html</a>.</li>
          <li><a rel="ore:aggregates"
            href="http://my.example.org/doc1.pdf">
            http://my.example.org/doc1.pdf</a>.</li>
        </ul>

        <p>See also:  <a rel="rdfs:seeAlso"
          href="http://your.example.org/aggregation-1">
          http://your.example.org/aggregation-1</a>.</p>
        <p>Similar to:  <a rel="ore:similarTo"
          href="info:doi/10.1045/february-2006-smith">
          info:doi/10.1045/february-2006-smith</a>.</p>

        <p>Referenced by: <a rev="dcterms:references"
       href="http://example.org/docs/doc/789/">http://example.org/docs/doc/789/</a>.</p>
      </div>

      <div about="http://my.example.org/doc1.html"
        class="AggregatedResource">
      <h3>Aggregated Resource http://my.example.org/doc1.html</h3>

        <p>Available in different format: <a rel="dcterms:hasFormat"
          href="http://my.example.org/doc1.pdf">
          http://my.example.org/doc1.pdf</a>.</p>
        <p>Referenced by: <a rev="dcterms:references"
          href="http://example.org/docs/docABC/">
          http://example.org/docs/docABC/</a>.</p>
      </div>

      <div about="http://my.example.org/doc1.pdf"
        class="AggregatedResource">
      <h3>Aggregated Resource http://my.example.org/doc1.pdf</h3>

        <p>Type: <a rel="rdf:type"
          href="http://purl.org/dc/dcmitype/Text">Text</a>.</p>
      </div>

    </div>
  </body>
</html>

XHTML+RDFa, RDF/XML via RDFa Distiller, NTriples via RDFa Distiller

3.11 Aggregated Resource as constituent of another Aggregation

A Resource Map can describe relationships between an Aggregated Resource and another Aggregation, in the form of triples in which the subject is the URI of an Aggregated Resource, the predicate is the URI http://www.openarchives.org/ore/terms/isAggregatedBy and the object is the URI of another Aggregation, i.e. an Aggregation other than the one described by the current Resource Map.

In RDFa, this can be expressed using an XHTML element with an about attribute (the value of which provides the subject, the URI of the Aggregated Resource), and nested within that element an a element with a rel attribute with a CURIE value corresponding to the predicate (typically ore:isAggregatedBy and an href attribute, the value of which provides the object, the URI of the other Aggregation).

For the example described in section 3, the relevant triple is:

Subject Predicate Object
http://my.example.org/doc1.pdf ore:isAggregatedBy http://your.example.org/aggregation-2

This triple could be expressed in RDFa as follows:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN"
                      "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
      xmlns:ore="http://www.openarchives.org/ore/terms/"
      xmlns:dc="http://purl.org/dc/elements/1.1/"
      xmlns:dcterms="http://purl.org/dc/terms/"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
      xmlns:marcrel="http://www.loc.gov/loc.terms/relators/"
      xmlns:foaf="http://xmlns.com/foaf/0.1/"
      xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
      xml:lang="en">
  <head profile="http://www.w3.org/1999/xhtml/vocab">
    <title>Resource Map http://my.example.org/rem</title>
  </head>
  <body>

    <div about="http://my.example.org/rem"
      typeof="ore:ResourceMap" class="ResourceMap">
      <h1>Resource Map http://my.example.org/rem</h1>

      <p>Described Aggregation: <a rel="ore:describes"
        href="http://my.example.org/aggregation">
        http://my.example.org/aggregation</a></p>

      <p>Creator: <a rel="dcterms:creator"
        href="http://my.example.org/agents/AgencyX">Agency X</a>.</p>

      <div about="http://my.example.org/agents/AgencyX" class="Agent">
        <p>Name <span property="foaf:name">Agency X</span>.</p>
        <p>Email: <a rel="foaf:mbox"
          href="mailto:agencyx@example.org">mailto:agencyx@example.org</a>.</p>
      </div>

      <p>Modification date: <span property="dcterms:modified" datatype="xsd:date"
      content="2008-02-12">12 February 2008</span>.</p>

      <p>Rights Statement:
        <a rel="dc:rights" href="http://example.org/docs/doc123/">Rights Statement 123</a>.</p>
      <p>Creation date: <span property="dcterms:created" datatype="xsd:date"
        content="2008-02-07">07 February 2008</span>.</p>
      <p>Owner: <a rel="marcrel:OWN" href="http://my.example.org/agents/AgencyY">Agency Y</a>.</p>
      <p>Referenced by:
        <a rev="dcterms:references" href="http://example.org/docs/doc456/">Document 456</a>.</p>

      <div about="http://my.example.org/aggregation"
        typeof="ore:Aggregation" class="Aggregation">
        <h2>Aggregation http://my.example.org/aggregation</h2>

        <p>Components/members of Aggregation: </p>
        <ul>
          <li><a rel="ore:aggregates"
            href="http://my.example.org/doc.html">
            http://my.example.org/doc.html</a>.</li>
          <li><a rel="ore:aggregates"
            href="http://my.example.org/doc1.html">
            http://my.example.org/doc1.html</a>.</li>
          <li><a rel="ore:aggregates"
            href="http://my.example.org/doc1.pdf">
            http://my.example.org/doc1.pdf</a>.</li>
        </ul>

        <p>See also:  <a rel="rdfs:seeAlso"
          href="http://your.example.org/aggregation-1">http://your.example.org/aggregation-1</a>.</p>
        <p>Similar to:  <a rel="ore:similarTo"
          href="info:doi/10.1045/february-2006-smith">info:doi/10.1045/february-2006-smith</a>.</p>

        <p>Referenced by: <a rev="dcterms:references"
          href="http://example.org/docs/doc/789/">http://example.org/docs/doc/789/</a>.</p>

      </div>

      <div about="http://my.example.org/doc1.html"
        class="AggregatedResource">
        <h3>Aggregated Resource http://my.example.org/doc1.html</h3>

        <p>Available in different format: <a rel="dcterms:hasFormat"
          href="http://my.example.org/doc1.pdf">http://my.example.org/doc1.pdf</a>.</p>
        <p>Referenced by: <a rev="dcterms:references"
          href="http://example.org/docs/docABC/">http://example.org/docs/docABC/</a>.</p>
      </div>

      <div about="http://my.example.org/doc1.pdf"
        class="AggregatedResource">
        <h3>Aggregated Resource http://my.example.org/doc1.pdf</h3>

        <p>Type: <a rel="rdf:type" href="http://purl.org/dc/dcmitype/Text">Text</a>.</p>
        <p>Aggregated By: <a rel="ore:isAggregatedy"
          href="http://your.example.org/aggregation-2"
          >http://your.example.org/aggregation-2</a>.</p>
      </div>

    </div>
  </body>
</html>

XHTML+RDFa, RDF/XML via RDFa Distiller, NTriples via RDFa Distiller

3.12 Nesting Aggregations

A Resource Map may express the information that an Aggregated Resource is itself an Aggregation described by another Resource Map, in the form of triples in which the subject is the URI of an Aggregated Resource, the predicate is the URI http://www.openarchives.org/ore/terms/isDescribedBy and the object is the URI of another Resource Map.

In RDFa, this can be expressed using an XHTML element with an about attribute (the value of which provides the subject, the URI of the Aggregated Resource), and nested within that element an a element with a rel attribute with a CURIE value corresponding to the predicate (typically ore:isDescribedBy and an href attribute, the value of which provides the object, the URI of the other Resource Map).

For the example described in section 3, the relevant triple is:

Subject Predicate Object
http://my.example.org/doc1.html ore:isDescribedBy http://your.example.org/rem-3

This triple could be expressed in RDFa as follows:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN"
                      "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
      xmlns:ore="http://www.openarchives.org/ore/terms/"
      xmlns:dc="http://purl.org/dc/elements/1.1/"
      xmlns:dcterms="http://purl.org/dc/terms/"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
      xmlns:marcrel="http://www.loc.gov/loc.terms/relators/"
      xmlns:foaf="http://xmlns.com/foaf/0.1/"
      xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
      xml:lang="en">
  <head profile="http://www.w3.org/1999/xhtml/vocab">
    <title>Resource Map http://my.example.org/rem</title>
  </head>
  <body>

    <div about="http://my.example.org/rem"
      typeof="ore:ResourceMap" class="ResourceMap">
      <h1>Resource Map http://my.example.org/rem</h1>

      <p>Described Aggregation: <a rel="ore:describes"
        href="http://my.example.org/aggregation">
        http://my.example.org/aggregation</a></p>

      <p>Creator: <a rel="dcterms:creator"
        href="http://my.example.org/agents/AgencyX">Agency X</a>.</p>

      <div about="http://my.example.org/agents/AgencyX" class="Agent">
        <p>Name <span property="foaf:name">Agency X</span>.</p>
        <p>Email: <a rel="foaf:mbox"
          href="mailto:agencyx@example.org">mailto:agencyx@example.org</a>.</p>
      </div>

      <p>Modification date: <span property="dcterms:modified" datatype="xsd:date"
      content="2008-02-12">12 February 2008</span>.</p>

      <p>Rights Statement:
        <a rel="dc:rights" href="http://example.org/docs/doc123/">Rights Statement 123</a>.</p>
      <p>Creation date: <span property="dcterms:created" datatype="xsd:date"
        content="2008-02-07">07 February 2008</span>.</p>
      <p>Owner: <a rel="marcrel:OWN" href="http://my.example.org/agents/AgencyY">Agency Y</a>.</p>
      <p>Referenced by:
        <a rev="dcterms:references" href="http://example.org/docs/doc456/">Document 456</a>.</p>

      <div about="http://my.example.org/aggregation"
        typeof="ore:Aggregation" class="Aggregation">
        <h2>Aggregation http://my.example.org/aggregation</h2>

        <p>Components/members of Aggregation: </p>
        <ul>
          <li><a rel="ore:aggregates"
            href="http://my.example.org/doc.html">
            http://my.example.org/doc.html</a>.</li>
          <li><a rel="ore:aggregates"
            href="http://my.example.org/doc1.html">
            http://my.example.org/doc1.html</a>.</li>
          <li><a rel="ore:aggregates"
            href="http://my.example.org/doc1.pdf">
            http://my.example.org/doc1.pdf</a>.</li>
        </ul>

        <p>See also:  <a rel="rdfs:seeAlso"
          href="http://your.example.org/aggregation-1">http://your.example.org/aggregation-1</a>.</p>
        <p>Similar to:  <a rel="ore:similarTo"
          href="info:doi/10.1045/february-2006-smith">info:doi/10.1045/february-2006-smith</a>.</p>

        <p>Referenced by: <a rev="dcterms:references"
          href="http://example.org/docs/doc/789/">http://example.org/docs/doc/789/</a>.</p>

      </div>

      <div about="http://my.example.org/doc1.html"
        class="AggregatedResource">
        <h3>Aggregated Resource http://my.example.org/doc1.html</h3>

        <p>Available in different format: <a rel="dcterms:hasFormat"
          href="http://my.example.org/doc1.pdf">http://my.example.org/doc1.pdf</a>.</p>
        <p>Referenced by: <a rev="dcterms:references"
          href="http://example.org/docs/docABC/">http://example.org/docs/docABC/</a>.</p>
        <p>Described By: <a rel="ore:isDescribedy"
          href="http://your.example.org/rem-3"
          >http://your.example.org/rem-3</a>.</p>
       </div>

      <div about="http://my.example.org/doc1.pdf"
        class="AggregatedResource">
        <h3>Aggregated Resource http://my.example.org/doc1.pdf</h3>

        <p>Type: <a rel="rdf:type" href="http://purl.org/dc/dcmitype/Text">Text</a>.</p>
        <p>Aggregated By: <a rel="ore:isAggregatedy"
          href="http://your.example.org/aggregation-2"
          >http://your.example.org/aggregation-2</a>.</p>
      </div>

    </div>
  </body>
</html>

XHTML+RDFa, RDF/XML via RDFa Distiller, NTriples via RDFa Distiller

3.13 Additional Relationships in the Resource Map

A Resource Map may express information about relationships between other resources related to the "primary" resources described (Resource Map, Aggregation, Aggregated Resource, Proxy), in the form of triples in which the subject is any URI, the predicate is any URI and the object is any URI or a plain literal or a typed literal

These triples are expressed using the same conventions as in the previous sections. For each distinct subject, use an element with an about attribute, the value of which provides the subject, containing an element for each triple with that subject. For the URI case, a rel attribute value provides the predicate, and an href attribute value provides the object. For the literal case, a property attribute value provides the predicate and either a content attribute value or the content of the element provides the object (with a datatype attribute or xml:lang attribute as required).

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, 2004.
[ORE HTTP]
ORE User Guide - HTTP Implementation and Multiple Serializations, C. Lagoze, H. Van de Sompel, P. Johnston, M. Nelson, R. Sanderson, S. Warner, 2008-06-02. Available at http://www.openarchives.org/ore/0.9/http .
[ORE Model]
ORE Specification - Abstract Data Model, C. Lagoze, H. Van de Sompel, P. Johnston, 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 Primer]
RDFa Primer: Embedding Structured Data in Web Pages, Ben Adida, Mark Birbeck, Editors, W3C Working Draft 17 March 2008, Available at http://www.w3.org/TR/2008/WD-xhtml-rdfa-primer-20080317/ .
Latest version available at http://www.w3.org/TR/xhtml-rdfa-primer .
[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.
Available at 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,
Available at http://www.w3.org/TR/2004/REC-rdf-schema-20040210/ .
Latest version available at http://www.w3.org/TR/rdf-schema/.
[RDFXML]
RDF Vocabulary Description Language 1.0: RDF Schema , Dan Brickley and R.V. Guha, Editors. W3C Recommendation, 10 February 2004,
Available at 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 2004. Available at http://www.ietf.org/rfc/rfc3986.txt .
[RFC3987]
Internationalized Resource Identifiers (IRIs), M. Duerst & M. Suignard, IETF RFC3987, January 2005. Available at http://www.ietf.org/rfc/rfc3986.txt .
[Web Architecture]
Architecture of the World Wide Web, Volume One, I. Jacobs and N. Walsh, Editors, World Wide Web Consortium, 15 January 2004. Available at http://www.w3.org/TR/webarch/ .

A. Acknowledgements

This document is the work of the Open Archives Initiative. Funding for Open Archives Initiative Object Reuse and Exchange is provided by the Andrew W. Mellon Foundation, Microsoft, and the National Science Foundation.  Additional support is provided by the Coalition for Networked Information.

This document is based on meetings of the OAI-ORE Technical Committee (ORE-TC), with participation from the OAI-ORE Liaison Group (ORE-LG).  Members of the ORE-TC are: Chris Bizer (Freie Universität Berlin), Les Carr (University of Southampton), Tim DiLauro (Johns Hopkins University), Leigh Dodds (Ingenta), David Fulker (UCAR), Tony Hammond (Nature Publishing Group), Pete Johnston (Eduserv Foundation), Richard Jones (Imperial College), Peter Murray (OhioLINK), Michael Nelson (Old Dominion University), Ray Plante (NCSA and National Virtual Observatory), Rob Sanderson (University of Liverpool), Simeon Warner (Cornell University), and Jeff Young (OCLC).  Members of ORE-LG are: Leonardo Candela (DRIVER), Tim Cole (DLF Aquifer and UIUC Library), Julie Allinson (JISC), Jane Hunter (DEST), Savas Parastatidis  (Microsoft), Sandy Payette (Fedora Commons), Thomas Place (DARE and University of Tilburg), Andy Powell (DCMI), and Robert Tansley (Google, Inc. and DSpace)

We also acknowledge comments from the OAI-ORE Advisory Committee (ORE-AC).

B. Change Log

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

Creative Commons License
This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.

Use of this page is tracked to collect anonymous traffic data. See OAI privacy policy.