2020.05.19 Editors Meeting

Call-in

See invite

Attendees

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

(* indicates the notetaker)

Agenda

1. Possibility of rotating timing of community calls?
2. Fixture PRs
3. Open Spec Pull Requests
4. Open 1.0 Spec Issues
5. Open Extension Pull Requests
6. Open Extensions Issues
7. Releasing 1.0
   1. Status of validators
   2. Status of fixture objects
   3. Status of test suite
   4. Two institutions backing the project

Notes

1. Working session on assessing pull-requests and open issues
   1. Extensions: All editors to review following pull-requests by this Thursday
      • Parameterised extensions definition (splits out README.md) (extensions-pr-08)
      • Update 0000-example-extension.md with parameters (extensions-pr-09)
   2. Specification
      • Closed with merge "Clarify issues with case insensitive digests resulting in repeated digests" (spec-issue-461)
      • Closed with merge "Conflicting logical paths" (spec-issue-453)
      • Closed with merge "Invalid link in section 4.1" (spec-issue-466)
      • Agreed on resolution for "Logical paths MUST not have element . .. or //, but what about content paths?" (spec-issue-462)
      • New issue "Why does the Storage Root extensions section talk about what files are allowed in the root itself?" (spec-issue-470)
      • Issue addressed with pull request, "Update table of validator codes to use id tags for RFC2119 terms" (spec-issue-446)
2. Community calls
   • Decision to seek input from community on interest in rotating timing of monthly community call
   • Email poll to ocfl-community to come
3. Discussion of ocfl_layout.json
   • The file is optional
   • If the file is present, it must reference an extension that describes the storage layout
   • If the file is not present, the storage layout is undefined
   • In either case, the two rules governing the storage layout still must be true
     1. There must be no nested OCFL objects
     2. There must be no files in the storage hierarchy that are not contained within an OCFL object

Action Items

• All editors to review by Thursday, May 21: "Parameterised extensions definition (splits out README.md)" (extensions-pr-08)
• All editors to review by Thursday, May 21: "Update 0000-example-extension.md with parameters" (extensions-pr-09)

Previous Action Items

• Julian to retool for updated error codes
• Julian to align and link validation-codes.md with anchors in spec