-
Notifications
You must be signed in to change notification settings - Fork 9
2022 02 08 Technical WG Agenda and Notes
John Kunze edited this page Aug 5, 2024
·
1 revision
---
confluence-id: 230819906
confluence-space: %%CONFLUENCE-SPACE%%
---
Created by John Kunze, last modified on Feb 08, 2022
08 Feb 2022
- Mark Phillips John Kunze Karen Hanson Curtis Mirci Dave Vieglais Tom Creighton
| Item | Who | Notes |
| Announcements | 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 |
|
| Calls for papers, submission deadlines, upcoming meetings: Calendar of events | KH very probably be speaking at CNI | |
| Any news items we should blog about? | JK: blog about/ tweet about RFC news? invite people to ark@ietf.org DV: could we take advantage to attract review? |
|
| Reschedule to meet on hour earlier? | all: ok | |
| 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? |
JK: are people ok with ark@ietf.org for wider review, reserve googlegroup for private discussion? TC, MP: ok All: "use good judgement" in sending to ark@ietf.org |
|
| 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 specDV: raising hand |
|
| Planning transition to new spec. Would like to propose a joint operation with Outreach WG. | DV: start by communicating should include a list of changes TC: it will be hard to transition since we use colons as separators |
- John Kunze identify people not yet signed on to ietf list
- John Kunze Dave Vieglais draft spec section on URL encoding recommendations; consider what to say about publishing hyphens, eg, discouraged except where expected, as in UUIDs? (ask Smithsonian about their practice)