Page History

...

Note: Questionable goals are in red

For Identifiers

...

(just the complete URI and local part)

1. Identifiers must be permanent
2. Identifiers must permanently resolve to a digital object
3. Simplicity (of description and implementation)Support for OAI-ORE structuring
4. Support for vitality checking
5. Compatible with the Handle System and supports Handle System metadata
6. Needs to support multiple repositories and naming schemes
7. Makes sense in context of VIVO, arXiv, OAIS (CUL), Voyager Catalog, and WorldCat
8. Compatible Local part should not be Cornell branded so that it is compatible with multi-institution collections where Cornell branding is inappropriateSupport for "private" identifiers (e.g. for dark archive or internal digital objects. Generally, these identifiers should be branded to Cornell through the use of a Cornell-based DNS name for the full URI/resolver. It should also be possible to use the local part with non-Cornell resolver for consortia and other non-Cornell-branded needs (cf. DOI, handle; not our purl)
9. Identifiers should be short (so use 26 letters plus numbers)
10. Identifiers should be easy to copy by hand - separate every 4 characters with a dashIdentifiers should be (mostly)
11. opaqueIt must be possible to support opaque identifiers
12. Must be resolvable through a web browser
13. Must be unique without the DNS name portion of the URL
14. Should include a check digit

...

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
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
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?

...