[Fwd: support for oai-ore]

[Yuri-11]

Hi!

here a great news: http://www.openarchives.org/ore/0.1/toc

Some effort to support this? :)


   Abstract

Open Archives Initiative Object Reuse and Exchange (OAI-ORE) defines
standards for the description and exchange of aggregations of Web
resources.


   1. Introduction

The World Wide Web is built upon the notion of atomic units of
information called /resources/ that are identified with URIs such as
http://www.openarchives.org/ore/0.1/toc (this page). In addition to
these atomic units, aggregations of resources are often units of
information in their own right.  Examples of these aggregations are:

   * A simple unordered set, or bag, of resources, such as a collection
     of favorite images from various Web sites.
   * A multi-page, HTML document where the pages are linked together by
     hyperlinks that provide "previous page" and "next page" access.
   * Information available from "social networking" sites, such as
     flickr <http://flickr.com>, YouTube <http://youtube.com>, and
     myspace <http://www.myspace.com>.  Information in flickr, for
     example, consists of an entry page, a single Resource, that links
     to comments or annotations (each existing as a separate Resource),
     and  an image in  multiple sizes and resolutions, each also
     existing as a separate Resource.
   * A scholarly publication stored in an ePrint repository such as
     arXiv <http://arxiv.org> or in a DSpace <http://www.dspace.org>,
     ePrints <http://www.eprints.org>, or Fedora
     <http://www.fedora-commons.org/> repository.  Such a publication
     may appear on the Web as multiple resources, each with an
     individual URI.  The set of resources typically consists of a
     human readable "splash page", that links to the body of the
     publication in multiple formats such as LaTeX, PDF, and HTML.  In
     addition, the publication may have citation links to other
     publications, each existing as one or more resources.
   * An /overlay journal issue/ that aggregates multiple scholarly
     publications as described above, each located in their origin
     repository, into an /issue/.  Issues may be recursively aggregated
     themselves into /volumes/, and then into the /journal /itself.
   * A semantically-linked group of cellular images - each available as
     a Resource resident in repositories from research laboratories,
     museums, libraries, and the like - in the manner implemented in
     the ImageWeb Project <http://imageweb.zoo.ox.ac.uk>.
   * Published scientific results such as those envisioned by [Lynch
     CTWatch <http://www.openarchives.org/ore/0.1/toc#Lynch_CTWatch>]
     that, in addition to the features of the scholarly publication
     described above, incorporate data plus the tools to visualize and
     analyze that data.

A mechanism to associate identities with these aggregations and describe
them in a machine-readable manner would make them visible to Web agents,
both humans and machines.  This could be useful for a number of
applications and contexts.  For example:

   * Crawler-based search engines could use such descriptions to index
     information and provide search results sets at the granularity of
     the aggregations rather than their individual parts.
   * Browsers could leverage them to provide users with navigation aids
     for the aggregated resources, in the same manner that
     machine-readable site maps <http://www.sitemaps.org/> provide
     navigation clues for crawlers.
   * Other automated agents such as preservation systems could use
     these descriptions as guides to understand a "whole document" and
     determine the best preservation strategy.
   * Systems that mine and analyze networked information for citation
     analysis/bibliometrics could achieve better accuracy with
     knowledge of aggregation structure contained in these descriptions.
   * These machine-readable descriptions could provide the foundation
     for advanced scholarly communication systems that allow the
     flexible reuse and refactoring of rich scholarly artifacts and
     their components [Value Chains
     <http://www.openarchives.org/ore/0.1/toc#Value_Chains>].


   2. Specifications

The OAI-ORE specifications are based around the ORE Model described in
ORE Specification - Abstract Data Model
<http://www.openarchives.org/ore/0.1/datamodel>. The ORE Model
introduces the Resource Map that makes it possible to associate an
identity with aggregations of resources and make assertions about their
structure and semantics.

The ORE Model makes use of a number of terms from existing Semantic Web
vocabularies and introduces a small number of new terms particular to
the model. These are described in ORE Specification - Vocabulary
<http://www.openarchives.org/ore/0.1/vocabulary>.

The primary serialization format for Resource Maps is a profile of Atom
and is described in ORE Specification - Resource Map Profile of Atom
<http://www.openarchives.org/ore/0.1/atom>. However, because the ORE
Model is expressed in RDF, Resource Maps may also be serialized in any
format capable of serializing RDF. A GRDDL crosswalk from Atom XML to
RDF/XML <http://www.openarchives.org/ore/0.1/atom-grddl> is provided and
we anticipate that later releases of these specifications will describe
other serializations.




_______________________________________________
Educational mailing list
[hidden email]
http://lists.plone.org/mailman/listinfo/educational