 |
Open Archives Initiative Object Reuse and Exchange |
 |
|
Open Archives Initiative Object Reuse and Exchange |
|
This document collects together descriptions of tools and additional resources useful when implementing the OAI-ORE standards.
This user guide is one of several documents comprising the OAI-ORE specifications and user guides. This document is intended for implementers working with ORE. Readers seeking a high-level understanding of the motivation for ORE, and of the solution it provides, should read the ORE Primer.
1. Introduction
2. Validation tools and services
2.1 ORE specific validation tools and services
2.2 Generic validation tools and services useful for ORE implementers
3. Libraries and toolkits
4. Additional resources
A. Acknowledgements
B. Change Log
In order to use ORE Resource Maps there must be software to create, write, validate, parse and interpret them. Implementers are encouraged to use available tools and libraries where possible to avoid unnecessary duplication of effort and to reduce errors. Tools are grouped in the following sections:
Finally, section 4 describes additional resources including the ORE logos.
It is expected that this document will be updated as more tools and services become available.
| Tool | Implementer | Description |
|---|---|---|
| ORE Atom Resource Map Validator | LANL |
This tool validates Atom XML Resource Maps. A Resource Map can be pasted into a form, or a URI can be provided. Validation results are provided in HTML or as an IsoSchematron Report. The tool also allows cross-walking the Atom Resource Map to RDF, and an RDF/XML as well as an SVG output is available. The tool can also be called remotely using an HTTP GET syntax that is documented in the Help section. |
| Schematron Schema for the Resource Map Profile | LANL |
This Schematron Schema can be used to valid Atom Resource Maps. It is the Schema that is also used by the ORE Atom Resource Map Validator. |
| Tool | Implementer | Description |
|---|---|---|
| W3C Markup Validation Service | W3C |
The site provides in interactive web form to validate an Atom feed. This is useful for ORE because all ORE Resource Maps in Atom must be valid Atom entry documents. This service allows validation not only by entering a URI of the feed to validate, but also by file upload or by direct input. |
| FeedValidator | feedvalidator.org |
The site provides in interactive web form to validate an Atom feed by entering a URI for the feed. This is useful for ORE because all ORE Resource Maps in Atom must be valid Atom entry documents. This site is typically more up-to-date than the W3C validator (which uses the same code) but does not allow pasted documents to be validated. |
| W3C RDF Validation Service | W3C |
The site provides in interactive web form to validate an RDF document. This is useful for ORE because all ORE Resource Maps in RDF/XML or other RDF serializations must valid RDF documents. This service allows validation not only by entering a URI of the RDF to validate, but also by direct input. |
| Tool | Implementer | Description |
|---|---|---|
| Java library | Foresite Project (Richard Jones, HP) | Java library for constructing, parsing, manipulating and serializing OAI-ORE Resource Maps. The library supports parsing and serializing in: ATOM (ORE 0.9 version only), RDF/XML, N3, N-Triples, Turtle and RDFa. |
| Python library | Foresite Project (Robert Sanderson, University of Liverpool) | Python libraries for constructing, parsing, manipulating and serializing OAI-ORE Resource Maps. The library supports parsing and serializing in: ATOM (ORE 1.0 and 0.9), RDF/XML, N3, N-Triples, Turtle and RDFa. |
| GRDDL crosswalk from Atom XML to RDF/XML | LANL |
This GRDDL XSLT takes an Atom XML Resource Map as input, extracts RDF triples from it in a manner that is compliant with the ORE Data Model, and returns the result as RDF/XML. |
| ORE Namespace document | LANL and Eduserv Foundation |
The namespace used by ORE specific elements listed in the
Vocabulary is described formally in an RDF
namespace document available at
|
The ORE Logo used at the top right of this page is available in a number of different sizes and in a form better suited for use as a small icon. It is made available for use on Web pages, in publications, presentations, and promotional materials without requesting permission. If the ORE Logo is used in media that support hyperlinks (such as HTML and PDF) it is recommended to hyperlink the logo to http://www.openarchives.org/ore/toc. See the ORE Logos page for details.
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).
This work is licensed under a Creative Commons Attribution-Share Alike 3.0 Unported License.
Use of this page is tracked to collect anonymous traffic data. See OAI privacy policy.