Difference between revisions of "OAI-ORE"

From MPDLMediaWiki
Jump to navigation Jump to search
 
(41 intermediate revisions by 4 users not shown)
Line 1: Line 1:
Open Archives Initiative - Object Reuse and Exchange
http://www.openarchives.org/ore/logos/ore_logo_e_128.png
'''O'''pen '''A'''rchives '''I'''nitiative - '''O'''bject '''R'''euse and '''E'''xchange


==General==
==General==


http://www.openarchives.org/ore/logos/ore_logo_e_128.png
OAI-ORE defines standards to identify and describe aggregations on the web to describe and. Taking a publication as an example, it mostly consists of multiple resources (publisher pdf, supplementary material, metadata etc.), therefore what we 'see' as an publication is actually the aggregation of multiple resources.  
 
 
OAI-ORE is a standard to describe and identify aggregations on the web. Taking a publication as an example, it mostly consists of multiple resources (publisher pdf, supplementary material, metadata etc.), therefore what we 'see' as an publication is actually the aggregation of multiple resources.  


Aggregations should be modelled in respect of the core foundations of the Web
Aggregations should be modelled in respect of the core foundations of the Web
Line 15: Line 13:


==Basic Principles==
==Basic Principles==
===Aggregation===
A non-informative resource


===Resource Map===
[[Image:Oai-ore.PNG | 500px | center ]]
An information resource that describes an aggregation
Image from: http://www.slideshare.net/hvdsomp/the-oaiore-interoperability-framework
 
