Page History

...

1. Supports billions of identifiers with very fast resolution
2. Robust architecture and implementation - a highly available system
3. Compatible with the Handle System and supports Handle System metadata - Should we support authorization, storage of checksum, multiple resolution, storage of arbitrary XML documents (ala cugir buckets) – these facilities not used by CUL handles at present
4. 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)
5. Support for OAI-ORE structuring
6. Need to avoid unbounded generation of surrogate persistent identifiers
7. Should support multiple delivery formats for an identifier _ (does this mean doing content negotiation at the resolver?)_
8. Must support splitting collections (what does this mean?)
9. Need a lightweight understanding of identifier equivalence
10. Need a way to integrate outside PIDs with Cornell (what does this mean? examples?)
11. The identifiers and the associated content should be easily discoverable by Google
12. The overall system should integrate well with the "web architecture"
13. Should have a PID corresponding to every Cornell NetID and potentially other non-digital resources, not necessarily at Cornell?

...