2019.04.03 Editors Meeting

Call-in

(* indicates the notetaker)

CNI presentation
Open Issues
1. Issue #313 - Change terminology
2. Clarify issues #284 and #285 - Resolutions documented. Neil to provide PRs
3. Issue #212 - its been addressed via PR #317.
  - Need approval on comment
All Beta Issues

CNI Presentation
- Suggestion: remove slides 22-24
  - Talk to slide 21 instead ("But wait, there's more...")
- "Sufficient Preservation Practices?" slide, examples:
  - Our regular backups are sufficient
  - My filesystem handles fixity checking
  - We perform nightly MySQL dumps
  - I have multiple copies
  - I have diverse (technology and geography) storage systems
Open Issues
- @rosy1280 to work #313 today
- #212 waiting on +1 from Neil
- #317, @awoods to review, add commit as appropriate
Beta issues
- Only 8 remaining
- Clarify how to extend algorithm choices
  - Potentially move table to an addendum document
  - ..but should not remove rows from the table
  - Updates to the digest table would impact client tooling, warranting a point release of the spec
  - Those present recommend keeping the table in the spec
Beta reference impl
- Provide example of an OCFL-compliant stack
  - For example, including NFS with options
- Potentially start off as a Git wiki page
- Interest in having "validation of an OCFL stack"
  - Not exactly clear on how this would be implemented
- Elements of the stack
  - Environment setup
  - UTF-8, case-sensitivity, filesystem delimiters
  - Storage systems?
  - Object store variants?
- Minimally, a guidance document (wiki page) would be a step forward

Andrew W.: send email asking how they think OCFL might fit into this OAIS-IF, will cc everyone