===Aggregation (A)===
A [http://www.w3.org/2001/tag/doc/httpRange-14/2007-05-31/HttpRange-14#iddiv1138805816 non-information resource].
 
===Resource Map (ReM)===
An [http://www.w3.org/2001/tag/doc/httpRange-14/2007-05-31/HttpRange-14#sec-information-resources information resource] that describes an aggregation
 
===Data model===
RDF Graph using name spaces:
* dc (http://purl.org/dc/elements/1.1/)
* dcterms (http://purl.org/dc/terms/)
* foaf (http://xmlns.com/foaf/0.1/)
* ore (http://www.openarchives.org/ore/terms/)
* owl (http://www.w3.org/2002/07/owl#)
* rdf (http://www.w3.org/1999/02/22-rdf-syntax-ns#)


==Advantages==
==Advantages==
===General===
===General===
* Improve interoperability
* Using a (soon?) standard for modelling our relations
* Detection and processing of relation information, within and outside eSciDoc
* Following the principles of Linked Data (share structured data on the Web)
* Addressing Cool URI and content negotiation
===Possible new Features===
===Possible new Features===
* One step towards the 'research data continuum'? If we can model faces, ViRR, PubMan data in ore, we can easily create new Aggregations containing data from different solutions.
* Visualize data with Foresite
===Tools===
===Tools===
* [http://code.google.com/p/foresite-toolkit/ Java Library] (for constructing, parsing, manipulating and serializing OAI-ORE Resource Maps. ATOM, RDF/XML, N3, N-Triples, Turtle and RDFa)
* [http://code.google.com/p/foresite-toolkit/ Java Library] (for constructing, parsing, manipulating and serializing OAI-ORE Resource Maps. ATOM, RDF/XML, N3, N-Triples, Turtle and RDFa)
* [http://foresite.cheshire3.org/explorer/screenshots/jstor-8.png Foreside Explorer]
* [http://foresite.cheshire3.org/ Foresite Explorer] (Visualization of Relations)
* [http://wordpress.org/extend/plugins/oai-ore/ WordPress plug-in] (creating Resource Maps for WordPress posts and pages)


==Steps==
==Steps==
The basic steps to integrate OAI-ORE to eSciDoc (regarding publication data for start) would be:
# Create mapping from eSciDoc Publication Item to ore
# Create mapping from ore to eSciDoc Publication Item
# Make sure that every resource has its own URI
# Expose oai_ore over OAI-PMH
# Implement http part
# Enable SWORD deposit of ore data
==OAI-ORE in use==
This is just an extract of systems supporting OAI-ORE:
* EPrints
* Fedora
* DSpace
* Microsoft Zentity
* MyExperiment.org
* arXiv.org
* Flickr
* Oxford Research Archive
* Word Press
* Amazon


==Related Material==
==Related Material==
Line 34: Line 76:
* [http://www.openarchives.org/ore/1.0/toc.html ore 1.0 Specification]
* [http://www.openarchives.org/ore/1.0/toc.html ore 1.0 Specification]
* [http://indico.cern.ch/materialDisplay.py?contribId=34&materialId=slides&confId=48321 oai-ore tutorial at OAI6] by Herbert van de Sompel
* [http://indico.cern.ch/materialDisplay.py?contribId=34&materialId=slides&confId=48321 oai-ore tutorial at OAI6] by Herbert van de Sompel
* [http://www.ctwatch.org/quarterly/multimedia/11/ORE_prototype-demo/ Screencast on oai-ore]
* [http://www.w3.org/DesignIssues/LinkedData.html  Linked Data]
* [http://www4.wiwiss.fu-berlin.de/bizer/pub/LinkedDataTutorial/20070727/#intro More on Linked Data]
* [http://www.w3.org/Provider/Style/URI Cool URI]
* '''Intern:'''
** [[Talk:ESciDoc_Container_Toc#Attempt_to_map_to_OAI-ORE | Previous CoLab entry on OAI-ORE]]
** [[OAI-ORE_Publication_Item | OAI-ORE for eSciDoc Publication Items]]
* [http://www.driver-repository.eu/component/option,com_jdownloads/Itemid,83/task,summary/cid,54/catid,8/ Enhanced Publications Model]
[[Category:Standards]]

Latest revision as of 12:36, 5 January 2011

http://www.openarchives.org/ore/logos/ore_logo_e_128.png Open Archives Initiative - Object Reuse and Exchange

General[edit]

OAI-ORE defines standards to identify and describe aggregations on the web to describe and. Taking a publication as an example, it mostly consists of multiple resources (publisher pdf, supplementary material, metadata etc.), therefore what we 'see' as an publication is actually the aggregation of multiple resources.

Aggregations should be modelled in respect of the core foundations of the Web

  • Resource, an item of interest.
  • URI, a global identifier for a Resource.
  • Representation
  • Link, a directed connection between two Resources.

Basic Principles[edit]

Oai-ore.PNG

Image from: http://www.slideshare.net/hvdsomp/the-oaiore-interoperability-framework

Aggregation (A)[edit]

A non-information resource.

Resource Map (ReM)[edit]

An information resource that describes an aggregation

Data model[edit]

RDF Graph using name spaces:

Advantages[edit]

General[edit]

  • Improve interoperability
  • Using a (soon?) standard for modelling our relations
  • Detection and processing of relation information, within and outside eSciDoc
  • Following the principles of Linked Data (share structured data on the Web)
  • Addressing Cool URI and content negotiation

Possible new Features[edit]

  • One step towards the 'research data continuum'? If we can model faces, ViRR, PubMan data in ore, we can easily create new Aggregations containing data from different solutions.
  • Visualize data with Foresite

Tools[edit]

  • Java Library (for constructing, parsing, manipulating and serializing OAI-ORE Resource Maps. ATOM, RDF/XML, N3, N-Triples, Turtle and RDFa)
  • Foresite Explorer (Visualization of Relations)
  • WordPress plug-in (creating Resource Maps for WordPress posts and pages)

Steps[edit]

The basic steps to integrate OAI-ORE to eSciDoc (regarding publication data for start) would be:

  1. Create mapping from eSciDoc Publication Item to ore
  2. Create mapping from ore to eSciDoc Publication Item
  3. Make sure that every resource has its own URI
  4. Expose oai_ore over OAI-PMH
  5. Implement http part
  6. Enable SWORD deposit of ore data

OAI-ORE in use[edit]

This is just an extract of systems supporting OAI-ORE:

  • EPrints
  • Fedora
  • DSpace
  • Microsoft Zentity
  • MyExperiment.org
  • arXiv.org
  • Flickr
  • Oxford Research Archive
  • Word Press
  • Amazon

Related Material[edit]

Open Archives Initiative Object Reuse and Exchange

Portable Document Format

Uniform Resource Identifier

Resource Description Framework

Enhanced Scientific Documentation

Virtueller Raum Reichsrecht

Publication Management

Extensible Markup Language

Open Archives Initiative Protocol for Metadata Harvesting

Simple Web-service Offering Repository Deposit

Flexible Extensible Digital Object Repository Architecture

Retrieved from "https://colab.mpdl.mpg.de/mw010/index.php?title=OAI-ORE&oldid=57887"