2019.10.29 Editors Meeting - OCFL/spec GitHub Wiki

Call-in

(* indicates the notetaker)

MAY have 'extensions' dir
- Agreed
- Interest in a shorter version (e.g. 'ext'), but... no
What should we specify related to what goes into the 'extensions' dir within the Object Root?
- Notion of "namespaces" related to extensions
- These namespaces would be sub-directory names within the 'extensions' directory
- Language: Extensions should have their own sub-directory in 'extensions' which MUST correspond to the namespace defined in the extension specification
- Should we require a namaste file for extensions in Object root?
What should we specify related to what goes into the Storage Root?
- Plain-text version of extension in Storage Root
- This would be a copy/paste of the extension .md file in GitHub
- Need to provide naming convention: extension-mutable-head-1.0.txt
- Use a JSON document?
  - Configuration/JSON? file may exist in storage root for use by extension-specific validators
Extension specifications should be versioned and tied to given OCFL versions
- Extensions MUST NOT modify any part of the OCFL Object outside of the 'extensions' dir
Note, not all Objects will be using the extension... even if the extension is defined at the Storage Root
ACTION: A.Woods to create a ticket to update the spec to support the notion of 'extensions'
- Language found in the spec related to the "log dir" may be a useful starting point
- https://github.com/OCFL/spec/issues/403

Julian: consider what a guidance document of the OCFL stack (on the wiki) would look like
Neil to check where not section links do not work issue#397
Neil to remove the 'deposit' directory statements issue#396
Andrew W to find time for all editors to discuss the mutable head issue
Neil to create issue for discussion of ocfl_layout.json options with respect to keys and optional parameters