2020.03.11 Community Meeting - OCFL/spec GitHub Wiki

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

Agenda

  1. Community updates (introductions, updates, implementations, plans, etc)
  2. Editorial updates
    1. Consistency of version blocks in most recent version of the inventory with all previous inventories (issue-421 & suggested resolution:issue-430)
    2. Updating 'date format' used in the specification (issue-419)
    3. Coordinating between validator and normative MUSTs/SHOULDs (issue-384)
  3. OCFL client and validator - Demo by @julianmorley
  4. Review of previous action items
  5. Releasing 1.0
    1. Requirements to release 1.0
    2. Status of validators
    3. Open 1.0 Spec Issues
  6. Next community meeting: April 8, 2020 (second Wednesday of the month)

Notes

Review of changes to spec & issues:

  • No objections raised about the scope of the inventory changes for #421, etc.
  • RFC 3339 sounds OK, no objections
  • Neil has created draft pull-request related to extension definitions

Michael making strides with OCFL implementation, including Express

Julian's demo:

  • Ruby gem
  • Super simple entrypoint into an OCFL object library
  • Needs to be linked a bit more to the spec.
  • May need further work on classifying the validator messages (ERROR, INFO, OK, maybe Debug?)
  • Provides an indication of some of the optional features that are in use for an object.

Lots of documentation about Julian's OCFL Tools:

Peter W:

  • 423 -- good to go for the spec, other issues about problematic characters for implementation notes
  • May need to capture additional issues about this for improving impl. notes.

Getting close to 1.0! Stay healthy. Don't touch your face. Next meeting April 8.

Audio recording

  • [2020-03-11.mp4]

New Action Items

  • Who: What

Previous Action Items

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