...
- Announcements
- See if we can get a unified vision for how we want Fedora to interact with OCFL, so that we can propose one of the following to the leadership group:
- Recommend pushing for changes to the OCFL spec (i.e. a mutable head), so that both versioned and un-versioned content can be "in" OCFL
- Accept the immutability of object versions in OCFL, and recommend one of the following
- Fedora shall store un-versioned content outside of OCFL in a fedora-specific layout
- Fedora shall disallow un-versioned content entirely
- Recommend Fedora use something other than OCFL for Fedora's persistence layer, and create external tools for exporting/publishing to OCFL when desired.
- This document describes the core issues and outlines the pros and cons of the implementation possibilities described in the preceding agenda item. Recommending a particular implementation is beyond the scope of the document; it simply seeks to provide an objective (to the degree possible) analysis to serve as a baseline for an informed discussion. Comments and suggestions are welcome, but please respect the scope of the document.
- Other questions to be answered
- > “When making a request during a transaction, should the ACL of the HEAD version of the resource be evaluated, or the ACL of the version of the resource that exists in the transaction?”
- What is the approach we want to take for adding digests to external binaries?
- Reference: 2019-09-26 - Fedora Tech Meeting (Notes: 3.a.)
- What do we want our approach to be for loading Fedora6 resources? lazy or eager?
- Related to https://github.com/fcrepo4/fcrepo4/pull/1557
- <add topics here>
...