-
Notifications
You must be signed in to change notification settings - Fork 14
2019.12.03 Editors Meeting
Rosalyn Metz edited this page Dec 3, 2019
·
8 revisions
https://lyrasis.zoom.us/my/vivo1
- Julian Morley (Stanford)
- Rosy Metz (Emory) *
- Simeon Warner (Cornell)
- Andrew Hankinson (Bodleian Libraries)
Absent
- Andrew Woods (Lyrasis)
- Neil Jefferies (Bodleian Libraries)
(* indicates the notetaker)
- Open 1.0 Spec Issues
- Previous Actions
- #404 WIP Extensions - AH still working on this. Concerns that extension creators might not follow the spirit of OCFL.
-
#407 Characters allowed in paths - Ticket submitted by @pwinckles
- In section 3.3 paragraph 5, 7, and 8 should become section 3.3.1 Content Directory. (Rosalyn PULL REQUEST)
- Add section 3.3.2 around file names and what you should be thinking about with regard to names for the content path; clearly say that file name restrictions don't apply to the logical path. (CREATE NEW ISSUE - Rosalyn; reference BagIt spec in the issue)
- In section 3.5 remove
and logical paths
andand state blocks
that appears in the second paragraph; add a third paragraph referring to section 3.3.2 basically asking users to follow those restriction. (Simeon PULL REQUEST) - We need further discussion on how these restrictions impact the logical path. (CREATE NEW ISSUE - Andrew H.)
- @julianmorley will be publishing the OCFL tools gem in the next couple of days.
- Fedora 6 sprint 2 demo shows real live OCFL in action.
- Simeon: create pull request for section 3.5 changes
- Rosalyn: create pull request for section 3.3 changes
- Rosalyn: create new issue for addition of section 3.3.2
- Andrew H: create new issue for discussion of how restrictions of allowable characters in content path might impact logical paths
- Julian: consider what a guidance document of the OCFL stack (on the wiki) would look like
- Neil: Specifying support for "extension" keys... with query-parameters