DO NOT USE, SEE CURRENT ORE SPECIFICATIONS

ORE Specification and User Guide - Open Issues

2 March 2008

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

This document was part of an alpha release and has been superseded.

This version:
http://www.openarchives.org/ore/0.2/open-issues
Latest version:
http://www.openarchives.org/ore/open-issues
Previous version:
http://www.openarchives.org/ore/0.1/open-issues
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.  This document lists open issues in the OAI-ORE specification and user guide documents that make up the OAI-ORE standards.


1. Issues to be considered

The following topics are agenda items for ORE Technical Committee discussions before the beta release.

1.1 Aggregation without enumeration

There is considerable interest in extending the ORE Data Model to handle the notion of aggregation without explicitly enumerating all of the Aggregated Resources. This would likely involve a URI templating mechanism.

1.2 Choice regarding external vocabularies

Should the ORE select or promote certain vocabularies as preferred or not?

2. Open Issues noted in specific documents

The following issues are noted in the current OAI-ORE specification and user guide documents and have yet to be resolved. Each section refers to a specific document and a particular issue may appear in more than one document.

2.1 ORE Specification - Representing Resource Maps Using RDF Syntaxes

2.1.1 Choice of RDF XML Profile

Should this specification say:

2.1.2 Additional Relationships in RDF XML

Need description of how to include Additional Relationships in the Resource Map.

2.1.3 RDFa Examples

Need fuller description of RDFa, examples?

2.1.4 RDFa Example URIs

Add some examples of URIs in RDFa.

2.1.5 Additional Relationships in RDFa

Need description of how to include Additional Relationships in the Resource Map in RDFa.

2.2 ORE User Guide - Resource Map Discovery

2.2.1 Links in HTML pages

HTML does not provide appropriateattributes in the A and IMG elements to link to a Resource Map as well as the target resource. This section suggests either the addition of extra attributes to the A and IMG elements (which would make otherwise valid HTML documents invalid), or re-purposing an existing attribute.

2.3 ORE Specification - Abstract Data Model

2.3.1 Definition of ore analogousTo

The definition of ore:analogousTo needs to be clarified.

2.3.2 Constraints on RDF Graph

There need to be some additional constraints on the RDF Graph expressed by a Resource Map, in addition to the stated connectedness. For example, the use of the predicates ore:describes and ore:aggregates should probably be limited to the single subgraph rooted in the node denoting the Resource Map, thereby preventing the expression of nested aggregations in a single Resource Map.

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-03-02 simeon public alpha 0.2 release
2007-12-10 simeon public alpha 0.1 release

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.