JK: first (mailchimp) newsletter failed to go out today; will investigate; suspect RSS feed failure BC: issue appeared on French forum concerning how n2t normalizes hyphens out of ARKs before redirecting JK: yes, feature rather than bug; but what do others think? (no disagreement) Action: BC will send ARK Alliance announcement to French forum
upcoming meetings, calls for papers, submission deadlines
PASIG
ARKA newsletter
Feb 22 IETF submission cutoff
Action: JK will inquire about PASIG deadline (since it wasn't available online) Action: All: please think about topics for the ARKA newsletter JK: Feb 22 IETF cutoff is just a temporary outage of IETF submissions for a period surrounding each meeting
RM: section 1.3 – is it true that "high quality access" is the central duty, and doesn't "high quality" risk being confused with "access to high-quality objects" JK: definitely not meant to be a statement about quality of the objects, but quality of the access; persistent access is still very important, but the ability to set expectations (weak or strong) could as easily enable a powerful mechanism to promise the opposite (eg, single-use links) Action: clarify GJ: what is the use case of multiple suffixes? could we clarify that multiple suffix normalization is for comparing arks rather than publishing them? GJ: general notion of what normalization is for could use clarification, not just for comparison, but also for resolution; should suffix order matter? why? Action: clarify RM: need to clarify whether changing order of suffixes is equivalent CM: what if suffixes don't match? ok to resolve to parent object so if you can't normalize the user at least sees something MP: yes, at UNT we might change our minds, and will resolve older qualifiers to the parent object
Spec to do:
normalization of encodings
point to structured area for ongoing work (arks.org/labs ?)
JK: what's left before RFC submission; where do we continue our work -- using arks.org/labs? JK: need to catch up shoulder spec docs with shoulder FAQ
Wikipedia ARK - is this as much Tech WG as Outreach WG?
JK: arks.org rollout brought wikipedia page to the fore; some of the problem is that the page has real overlap with spec (Tech WG) BC: recently reviewed French wikipedia page and will forward results JK: Action: go back and review where we got with outreach wg
Planning for feature support (optionality of "/", relaxed limits on NAANs and string lengths)
soft or loud, internal vs everyone implementing ARKs
reference implementation could help?
target date?
URI scheme?
Action items
Bertrand Caron will send ARK Alliance announcement to French forum