...
Item | Who | Notes |
---|---|---|
Announcements | m: texas conference on digital libraries, with emphasis on pids, arks, what choices, use cases | |
Calls for papers, submission deadlines, upcoming meetings: Calendar of events | m: I will add link in calendar entry on texas conf | |
Any news items we should blog about? | ||
ARK spec transition plan; what can we learn from the Outreach discussion? Below are notes from the last Outreach WG meeting. We've blogged about the upcoming change in the recommended form of newly published ARKs (starting on STARTDATE) – from ark:/12345 (oldform) to ark:12345 (newform)
Discussion notes on the above strawman (rf=Ricc Ferrante, mg=Maria Gould, jk=John Kunze): rf: confused about CUTOVERDATES; does this mean we have to start normalizing to newform ARKs? do we leave old ARKs in oldform in our system? | J Introduced strawman and discussion from the previous Outreach WG meeting. Some questions: Are there non-backward compatible changes? no j: is a focus group the right thing? if so, do we want formal or informal? | |
Some ARK spec publication options
| g: would w3c standard require setting up a wg? j: dunno, could be expensive in terms of efforts g: what about going with iso/niso -- could this be feasible? g: what about ECMA (eg, json.org?) m: what about IIIF.io? |
Greg’s concise version of the ARK spec transition scope:
The standardized format of an ARK is ark:12345. A legacy format for ARK identifiers, in which a slash occurs after the colon as in ark:/12345, is deprecated. Because of the permanence guarantees of ARKs, such legacy ARKs must continue to be supported. Services that consume ARKs from external sources should anticipate encountering ARKs in both standardized and legacy formats, and accept them equally. Services that produce ARKs should produce them in standardized format only.
Action items
- Karen Hanson will start a use case googledoc
- All: will add use cases to it