2020.11.17 Editors Meeting

Call-in

See invite

(* indicates the notetaker)

Review previous action items
Administrative Items
1. Organize Use Cases repository, i.e. Sorting labels?
  - Agree to change "Proposed In-Scope V2" labels to be just "Proposed In-Scope" now
  - Rosy to write issue similar to https://github.com/OCFL/Use-Cases/issues/38 but focusing on Google
  - Need to engage community for higher level discussion of use cases. What other open source projects have a preservation sensibility that might benefit from OCFL? Which vendors might be interested?
  - Focus on this on December 15
Spec
1. Open PRs - none
2. Open Issues
  - character encoding issue #514. a number of related issues/PRs linked to this including extension/PR #16 and spec/issue #284 (closed)
    - Editors agree that inventory.json MUST be UTF-8. Therefore within the inventory.json the object id is always expressed in UTF-8. If an extension depends upon an operation the is affected by the encoding of the object id then the extension should clarify the expected encoding (likely UTF-8) -- this is outside of the core OCFL specification
Extensions
1. Open PRs
  - "Add 'Optional Extension Initializer'" - pull-36
    - MERGED
  - "add extensions specification version" - pull-39
    - Agreed that we don't think it is good to add "minimum", a clear path to merging this after the one remaining change is implemented
2. Open Issues
  - thoughts on OCFL over S3 - issue #522. What should we do with this? move to the use cases? - done (use-case-38)

Need to get more eyes on extensions by people with actual interest in topics, email to list again -- DONE, got input on range issue, since closed
Andrew W. to create a PR based on our conversation about how to initialize extensions -- DONE and merge