Date
Attendees
Goals
Review proposed specification changes
...
Item | Who | Notes |
---|---|---|
announcements | ||
calls for papers, submission deadlines, upcoming meetings: Calendar of events | ||
normalizing unicode hyphens "Implementors should be prepared to normalize some common invalid characters that may be found in ARKs copy pasted from processed text. For example, when pasting an ARK that was broken during line wrapping, a user may inadvertently introduce newlines and spaces that should be removed, or a variety of dash-like (eg, en dash) Unicode characters that should be removed or converted to hyphens." | GJ: "should be prepared" maybe too vague; perhaps this should be "best practice" or "it is recommended..." | |
more diagrams (2) with more diagrammed ARK part names | GJ: having two diagrams that are so similar is confusing TC: I'd agree; I hadn't seen the check digit language before | |
new terms:
| TC: who is the audience for the resolver chain discussion; would be good to have some use cases | |
recommend/exemplify link header with resource response? | n/a | |
recommend/exemplify link header with metadata response? https://n2t.net/e/pub/ark.html#name-overview-of-the-http-url-map | KH: I like the link header example | |
adding n2t.net as infrastructure; current statement is weak https://n2t.net/e/pub/ark.html#name-finding-a-name-mapping-autho | JK: we could use a statement about n2t.net as infrastructure; volunteers? | |
non-normative pointer to ARK extensions at arks.org/specs/ https://n2t.net/e/pub/ark.html#name-enhancements-and-related-spe | RM: the arks.org/specs/ endpoint is ok |
Action items
- Greg Janée will try to reword the statement about normalizing alternate forms of received hyphens
- John Kunze to establish specs stub page at endpoint
- John Kunze to add contrast to the two diagrams