Versions Compared

Key

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

Purpose

The Technical Working Group (WG) oversees development and maintenance of specifications, software, and servers that support infrastructure for ARKs-in-the-Open the ARK Alliance (ARKA) community. Examples include ARK standardization, code for counting ARKs, and global resolver replication. A short 2-3 sentence description of why the working group has been formed and what it will accomplish for the project.

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.)
  3. Work with standards bodies (IETF, NISO, W3C, etc) to adopt the ARK spec.
  4. Design and review '?info' inflection for returning human- and machine-readable metadata.
  5. Global ARK resolver. Guide the development and hosting of the N2T.net resolver.
  6. Counting ARKs. Work with the Outreach Working Group
  7.  to
  8. 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-5: several rounds of review, feedback, and revision for (a) and (b), including public review via the arks-forum list; expect also interaction with the Outreach WG when they send requirements for (c) the “counting ARKs” project, for which design and prototyping then begins

  • Month 6: ARK spec submitted to IETF; NAAN procedures are piloted; counting ARKs prototype is tested

  • Months 7-12: further refinements to procedures; ask Outreach Working Group to identify more orgs with ARKs to be counted; deal with inevitable spec feedback from the IETF

  • Month 11: production-ready procedures in place; production-ready ARK counting is in place

  • Month 12: 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

A list of existing documents and other resources for reference. Add to this list as content is created by the working group.

Working Group Members

Initial proposed members:

  • John Kunze (AG Liaison), CDL

  • Emmanuelle Bermès, BnF

  • Bertrand Caron, BnF

  • ...

List all members, using the wiki @ symbol feature to link their user profile to the document

Meeting Times

List the regular meeting time for the working group, and access information if the working group is open. TBD

Communication Channels

How will the working group communicate? list any Zoom meetings, Slack channels, Google groups etc.

Agendas and Notes

...

Working Group Members

Meeting Times

Teleconferences are generally held once a month, 08:00-09:00 San Francisco time, on the second Tuesday. Connection details included in calendar invitations.

Communication Channels

arka-technical-wg@googlegroups.com, archived at https://groups.google.com/forum/#!forum/arka-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
contentBlueprintId44280a52-b7ed-4e6d-89fc-5e290d7766c7
templateName44280a52-b7ed-4e6d-89fc-5e290d7766c7
title2023-MM-DD Technical WG Agenda and Notes
buttonLabelGenerate new Agenda/Notes link

Children Display
sorttitle
reversetrue