Page History

...

The hope is that the URL can be of the form http://hostname.com/localNamespacePrefix/identifierPart or something similar. The localNamespacePrefix could also be called a collectionPrefix. The resolver system should place no additional restrictions on the identifierPart beyond conforming URL syntax.

#support for opaque identifiers

In an attempt to avoid problems in situations where the labels associated with resources change, the PIDs should support partially opaque identifiers such as http://hostname.com/170/2a33-ffff instead of http://hostname.com/SuperMegaCollection/WalterCarlos1^{Image Added}. Since the resolver system places no additional restrictions on the identifier part, we cannot stop systems from requesting new identifiers with a syntax that they attach meaning to.

Ex. A collection administrator might register the following Identifiers: http://resolver.cornell.edu/170/article23332^{Image Added} -> http://collectionX.cornell.edu/article/23332^{Image Added} http://resolver.cornell.edu/170/article23332.pdf^{Image Added} -> http://collectionX.cornell.edu/article/23332?format=pdf^{Image Modified} http://resolver.cornell.edu/170/article23332.tex^{Image Added} -> http://collectionX.cornell.edu/article/23332?format=tex^{Image Added}
The resolver system will not attempt to parse these identifiers and will not record or track relationships between identifiers.

#Local part should not be Cornell branded

...