September 5-7, 2018, Oxford, UK

Present:

• Andrew Hankinson (Bodleian Libraries)
• Simeon Warner (Cornell)
• Julian Morley (Stanford)
• Neil Jefferies (Bodleian Libraries)
• Rosalyn Metz (Emory)
• Andrew Woods (DuraSpace)

Agenda

September 5

• Review Use cases, in particular decide which proposed use cases are in or out of scope. Rewrite or assign rewritings for clarification. Create new issues as appropriate. (timebox 2h?)
• Review and prioritize Issues, plan work for rest of day (timebox 1h?)
• Work on issues, review text and merge in real time

September 6

• Re-review and re-prioritize Issues, plan work for the day (brief)
• Perhaps start by tackling a tough one: renaming
• More on issues, review text and merge in real time

September 7

• Re-review and re-prioritize Issues, plan work for the day (brief)
• More on issues, review text and merge in real time
• Plan future work
• Discuss implementation
• Plan communication and feedback strategy

Desired outcomes

• Draft of OCFL specification with text for all sections (possibly excluding examples and implementation considerations)
• Greater clarity on OCFL scope as defined by use cases that are determined in or out of scope

Notes

Friday afternoon

• Work on specs until 3:30pm
• Discuss versioning the spec
  • Decision: x.y
  • First version is 0.1
    • http://ocfl.io/0.1/spec/
    • http://ocfl.io/0.1/implementation-notes/
    • http://ocfl.io/0.1/context.jsonld
  • Working version would be useful
    • http://ocfl.io/draft/spec/
    • http://ocfl.io/draft/implementation-notes/
    • http://ocfl.io/draft/context.jsonld
  • We will edit the files in the draft directory and merge into master branch
• Roadmap
  • Alpha
    • October community call we will release (OCFL Editors and PASIG Discuss)
    • Review feedback in the November community call
    • Then determine release date based on the amount of feedback
  • Beta
    • A spec we are happy with
    • Experimental validation tool
    • Determine who else to push this out to
  • Release 1.0
    • One production ready validator
    • Test suite and fixture objects
    • Two institutions committed to backing the initiative (should define that)
• Community Call Agenda
  • Review Roadmap (Simeon)
  • Review F2F meeting outcomes and walkthrough of the specification (Andrew H.)
  • Review upcoming meetings/presentation proposals (Rosy)
• Editorial Agenda
  • Review Open Pull Requests
  • Review Issues with label Question
• Action Items
  • Andrew: add a roadmap page to the wiki
  • Rosy: create proposal for CNI (plus Julian and Andrew W.)
  • Neil: copy Rosy's proposal for JISC
  • Neil: lightning talk at PASIG
  • Simeon: propose workshop for OR2019
  • Simeon: will move the current data into a draft directory and create a new index.html page.
  • Julian: put in nomination for digital preservation awards
  • Rosy: identify a journal to publish a paper about the spec

Next Steps

These are pull requests that we indicated during F2F that we needed to go back and review.

• Review implementation notes
• Review section 3 pull request
• Review section 4 pull request