...
Here is a workshop on PI?s.
Wiki Markup
30 June ? 1 July 2005\| [ http://www.dcc.ac.uk/training/pi-2005/]\]
Lots of excellent papers.
...
3) The ERL reference talks about the trustworthiness of the reference.
Evidently their references include some sort of signature in the reference, which is then compared with the signature of the object. This proves that the user is pointed to what they planned to point to.
SYSTEMS
ARK
Wiki Markup
The Archival Resource Key (ARK) identifier is a naming scheme for persistent access to digital objects (including images, texts, data sets, and finding aids), currently being tested and implemented by the California Digital Library (CDL) for collections that it manages.
An identifier is an association between a string (a sequence of characters) and an information resource. That association is made manifest by a record (in the case of this service, a METS record ) that binds th\[e identifier string to a set of identifying resource characteristics. The ARK identifier is a specially constructed, globally unique, actionable URL. Each ARK links end-users to three things:
- Digital object metadata
- Digital object content files
- A commitment statement made by the CDL concerning the digital object.
And this:
http://www.sspnet.org/files/public/Kunze.htm
...
Handles can store arbitrary data:
http://www.handle.net/hs_manual/server_manual_2.html#SEC3
says:
A handle has a set of values assigned to it and may be thought of as a record that consists of a group of fields. Each handle value must have a data type specified in its <type> field, that defines the syntax and semantics of its data, and a unique <index> value that distinguishes it from the other values of the set. A set of handle data types has been pre-defined for administrative use. (See Handle System Namespace and Service Definition.)
<type> can be any UTF8-string. Handle System users acknowledge, however, that there are potential conflicts for handle clients if users assign types that are not registered and recognized across the user community. How <types> should be defined and how they should be used is currently under discussion. The non-administrative types that have been registered and defined to date are listed below.
- URL: Values of type URL are UTF8-encoded URIs that specify the location of the object identified by a handle.
- EMAIL: Values of type EMAIL are UTF8-encoded email addresses.
PID Pros and Cons:
Characteristic | Store URL. | Store more than 1 URL. | Metadata other than URL. | Tools for administering/configuring | Integration into other tools, browsers,etc. |
|---|---|---|---|---|---|
PURL | Y | N | N | Y | N |
Handle | Y | Y | Y | ||
ARK | Y | Y | Y | ||
DOI | Y | Y | Y | Y | |
OpenURL |
| Y | Y | Y |
...
This paper describes the aDORe repository architecture designed and implemented for ingesting, storing, and accessing a vast collection of Digital Objects at the Research Library of the Los Alamos National Laboratory. The aDORe architecture is highly modular and standards-based. In the architecture, the MPEG-21 Digital Item Declaration Language is used as the XML-based format to represent Digital Objects that can consist of multiple datastreams as Open Archival Information System Archival Information Packages (OAIS AIPs). Through an ingestion process, these OAIS AIPs are stored in a multitude of autonomous repositories. A Repository Index keeps track of the creation and location of all the autonomous repositories, whereas an Identifier Locator reflects
in which autonomous repository a given Digital Object or OAIS AIP resides. A front-end to the complete environment?the OAI-PMH Federator?is introduced for requesting OAIS Dissmination Information Packages (OAIS DIPs). These OAIS DIPs can be the stored OAIS AIPs themselves, or transformations thereof. This front-end allows OAI-PMH harvesters to recurrently and selectively collect batches of OAIS DIPs from aDORe, and hence to create multiple, parallel services using the collected objects. Another front-end?the OpenURL Resolver?is introduced for requesting OAIS Result Sets. An OAIS Result Set is a dissemination of an individual Digital Object or of its constituent datastreams. Both front-ends make use of an MPEG-21 Digital Item Processing engine to apply those services to OAIS AIPs, Digital Objects, or constituent datastreams that were specified
in a dissemination request.
http://comjnl.oxfordjournals.org/cgi/rapidpdf/bxh114v1.pdf
OpenURL
OpenURL 1.0 for Reptilian Brains
http://outgoing.typepad.com/outgoing/2006/03/openurl_10_for_.html