2023-02-14 Technical WG Agenda and Notes

Community Leaders (chairs and co-chairs email list set up) arka-conduct@googlegroups.com

https://arks.org/community doesn’t load, but https://arks.org/community/ does …

John wants a "send an email" form to put on the code of conduct page. So no need to give out an email address of individual chair or co-chair.

• there are services to embed a contact form on a static website, e.g. netlify forms (https://www.netlify.com/products/forms/), backed by "serverless functions" (ephemeral container init and running)
• good to have something that works with github pages (where we want to migrate to)

* nice to have blog post persistence statements once there's some more concrete content to share

https://docs.google.com/document/d/1n5ETS45fHqJefu74vXKLFZhrXm_VmIB7jT2Yk4zR2_E/edit#heading=h.v83orrqv3vnr

Migration from confluence, perhaps consider something like: https://github.com/sjones4/confluence-to-github

ensure deliverable(s) associated with each objective:

•     json schema for NAAN entry record for validation.

Ongoing collection of ARK spec update use cases

Spec transition implementation – is someone willing to lead?

https://docs.google.com/document/d/1Yh60RajuAqlBox94iW47_43oeOKEuyzenXExggtpGdU

updates:

• length of NAAN is variable. Not restricted to 5-digit numerical values
• no slash after colon (ark:12345/key) is the canonical form, but old form (ark:/12345/key) must still resolve.

Need concise description of changes.

Persistence Statements / "Durability"? strawman

MVP (minimum viable product)

strawman mvp: https://docs.google.com/document/d/1Ej8wup8mK3yS39AdwHDJSclPCh3K9zP-RlkPKaqmxQ4/edit?usp=sharing

objective: be less overwhelming than https://datascience.codata.org/articles/10.5334/dsj-2017-039/

NR - non-reassignment
OP - opaque
CC - check character
resolvable