Versions Compared

Old Version 25

changes.mady.by.user John Kunze

Saved on

compared with

New Version Current

changes.mady.by.user John Kunze

Saved on

Key

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

...

The Technical Working Group (WG) oversees development and maintenance of specifications, software, and servers that support infrastructure for the ARKs-in-the-Open (AITOARK Alliance (ARKA) community. Examples include ARK standardization, code for counting ARKs, and global resolver replication.

Objectives

  1. Standardization.
    2. Review the ARK specification so that the authors, who are WG members, can finalize it and submit it to the IETF for publication as an Internet RFC.NAAN procedures. Adapt current CDL procedures for updating NAANs and registering new NAANs so that these maintenance activities can be shared by the community, eg, on github. (The NAAN registry that CDL currently maintains is a text file of globally unique 5-digit Name Assigning Authority Numbers (NAANs) reserved for organizations that wish to assign ARKs.)
  2. Work with standards bodies (IETF, NISO, W3C, etc) to adopt the ARK spec.
  3. Design and review '?info' inflection for returning human- and machine-readable metadata.
  4. Global ARK resolver. Guide the development and hosting of the N2T.net resolver.
  5. Counting ARKs. Work with the Outreach Working Group
    6.  to
  6. to implement mechanisms (eg, surveys, APIs) to measure ARK usage world-wide.

Deliverables

  • Kickoff: clarify objectives and assign roles for (a) standardization and (b) NAAN procedures designers; spec authors articulate areas they think are problematic

  • Months 1-9: several rounds of review, feedback, and revision for (a) and (b), including public review via the arks-forum list; NAAN procedures are piloted

  • Months 10-12: feedback and review of '?info' inflection for returning human- and machine-readable metadata; ARK spec submitted to IETF

  • Months 13-15: recruit NAAN registry workers; deal with spec feedback from the IETF

  • Months 16-18: further refinements to procedures; “counting ARKs” project design and prototyping then begins

  • Months 19-20: counting ARKs prototype is tested

  • Month 21: updated WG objectives and deliverables for the coming year, with an accordingly updated overall AITO roadmap

Resources

  1. Support the Outreach WG in a liaison with the IIIF community.
  2. Work with standards bodies (IETF, NISO, W3C, etc) to adopt the ARK spec.

Deliverables

  • A declarative schema (e.g. JSON Schema) for NAAN entry record, for validation.
    • schema definition
    • adjusted tooling to work with schema
    • tool to generate the ANVL format from json for 3rd party consumers
  • Transition to new ARK spec.
  • Spin off a Persistence Statements group (charter, timeline)
  • Investigate moving arks.org from a Wordpress site to a github pages site
  • Move lyrasis confluence wiki content to github.

Resources

Working Group Members

Meeting Times

Teleconferences are generally held once a month,  1708:00-18:00 UTC09:00 San Francisco time, on the third Mondaysecond Tuesday. Connection details included in calendar invitations.

Communication Channels

aitoarka-technical-wg@googlegroups.com, archived at https://groups.google.com/forum/#!forum/aitoarka-technical-wg

IETF discussion list: https://www.ietf.org/mailman/listinfo/ark

Agendas and Notes

** add standing agenda item: "ARK spec transition report" **

Create from template
blueprintModuleCompleteKeycom.atlassian.confluence.plugins.confluence-business-blueprints:meeting-notes-blueprint
contentBlueprintId89dc2a6044280a52-0dcfb7ed-47164e6d-908289fc-166f06cec1395e290d7766c7
templateName89dc2a6044280a52-0dcfb7ed-47164e6d-908289fc-166f06cec1395e290d7766c7
title20202024-MM-DD Technical WG Agenda and Notes
buttonLabelGenerate new Agenda/Notes link

...