Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Supports billions of identifiers with very fast resolution
  2. Robust architecture and implementation - a highly available system
  3. 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)
  4. Need to avoid unbounded generation of surrogate persistent identifiers
  5. There should be a separate service request using the identifier as a parameter that gives metadata about the identifier
  6. Need a lightweight understanding of identifier equivalence
  7. The identifiers and the associated content should be easily discoverable by Google
  8. The overall system should integrate well with the "web architecture"
  9. Should have a PID corresponding to every Cornell NetID, using 303 redirect to an appropriate surrogate.
  10. Should give useful error when check digit is wrong.

...

  1. Any extra characters for error correction (as an extension of any possible error detection)
  2. Attempt to create a fixed-length of fixed-syntax form (that would aid recognition but cost in flexibility/length)
  3. 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)