2020.11.03 Editors Meeting

Call-in

See invite

Attendees

• Neil Jefferies (Bodleian Libraries)
• Julian Morley (Stanford)
• Rosy Metz (Emory)*
• Simeon Warner (Cornell)
• Andrew Woods (Lyrasis)

(* indicates the notetaker)

Agenda & Notes

1. Review previous action items
2. Administrative Items
   1. US NIST Multibag work, see https://github.com/usnistgov/multibag-py/blob/master/docs/multibag-profile-spec.md and http://www.aspbooks.org/a/volumes/article_details/?paper_id=39243 (Simeon)
      • might be useful for us to read through this before we start work on OCFL 2.0
   2. OCFL T-shirt! (Rosalyn)
      • Fedora marketing group thought of this. Put it up on RedBubble, let Patrick know.
   3. DPC Awards on Thursday (Rosalyn)
      • see: https://www.dpconline.org/events/digital-preservation-awards
3. Spec
   1. Open PRs
   2. Open Issues
4. Extensions
   1. Open PRs
      1. "update extension spec spec" - pull-32
         • Discussion about making the constraints section loose so that things can grow how they grow rather than be artificially tight. So the current example may be the concern on line 42. Instead better language might be: Constraints may be in plain text, regex, JSON Schema, or whatever makes the most sense for the extension.
      2. "add section about implementing extensions" - pull-31
         • is it possible to have our cake and eat it too -- can we allow for fully prescribed extensions and those that might be less prescriptive. the extensions are an open door to add more functionality. it could be an extension is written that does something like what #31 is prescribing.
         • for this PR we suggest removing the manifest block and merging the rest of the PR.
      3. "Update merge policy to indicate use of next available number" - pull-35
         • Julian merged
   2. Open Issues
      1. "Add mechanism for defining which extensions apply at the object level" - issue-33
         • Related to pull-31 so was discussed above
      2. "extension manifest"- issue-34
         • Related to pull-31 so was discussed above

Action Items

Previous Action Items

• Editors to create new Issue for extensions using language from PR #31 --> Issue #33
• Need to get more eyes on extensions by people with actual interest in topics, email to list again
• Rosalyn to update merge policy language in extension #26