-
Notifications
You must be signed in to change notification settings - Fork 14
2018.10.10 Community Meeting
Andrew Woods edited this page Oct 11, 2018
·
9 revisions
- 11am ET
- https://duraspace.zoom.us/j/8128353771
- 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
- Andrew Hankinson
- Simeon Warner
- Don Brower
- Ben Cail
- Julian Morley
- Andrew Woods
- Community updates / points of discussion?
- Changing JSON-LD to JSON in OCFL: Reasons & community feedback, see https://github.com/OCFL/spec/issues/41
- Review Alpha ...and Implementation Notes
- October community call we will release (OCFL Editors and PASIG Discuss)
- Review feedback in the November community call
- Review open issues
- Alpha published now
- Take community input at November community meeting, then publish Beta
- Incorporate input, meet other criteria
- Release 1.0
- Specification has moved from json-ld to json
- Driver: creating a json-ld context was not possible based on our inventory format
- Changing the inventory was possible, but more complex
- Is the value of having json-ld more important than simplicity?
- Simplicity is prioritized
- Reviewed each section:
- Terminology
- OCFL Object
- OCFL Storage Root
- Examples
- Questions / Discussion around the following topics:
- Is there support for slashes in file names
- Is there a specified order to versions
- Should the inventory schema reside in the Storage Root
- Which other applications may be appropriate to engage with
- Archivematica?
- IIIF?
- Clarify that an empty object MUST have at least a v1 folder"
- Clarify the ordering or non-ordering of versions
- Logical file paths - directory separators
- Minor wording simplification
- Section 3.5.2 "Manifest" to reference existing file paths
- Section 3.5.4 "Fixity" to clarify existing file paths
- Add inventory schema to Storage Root?