You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Date

Attendees

Goals

Discussion items

ItemWhoNotes
Announcements

Any news items we should blog about? Any calls for papers, submission deadlines, upcoming meetings we should note? Please add to Calendar of events.


At arks.org/resources updated current spec link (v.18) from an external link to a PDF hosted onsite; updated current spec to landing page for IETF specs (easier to keep updated)

Final discussion of WG homepage review

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


IETF standardization update

  • ARK as URN namespace (in addition to other IETF); might be easy
  • 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


ARK 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


Action items

  •  
  • No labels