...
- Supports billions of identifiers with very fast resolution
- Robust architecture and implementation - a highly available system
- Support for "private" identifiers (e.g. for dark archive or internal digital objects) (this is about metadata stored with id and facilities provided depending on it)
- Need to avoid unbounded generation of surrogate persistent identifiers
- There should be a separate service request using the identifier as a parameter that gives metadata about the identifier
- Need a lightweight understanding of identifier equivalence
- The identifiers and the associated content should be easily discoverable by Google
- The overall system should integrate well with the "web architecture"
- Should have a PID corresponding to every Cornell NetID, using 303 redirect to an appropriate surrogate.
- Should give useful error when check digit is wrong.
...
- Any extra characters for error correction (as an extension of any possible error detection)
- Attempt to create a fixed-length of fixed-syntax form (that would aid recognition but cost in flexibility/length)
- Support for "private" identifiers (e.g. for dark archive or internal digital objects) (this is about metadata stored with id and facilities provided depending on it)