Date
Attendees
- Karen Hanson, Donny Winston, Greg Janee, Dave Vieglais, Tom Creighton, Roxana Maurer, John Kunze
Goals
scope subgroups for IIIF and Persistence statements
...
Item | Who | Notes |
---|---|---|
Announcements | jk: everyone please have a look at the end of year wrapup blog post before it goes out later today | |
Calls for papers, submission deadlines, upcoming meetings: Calendar of events | CNI pre-recorded briefing on ARKs accepted, speakers jk, dv, and Tim Clark | |
Any news items we should blog about?
| Should we point to presentations by Bertrand's and Donny's talks | |
What should be the scope of the ARKA Persistence Statements subgroup?
| Do p. statements apply to the object only, or to the organization, or to a record of the past (even if the digital artifacts change)? From last time, Roxana's implementation: persistence: { // Persistence statements: https://datascience.codata.org/articles/10.5334/dsj-2017-039/ contentVariance: { // how an object’s content will change over time type: String, enum: [ "frozen", // The bit stream representing previously recorded content will not change. "keeping", // Previously recorded content will not change, but character, compression, and markup encodings may change during a format migration, and high-priority security concerns will be acted upon (e.g., software virus decontamination, security patching). "fixing", // Previously recorded content may be corrected at any time, in addition to any change under “keeping”. "rising", // Previously recorded content may be improved at any time, for example, with better metadata (datasets), new features (software), or new insights (pre- and post-prints). This encompasses any change under “fixing”. "molting", // Previously recorded content may be entirely overwritten at any time with content that preserves thematic continuity (homepages). "waxing" // Change that is limited to appending content in a way that does not in itself disrupt or displace previously recorded content. Examples of waxing objects include live sensor-based data feeds, citation databases, and serial publications. ] }, objectAvailability: { // the period of time during which the provider expects to keep the object available type: String, enum: [ "finite", // Availability is expected to end on or around a given date (e.g., limited support for software versions not marked “long term stable”) or trigger event (e.g., single-use link). "indefinite", // The provider has no particular commitment to the object. "lifetime", // The object is expected to be available as long as the provider exists. "subinfinite" // Due to succession arrangements, the object is expected to be available beyond the provider organization’s lifetime. ] }, nonReassignment: { // (NR) Once assigned and made public, the identifier will not be reassigned. type: Boolean BnL example: https://persist.lu/ark:70795/m4bk6v?info returns { | |
What should be the scope of the ARKA IIIF subgroup?
| Right now we're looking at best practices for those considering using ARKs and IIIF dw: https://gallica.bnf.fr/iiif/ark:/12148/btv1b8449691v/f29/2131,4016,1467,948/full/0/default.jpg |