2019.03.20 Editors Meeting

Call-in

(* indicates the notetaker)

Use Cases - We went through the below use cases and closed. Reviewed remaining use cases:
1. Object stores: Use Case #2 - we should create an issue indicating that we don't support empty directories because object stores don't support empty directories. #322 created. Discussion about if there is more we can do to the spec because we talk a lot about hierarchy and directory (around 74 references to that), but object stores don't support those. Add directory as a term to the spec saying that the common implementation utilizes directory structure, but when we refer to this, we mean hierarchical organization. #323
Open Issues
1. #306 - We agreed that we would go with @zimeon 's original recommendations (from Feb 15.), sequential starting with v1 and incrementing up. In the next version of the spec will handle distributed versions.
2. #313 - Start with spec then move to implementation notes.
3. #212, #284, and #285 - Waiting on PR #317 to be updated.
4. #320 - Discussion of how Moab handles this; creates a deposit directory where the work happens and then a move happens where the final version moves into the object and then the inventory is updated. There may be other approaches as well. Let's create a section of the implementation notes that discusses how to accession content into an OCFL object. We agreed to create the deposit directory at the storage root level.

Andrew W.: send email asking how they think OCFL might fit into this OAIS-IF, will cc everyone