wiki-archive/twiki/data/GUID/ARK.txt,v

head	1.9;
access;
symbols;
locks; strict;
comment	@# @;


1.9
date	2005.10.11.17.11.04;	author DonaldHobern;	state Exp;
branches;
next	1.8;

1.8
date	2005.10.11.17.09.55;	author DonaldHobern;	state Exp;
branches;
next	1.7;

1.7
date	2005.10.11.17.07.39;	author DonaldHobern;	state Exp;
branches;
next	1.6;

1.6
date	2005.10.11.17.06.54;	author DonaldHobern;	state Exp;
branches;
next	1.5;

1.5
date	2005.10.11.16.11.58;	author DonaldHobern;	state Exp;
branches;
next	1.4;

1.4
date	2005.10.11.16.05.48;	author DonaldHobern;	state Exp;
branches;
next	1.3;

1.3
date	2005.09.21.03.37.10;	author MattJones;	state Exp;
branches;
next	1.2;

1.2
date	2005.09.13.15.54.17;	author DonaldHobern;	state Exp;
branches;
next	1.1;

1.1
date	2005.09.13.15.54.03;	author DonaldHobern;	state Exp;
branches;
next	;


desc
@
.
@


1.9
log
@
.
@
text
@---+++ Archival Resource Keys (ARKs)

---++++ Links
   * *[[http://www.cdlib.org/inside/diglib/ark/][Inside CDL: Archival Resource Key]]* ([[http://www.cdlib.org/inside/diglib/ark/]]) - Overview of technology
   * *[[http://www.cdlib.org/inside/diglib/ark/arkcdl.pdf][Towards Electronic Persistence Using ARK Identifiers]]* - Excellent overview of the issues that ARK Identifiers are trying to address ("...what people really want is the kind of convenient access to which they have become accustomed on the Web. ...what we're looking for are persistent _actionable_ identifiers, where an _actionable_ identifier is one that widely available tools such as web browsers can use to convert a simple "click" into access to the object or to a doorway leading directly to access...")

---++++ Form
An ARK has the following general form:
   [http://NMAH/]ark:/NAAN/Name[Qualifier]

where:
   * *NMAH* is the *Name Mapping Authority Hostport*, a (temporary) internet address to which ARK service requests may be sent - this is optional and not part of the ARK for the purpose of identity comparison
   * *NAAN* is the *Name Assigning Authority Number*, an assigned identifier unique to the body which originally assigned this ARK
   * *Name* is a semantically opaque unique name assigned by the NAAN
   * *Qualifier* is an optional service entry point supported by the NMA to access hierarchical components of the identified object, or versions of the object

For example:
   http://foobar.zaf.org/ark:/12025/654xz321/s3/f8.05v.tiff

where:
   * foobar.zaf.org is the NMAH
   * 12025 is the NAAN
   * 654xz321 is the Name
   * /s3/f8.05v.tiff is the Qualifier

The following three ARKs are considered identical:
   * http://loc.gov/ark:/12025/654xz321
   * http://rutgers.edu/ark:/12025/654xz321
   * ark:/12025/654xz321

Any ARK provides access to three things:
   * The ARK itself provides access to a data object
   * The ARK followed by a single question mark, '?', provides access to a metadata record
   * The ARK followed by two question marks, '??', provides access to a commitment statement from the current provider (a service agreement)

---++++ Discussion

From Rod Page:

Another GUID system that might be of interest is ARK ([[http://www.cdlib.org/inside/diglib/ark/]]). The site describing this approach has a nice discussion of the issues surrounding persistent identifiers, and various solutions such as DOIs and URNs (of which LSIDs are an example). I think this system should be looked at closely, before we limit discussion to DOIs or LSIDs.

---+++++ Categories
CategoryARK@


1.8
log
@
.
@
text
@d9 1
a9 1
   [[http://NMAH/ark:/NAAN/NameQualifier [http://NMAH/]ark:/NAAN/Name[Qualifier] ]]
@


1.7
log
@
.
@
text
@d9 1
a9 1
   [ http://NMAH/ ]ark:/NAAN/Name[Qualifier]
@


1.6
log
@
.
@
text
@d9 1
a9 1
   [http://NMAH/]ark:/NAAN/Name[Qualifier]
@


1.5
log
@
.
@
text
@d7 29
@


1.4
log
@
.
@
text
@d5 1
a5 1
   * *[[http://www.cdlib.org/inside/diglib/ark/arkcdl.pdf][Towards Electronic Persistence Using ARK Identifiers]]* - Excellent overview of the issues that ARK Identifiers are trying to address ("...what people really want is the kind of convenient access to which they have become accustomed on theWeb. Instead, what we're looking for are persistent _actionable_ identifiers, where an _actionable_ identifier is one that widely available tools such as web browsers can use to convert a simple "click" into access to the object or to a doorway leading directly to access")
@


1.3
log
@
.
@
text
@d5 1
@


1.2
log
@
.
@
text
@d10 1
a10 1
Another GUID system that might be of interest is ARK (http://www.cdlib.org/inside/diglib/ark/). The site describing this approach has a nice discussion of the issues surrounding persistent identifiers, and various solutions such as DOIs and URNs (of which LSIDs are an example). I think this system should be looked at closely, before we limit discussion to DOIs or LSIDs.
@


1.1
log
@Initial revision
@
text
@d8 1
a8 1
From RodPage:
@