2020.02.18 Editors Meeting

Call-in

https://lyrasis.zoom.us/my/vivo1

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 and Notes

1. 2020-02-12 community meeting
   1. Next community meeting demo?
      • Julian's OCFL client / validator?
      • Mike Lynch's OCFL client?
2. PASIG Meeting
   1. Who is attending (Rosalyn, Neil, Andrew Woods)?
   2. Should we hold an editors meeting there?
   3. What do we need to provide PASIG for the presentation (presenter names)?
3. Open 1.0 Spec Issues and Open Pull Requests
   1. Specifying Extensions
      • Issue #403
      • Seeking input on details
   2. Path issues (issue-407, issue-411, issue-413)
   3. Metadata consistency between version inventories (issue-421)
4. Releasing 1.0
   1. Status of validators
   2. Status of fixture objects
   3. Status of test suite

Notes

1. Community meeting
   • Need to describe logical paths
     • Add new text under 'state' section
     • ACTION: Andrew H to create issue and PR
     • Candidate text:

     The logical path represents the file's location within the object state for a particular version. This will often be interpreted as a file path and the following restrictions provide for path safety in this common case. The logical path can be interpreted as a set of path elements joined by a '/' path separator. The path elements '.', '..', or empty path elements MUST NOT be included.

   • Sort out agenda for next month's community call
2. PASIG
   • Julian will likely be going (as well as, Rosy, Neil and Andrew W)
   • There will be no Editors meeting
     • However, target releasing 1.0 at least a week before
   • Organize details of OCFL presentation with David Minor
3. Open issues
   1. Extensions
      • No current need to mention/support extension directory parameters
      • Offer a SHOULD for how parameters can be supported for referenced extensions
      • Should we consolidate two extension approaches?
        • First write sub-dir text...
   2. Path issues
      • issue-411: PR has been created
        • Suggestion: Change to restrictions on "path elements"
        • Noting concern about limiting 'logical paths' to file system semantics
   3. Metadata consistency between version inventories
      • SHOULD is acceptable