Date
Attendees
Goals
scope subgroups for IIIF and Persistence statements
Discussion items
Item | Who | Notes |
---|---|---|
Announcements | ||
Calls for papers, submission deadlines, upcoming meetings: Calendar of events | dw: NASA proposal with rolling deadline (due 2023-03-29): NNH22ZDA001N-HPOSS (https://nspires.nasaprs.com/external/solicitations/summary.do?solId=%7bB364DBB8-390B-744D-013F-8F4C304B9A63%7d&path=&method=init). "proposals that would advance and streamline the open sharing of scientific information...supports the development of innovative open-source tools, software, frameworks, data formats, and libraries that will have a significant impact to the...science community". "expected to support...3-5 projects for the call. The awards will be for a duration of one year and a typical size of ~$100,000 per award." | |
Any news items we should blog about?
| ||
What should be the scope of the ARKA Persistence Statements subgroup?
| 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?
|