...

• ObjectUri
• W3 TR on URI/URN/URL (2001): http://www.w3.org/TR/uri-clarification/^{Image Removed}
• Commons ID: http://jakarta.apache.org/commons/sandbox/id/^{Image Removed}

• Code Block
  java.util.UUID

  : http://java.sun.com/j2se/1.5.0/docs/api/java/util/UUID.html^{Image Removed}
• Java UUID Generator (JUG): http://jug.safehaus.org/^{Image Removed}

Following from the recent discussion of persistent identifiers in DSpace, I thought it would be a good idea to define exactly what our requirements are. I will try to avoid using the term "persistent" because it is a loaded term that has limited meaning in the context of long-term preservation – if we assign a global identifier to a resource, it should be assumed that the identifier can and will survive as long as the object does. The resolution aspect of persistent identification is the key thing to be concerned about in this context, but that is far beyond the scope of what DSpace can take responsibility for.

...

Overview: Scoping of Identifier Schemes

...

Image Added

The following figure attempts to illustrate the problem of object identification within DSpace. In particular, it highlights the fact that:

...