2022-02-08 Technical WG Agenda and Notes

Texas Conference on Digital Library proposal for a PID workshop with a strong representation of ARKs. 
https://www.tdl.org/tdl-events/tcdl/2022-tcdl/

Recently hit 900th NAAN registration

KH very probably be speaking at CNI

Status of ARK spec in RFC Editor queue:

===
The Independent Submissions Stream RFC Editor (ISE) has accepted to work on the document with a view to publishing it as an Informational RFC outside the IETF. The ISE's next task is to review the work and then commission some independent reviews. The process from here to a published RFC could be between 3 and 6 months.

We have established an email list within the IETF to discuss the work: although this list has so far been quiet, it is very early days.

JK: have you all signed up for ark@ietf.org ? please remember to do
Action: verify who's on the list

Seeding the ark@ietf.org discussion

• which discussion should we keep more private on the googlegroup? how do we decide?

Anticipating questions about URL encoding

• includes question of colon ':' and '/' and when to percent-encode them

DV: I go back and forth on encoding ark in query string
TC: maybe we should say there's flexibility (like the URI spec), but acknowledge that people tend to like human readable
DV: would be good to have a simple recommendation on publishing ARKs
JK: can we take a page from the web archiving folks?
MP: https://github.com/iipc/urlcanon
JK: use the word "publishing an ARK"?
TC: how about the word "canonical" in prose and link tags?
JK: if we're talking canonical, maybe UUIDs should have hyphens even if we discourage hyphens elsewhere?
JK: who wants to help write section of the ARK spec
DV: raising hand

DV: start by communicating should include a list of changes
TC: it will be hard to transition since we use colons as separators