Page History

• https://www.pidwijzer.nl/en - Persistent Identifier Guide from Dutch Digital Heritage Network
• • • no mention of ARKs?
• jk and dw did first ARK workshop. Was very nice. Donny shared copy of slide deck with call participants

dw: clarify messaging around v.18 being "current" (elaborate on this?) vs e.g. v.36

jk: agreed we should clarify this. punting for now in favor of existing agenda items.

Final discussion of WG homepage review

• KH: counting ARKs via API vs survey (pros/cons)

IETF standardization update

• ARK as URN namespace ? Doesn't preclude pursuing as separate IETF RFC, eg, DOI is getting a URN namespace
  • should be very easy, doesn't require using urn: in front of ARKs
  • would need to remove spec's discussion of URNs and DOIs (a URN namespace)
  • would need to verify a few char set conflicts
• ARK as API rather than as identifier? ARK as centralized silo rather than as distributed (see GJ's April 10 email about n2t)
• Current ARK draft expires April 20

• URN namespace
  • namespaces: https://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml
  • see e.g. https://www.iana.org/assignments/urn-formal/doi

ARK spec transition

* what to call before and after -- call them? V.I and V.II ? old and new?
* add those names to new spec, and add section about transition?

• blog post https://arks.org/blog/upcoming-changes-to-the-ark-specification/
• Changes (complete?):
  • NAAN should be preceded by "ark:", as in ark:12345/x7th8, but the the V.I format should also be accepted as valid in perpetuity, ie, no links will break because of the transition
  • NAAN can be 1 or more betanumerics (no length limit mentioned)
  • ARK chars:    =   ~   *   +   @   _   $        %   -   .   /
       this removes #, adds ~
  • inflections: add ?info  (with ? and ?? reserved for future use, but undefined; ok to keep using them as you do for now)
  • For received ARKs, implementations must support a minimum length of 255 octets for the string composed of the Base Name plus Qualifier
• Draft Transition Plan

  Overall impact should be minimal. The fewer NAANs you deal with, the easier. Timings T1, T2, ..., T6 to be determined later.

  1. If you produce ARKs, by time T1 you should produce ark:12345 instead of ark:/12345

  2. If you produce ARKs but only ever produced new format (ark:/12345) ARKs, by time T2 you should prepare to receive your own ARKs in the old format (because others may unwittingly reformat your ARKs)

  3. If you receive or resolve ARKs, by time T3 you should accept either ark:12345 or ark:/12345, and plan to do that in perpetuity.

  4. If you receive or resolve ARKs, by time T4 you should accept ARKs at least as long as 255 octets.

  5. If you validate ARKs, you should by time T5 make sure your validation is relaxed enough to not reject new format NAANs, ARKs with ~ or #, and Name and Qualifier parts longer than 128 octets.

  
  6. If you receive or resolve ARKs, by time T6 you should recognize ?info and (a) not flag it as an error, (b) return metadata or return something other than 404 (eg, return the object as if no inflection).