Call-in Details

• 4pm BST / 11am EDT / 8am PDT
• https://lyrasis.zoom.us/my/vivo1
• or Telephone:
  • US: +1 669 900 6833 or +1 646 876 9923
  • Canada: +1 647 558 0588
  • Australia: +61 (0) 2 8015 2088
  • United Kingdom: +44 (0) 20 3695 0088
  • Meeting ID: 812 835 3771
  • International numbers available: https://zoom.us/u/MO73B

Attendees

1. Ben Cail
2. Andrew Hankinson
3. Neil Jeffries
4. Julian Morley
5. Joshua Westgard
6. David Wilcox
7. Peter Winckles
8. Andrew Woods

Agenda

1. Community updates (introductions, updates, implementations, plans, etc)
2. Editorial updates
   • Mostly polish and validator work
   • Commits since last community meeting
   • Open questions
     • Clarify issues with case insensitive digests resulting in repeated digestsissue-461
     • Logical paths MUST not have element . .. or //, but what about content paths?issue-462
   • Pending pull-requests
     • Conflicting logical pathsissue-453
     • Update table of validator codes to use id tags for RFC2119 termsissue-446
3. Review of previous action items
4. Releasing 1.0
   1. Requirements to release 1.0
      1. Status of fixture objects
      2. Status of validators
      3. Status of test suite - embedded in validators
   2. Open 1.0 Spec Issues
5. OCFL Extensions
   • Issues
   • Pull-requests
6. Next community meeting: June 10, 2020 (second Wednesday of the month)
   • Potentially rotate timing of the community call?

Notes

1. Community Updates:
   • David Wilcox will be doing a presentation on Fedora 6 at Virtual Samvera Connect, which will include OCFL
2. Editorial Group Updates:
   • Python validator is coming along
   • Stanford will be moving forward with a ruby validator as well
   • Validator work has helped to clarify certain issues around strictness (may/should/must, errors vs. warnings)
3. Open issues:
   • Regarding the case insensitivity of hashes, the consensus was that this should be a validation error
   • Content paths must also not contain the elements that are already forbidden in logical paths
   • Pull Requests:
     • PR on conflicting logical paths was approved
     • Andrew W. will look at updating the table of validator codes
4. Extensions:
   • The intent is for community members to be able to create extensions (this would be facilitated by a PR resolving issue #2 )
5. Releasing 1.0
   • Extensions themselves by definition should not be blockers to a 1.0 release
   • Having an extensibility mechanism/pattern in place, however, would be important for 1.0

Audio recording

• 2020-05-13.mp4

New Action Items

• Who: What

Previous Action Items

• Neil: Add language specific to extensions, specifically layouts and parameterization. ext-issue-2