For Identifiers (just the complete URI and local part, not about mechanisms)
#permanent
The PID system should provide long term support for resolving identifiers.
#permanently resolve to a digital object
The Identifiers should be permanently resolvable via HTTP to a digital resource. The bits that comprise the digital resource may change. It is not a goal of the PID system to ensure fixity of digital resources.
#URL
The PIDs should conform to the URL RFC1738
#resolvable through a web browser
Since the PIDs are URLs they could be used as the href attribute in an <a> element in HTML.
#unique within our PID system without the DNS name portion of the
If the ID schema has a DNS name then all PIDs in the system should be unique even with the DNS name removed. This goal is trivially satisfied if there is only one DNS name used by the PID system. If there are more than one DNS names used in the system care must be taken to ensure that goal is met.
#works with existing systems
The PIDS should work with existing systems such as VIVO, arXiv, OAIS (CUL), Voyager Catalog, and WorldCat etc.
#Simplicity
#support for a local namespace prefix and an identifier part
The hope is that the URL can be of the form http://hostname.com/localNamespacePrefix/identifierPart
or something similar.
#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.
#Local part should not be Cornell branded
To encourage the possibility of using the PIDs across intuitions, the PIDs should not be branded.
#may be surrogate for physical object
The digital resource returned by the PID resolver might not be the thing identified by the PID, but a surrogate for a resource that cannot be transported easily via HTTP.
#should be short
Please add comments about this goal. How short? Should there be a length limit (which implies a limit to the number of things that can be resolved)?
#should be easy to copy by hand
Please add comments about this goal. Adding dashes between every 4 digits of the identifier may be a way to improve the easy of copying the PIDs.
For Resolver and System
#Supports billions of identifiers
Please add comments about this goal.
#Robust architecture
Please add comments about this goal.
#Robust implementation
Please add comments about this goal.
#ability to request metadata about the identifier
Please add comments about this goal.
#lightweight understanding of identifier equivalence
Please add comments about this goal.
#should be easily discoverable by Google
Please add comments about this goal.
#integrate well with the web architecture
This should be satisfied by earlier goals.
#vitality checking
Please add comments about this goal.
#Need to avoid unbounded generation of surrogate persistent identifiers
Please add comments about this goal.
#PID corresponding to every Cornell NetID
Please add comments about this goal.
#useful error when check digit is wrong
Please add comments about this goal.
Governance Issues
#Requires payment to external organization
Please add comments about this goal.
#Can continue resolve IDs in absence of external organization
Please add comments about this goal.