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. Andrew Woods
2. Steve Liu
3. Julian Morley
4. David Wilcox
5. Ben Cail
6. Andrew Hankinson
7. Michael Lynch
8. Peter Winckles

Agenda

1. Community updates (introductions, updates, implementations, plans, etc)
2. Editorial updates
   • Validation codes
   • Linking codes into the spec
     • Such as #E007 or #W012
   • Example of migrating to new digest algorithm
   • Forbidding trailing slash on logical paths
3. Demo by Michael Lynch
4. Review of previous action items
5. 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
6. Next community meeting: May 13, 2020 (second Wednesday of the month)

Notes

1. Editorial updates
   • Validation codes map MUST requirements to "errors"; SHOULD requirements to "warnings"; and nothing for MAY requirements
   • Links in agenda to details of other recent editorial work
2. Demo by Michael Lynch
   • nginx extension (now express)
     • resolves URLs to OCFL files
   • Shows 'head' of repo
   • Using RO-crate
   • Some next steps
     • Immutable archive of research projects
     • Authorization-protected access to datasets
   • Another project has taking the UTS code, and extended it
   • Documentation will be updated
   • Questions
     • Content stored on local disk
     • Interest in porting to AWS-S3
     • Potential concern about OCFL objects with many (10s, 100s of thousands) files
     • Current expectations/requirements of the UTS project
       • Docker
       • OCFL
       • RO-crate
   • Can you (Michael) share the slide/image?

Audio recording

• 2020-04-08.mp4

New Action Items

• Who: What

Previous Action Items

• Neil: Add language specific to extensions, specifically layouts and parameterization. ext-issue-2
• Who??: Add language to spec to warn users about problematic characters/sequences - issue-407