]> 2009-02-25T10:00:00-05:00 2009-02-25T11:30:00-05:00 Background:
-----------

Historically, published scientific research could include a description of an experiment that an independent party could use to reproduce the experiment with the same results, confirming the research. Modern research in the field of earth science often depends on terrabytes of data captured from remote sensing instruments, complex computer algorithms that undergo numerous changes over the year. A single result could be the result of the work of hundreds of individuals over decades. The representation of the measurements, algorithms and all the other artifacts of experimentation leading to that result becomes a daunting problem. A key to handling this representation is a good scheme for persisent identifiers.

Identifiers:
------------

Persistent identifiers seem like a simple problem. Just make a good URL and don't change it.[1] This sounds good in theory, but is difficult to maintain forever. Many other schemes have been proposed to attack various aspects of the problem of identification, with various advantages and disadvantages. I will introduce this topic and briefly describe some of the concerns with using identifiers specifically in the context described above, and some of the characteristics of various identifier schemes.

References:
-----------

[1] "Cool URIs Don't Change." http://www.w3.org/Provider/Style/URI
Some identifier schemes:

[2] "Naming and Addressing: URIs, URLs, ..." http://www.w3.org/Addressing/

[3] "Object Identifer (OID)" http://www.oid-info.com/

[4] "The Digital Object Identifier (DOI) System." http://www.doi.org/

[5] "Persistent Uniform Resource Locator" http://purl.org/

[6] " A Universally Unique IDentifier (UUID) URN Namespace" http://www.ietf.org/rfc/rfc4122.txt

[7] "XRI (Extensible Resource Identifier)" http://www.xdi.org/xri-and-xdi-explained.html

[8] "ARK (Archival Resource Key)" http://www.cdlib.org/inside/diglib/ark/arkspec.html

The talk is available live on http://www.ustream.tv/channel/umbc-ebiquity-meeting]]>