More Related Content
What's hot
What's hot (20)
Similar to An Introduction to the Open Archives Initiative Object Reuse and Exchange (OAI-ORE)
Similar to An Introduction to the Open Archives Initiative Object Reuse and Exchange (OAI-ORE) (20)
More from Jenn Riley
More from Jenn Riley (20)
Recently uploaded
Recently uploaded (20)
An Introduction to the Open Archives Initiative Object Reuse and Exchange (OAI-ORE)
- 1. An Introduction to the Open Archives Initiative Object Reuse and Exchange (OAI-ORE) Jenn Riley Metadata Librarian Digital Library Program
- 2. This is all pretty new! • OAI-ORE v1.0 specs released October 17, 2008 • Content, especially diagrams, in this presentation, adapted from http://www.openarchives.org/ore/1.0/toc.html • Not going to explain all the details, just the ones that look like they’ll be useful to production digital libraries 11/19/2008DLP Brown Bag Series Fall 2008
- 3. Purposes of OAI-ORE • Identify “aggregations” of content • Describe constituents/boundaries of aggregations That’s it. • Does not prescribe a protocol for transferring content between repositories • Just about identifying in a machine-readable way what’s there, rather than providing tools for doing anything with that information 11/19/2008DLP Brown Bag Series Fall 2008
- 4. Design principles • Built on web architecture ▫ leverage the integrated nature of the web ▫ use existing infrastructure to build semantics • Uses RDF principles ▫ think “subject,” “predicate,” object ▫ but not only encoded in RDF ▫ extends into Linked Data and Cool URIs 11/19/2008DLP Brown Bag Series Fall 2008
- 5. The problem 11/19/2008DLP Brown Bag Series Fall 2008
- 6. Definitions • Objects of interest are resources • Resources have URIs that identify them • Aggregations: ▫ stand for a set or collection of resources ▫ an aggregation is itself a resource • A resource map is a resource that describes the aggregation • A representation is a datastream obtained after dereferencing a URI (e.g., for a resource map) 11/19/2008DLP Brown Bag Series Fall 2008
- 7. An example 11/19/2008DLP Brown Bag Series Fall 2008
- 8. 11/19/2008DLP Brown Bag Series Fall 2008 More detail
- 9. Requirements for Resource Maps • ore:describes ▫ referring to the aggregation resource • dcterms:creator ▫ MUST be a reference to a Resource of type http://purl.org/dc/terms/Agent ▫ and be a human (???) • dcterms:modified ▫ referring to when the RM was last updated 11/19/2008DLP Brown Bag Series Fall 2008
- 10. Some potential features for Aggregations • ore:aggregates ▫ referring to resources that make up the aggregation • rdf:type ▫ no defined vocabulary ▫ expected to use vocabularies other (reputable?) bodies develop (e.g., DCMI Type) 11/19/2008DLP Brown Bag Series Fall 2008
- 11. So what’s the point of all of this again? • A fancy way to say things belong together ▫ machine-readable ▫ machine-understandable? • Fundamentals that could enable many higher- level services ▫ presumably including “re-use” and “exchange” ▫ but don’t define those services here 11/19/2008DLP Brown Bag Series Fall 2008
- 12. Another possible feature of Resource Maps • MAY include additional properties about the Aggregation and Aggregated Resources, such as: ▫ relationships among the Aggregated Resources, ▫ relationships from the Aggregated Resources to other Resources, ▫ and other properties • RMs are probably not all that useful to DLs unless this feature is employed 11/19/2008DLP Brown Bag Series Fall 2008
- 13. Some potential relationships between Aggregated Resources • dcterms:isVersionOf • dcterms:replaces • dcterms:references 11/19/2008DLP Brown Bag Series Fall 2008
- 14. Serializations • Atom • RDF/XML • RDFa • METS serialization tentatively planned 11/19/2008DLP Brown Bag Series Fall 2008
- 15. Accessing Resource Maps over HTTP • RECOMMENDED: 303 redirection and content negotiation • Simpler use of 303 redirection for a single Resource Map • Limited but simple strategy using hash URIs • RFDa (or microformats) either alone or in addition to other formats • HTTP Proxy URIs and ORE Proxy URI resolver at http://oreproxy.org/r 11/19/2008DLP Brown Bag Series Fall 2008
- 16. Possible ReM for digitized book 11/19/2008DLP Brown Bag Series Fall 2008 Diagram by Tim Cole, UIUC
- 17. Possible ReM for annotation of a text 11/19/2008DLP Brown Bag Series Fall 2008 Diagram by Tim Cole, UIUC
- 18. 11/19/2008DLP Brown Bag Series Fall 2008 Possible ReM for data and published paper based on it
- 19. How the DLP could use OAI-ORE • As shared data representation for scenarios like those we just saw • ReMs in RDFa behind individual item HTML displays to describe multiple versions • Treat “collections” as aggregations and expose ReMs from DLP home page • Connect online secondary sources to primary sources we deliver • ??? 11/19/2008DLP Brown Bag Series Fall 2008
- 20. The bottom line • OAI-ORE adds a tool to our ever-growing cabinet • Won’t solve all of our problems • But looks promising as one strategy for putting our collections in the flow. 11/19/2008DLP Brown Bag Series Fall 2008
- 21. Thank you! • For more information: ▫ jenlrile@indiana.edu ▫ These presentation slides: <http://www.dlib.indiana.edu/~jenlrile/presentations/ bbfall08/ore/oaiore.ppt> ▫ OAI-ORE Specifications and User Guides: <http://www.openarchives.org/ore/1.0/toc.html> 11/19/2008DLP Brown Bag Series Fall 2008
Editor's Notes
- An Introduction to the Open Archives Initiative Object Reuse and Exchange (OAI-ORE) Jenn Riley, Metadata Librarian Digital Library Program The group behind the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) has recently released a beta specification for a new protocol, entitled Open Archives Initiative Object Reuse and Exchange (OAI-ORE). OAI-ORE &quot;defines standards for the description and exchange of aggregations of Web resources,&quot; a need commonly faced by digital libraries. This presentation will provide an introduction to the OAI-ORE data model and serializations of OAI-ORE &quot;resource maps&quot; in Atom and RDF. It will also discuss the movement towards data sharing by digital libraries using mechanisms native to the Web rather than in library-centric, high-value and low adoption protocols.
- 1. The URI http://arxiv.org/abs/astro-ph/0601007 of the human start page. 2. The formats in which the document is available, i.e. PostScript, PDF, etc. These are effectively the constituents of the aggregation that is the arXiv document. For the remainder of this example we will consider this human start page, the splash page, as also a constituent of the aggregation 3. The title of the arXiv document. 4. The authors of the arXiv document. 5. The creation and last modification date of the arXiv document. 6. Identifiers of entities that are in some manner comparable to this arXiv document. For example, a version of this document was later published as an article in a peer-reviewed journal, and the Digital Object Identifier of that article is shown. 7. The versions of this document. 8. Links to other arXiv documents in the same collection (i.e., astro-ph). 9. Citations made by this arXiv document, and citations it received from other documents.