-
Notifications
You must be signed in to change notification settings - Fork 14
2019.02.20 Editors Meeting
Andrew Woods edited this page Feb 20, 2019
·
9 revisions
https://duraspace.zoom.us/my/fedora
- Andrew Woods (DuraSpace)*
Julian Morley (Stanford)- Rosy Metz (Emory)
- Simeon Warner (Cornell)
Andrew Hankinson (Bodleian Libraries)- Neil Jefferies (Bodleian Libraries)
(* indicates the notetaker)
- Issue #275. Using file paths and digest.
- Issue #304. Unix
ls
references - Issue #306. Do we agree on requirements for validity?
- Clarify issues #284 and #285
- All Beta Issues
- Review of our Use Cases to see what that we considered in-scope is and isn’t supported by the current draft.
- CNI
- Simeon, Rosy and Andrew will be in attendance
- Issues for Beta
- Questioning mixed use of file paths and digests #275
- Close as "won't fix"
- Simeon to open new issues
- New issue: adding example to impl-notes with different existing and logical paths
- New issue: mention importance of impl-notes
- Add note about zero padding not being recommended pr-309
- All on call agree with PR as it stands
- Andrew H? Julian?
-
ls
details seem out of scope
- All on call agree with PR as it stands
- Be explicit about version sequence requirements for OCFL Object validity #306
- All on call agree with tightening language around version names
- Julian, do you have a use case that is counter to this?
- Suggestion that even redacted versions need to keep a version directory
- Case sensitivity and OCFL #285
- OCFL expects case sensitive and case preserving operating systems
- UTF Encoding for OCFL #284
- Spec: Inventory, as JSON, is in UTF
- Spec: Requires any systems that maps unicode sequences to pathnames
- Clarify how to extend algorithm choices #292
- Neil to add text explaining that the spec provides a table as a registry of algorithms
- Questioning mixed use of file paths and digests #275
- OCFL implementations
- Use case review
- Need to tag "in-scope", but for future releases
- The following were flagged as "resolved". Once all editors provide +1 on them, the use cases can be closed
- https://github.com/OCFL/Use-Cases/issues/31
- https://github.com/OCFL/Use-Cases/issues/26
- https://github.com/OCFL/Use-Cases/issues/25
- https://github.com/OCFL/Use-Cases/issues/17
- https://github.com/OCFL/Use-Cases/issues/12
- https://github.com/OCFL/Use-Cases/issues/11
- https://github.com/OCFL/Use-Cases/issues/9
- https://github.com/OCFL/Use-Cases/issues/6
- https://github.com/OCFL/Use-Cases/issues/3
- Andrew W.: send email asking how they think OCFL might fit into this OAIS-IF, will cc everyone
- ...