OAIOAI-ORE provides a framework for describing and exchanging aggregations of web resources -- compound digital objects that bring together text, images, data, video, and other media types distributed across the web. Developed by the Open Archives Initiative with funding from the Andrew W. Mellon Foundation, OAI-ORE has become a key specification for digital repositories, scholarly communication systems, and cultural heritage platforms that need to treat collections of web resources as coherent units.
Background
The Open Archives Initiative launched the ORE effort in October 2006, recognizing that the web increasingly featured compound objects -- scholarly articles with supplementary datasets, digital collections with multiple image formats, multimedia packages -- that lacked a standardized way to describe their boundaries and internal structure. While OAI's earlier Protocol for Metadata Harvesting (OAI-PMH) addressed metadata exchange between repositories, it did not tackle the problem of describing compound objects themselves.
Development proceeded through alpha and beta releases with input from the OAI-ORE technical committee and the wider community. The production release (version 1.0) was published on 17 October 2008.
Purpose & Scope
OAI-ORE defines how to describe aggregations of web resources and their relationships. Its core model centers on three concepts:
- Aggregation: A logical set of resources treated as a single intellectual unit
- Aggregated Resource: An individual web resource that is part of an aggregation
- Resource Map: An information resource that describes an aggregation, listing its constituent resources and their relationships
Resource Maps are the mechanism through which aggregations become visible on the web. They can express the structure, ordering, and typing of aggregated resources, enabling applications to discover what belongs to a compound object and how the pieces relate to one another.
Key Specifications
| Document | Description |
|---|---|
| Abstract Data Model | Formal model defining Aggregations, Resource Maps, and Proxies |
| Vocabulary | The ORE terms vocabulary in RDF |
| Primer | Introductory guide with examples |
| RDF/XML User Guide | Implementing Resource Maps in RDF/XML |
| RDFa User Guide | Embedding Resource Maps in HTML via RDFa |
| JSON-LD User Guide (Beta) | Serializing Resource Maps in JSON-LD |
| HTTP Implementation | Content negotiation and URI patterns |
| Resource Map Discovery | Finding Resource Maps from aggregated resources |
Serializations & Technical Formats
OAI-ORE Resource Maps can be serialized in multiple formats:
- RDF/XML — the primary serialization in the 1.0 specification
- RDFa — for embedding Resource Map data within HTML pages
- Atom — using Atom feeds to represent Resource Maps
- JSON-LD — added as a beta user guide in 2014
The ORE vocabulary namespace is http://www.openarchives.org/ore/terms/.
Governance & Maintenance
OAI-ORE is maintained by the Open Archives Initiative, an organization founded by Herbert Van de Sompel and Carl Lagoze. The specifications were developed through an open process involving a technical committee and public comment periods. The 1.0 specification has remained stable since its October 2008 release. The JSON-LD user guide, published as a beta draft in August 2014, represents the most recent addition to the specification suite.
The Foresite project produced open-source Java and Python libraries for working with OAI-ORE Resource Maps, released under a BSD license.
Notable Implementations
OAI-ORE has been adopted in a range of digital repository and preservation systems:
- Fedora Repository — uses ORE Resource Maps to describe compound objects
- DSpace — supports ORE for package ingest and export
- SWORD (Simple Web-service Offering Repository Deposit) — uses ORE for deposit packaging
- ResourceSync — OAI's newer framework for resource synchronization builds on concepts from ORE
- Scholarly publishing platforms — various systems use ORE to package articles with supplementary materials
Related Standards
- OAI-PMH — the Open Archives Initiative Protocol for Metadata Harvesting, OAI's earlier and complementary specification for metadata exchange
- Dublin Core — frequently used within ORE Resource Maps for resource description
- ResourceSync — OAI's specification for web resource synchronization