Decisions

Functional Decisions

Drop the Single Subject Restriction
Only enforce referential integrity on server generated triples
1. No automatic enforcement or cleanup of user supplied RDF
Add Archival Group interaction model

Drop support for import of historic mementos in OCFL
1. Allow or disallow in other backends?
1:1 mapping between Fedora info URIs and LDP paths
1. This means fedora 3 objects migrated to single OCFL objects would inherently have LDP path http://example.org/fcrepo/rest/${pid}

Refactor FedoraResource and its sub-classes to serve primarily as data encapsulation objects.
1. Refactor modification operations into separate service classes.

With the proposal of removing the SSR are we thinking that we will also support out of domain subjects?
OCFL
1. Will OCFL versions map directly to Fedora versions? Or will Fedora versions be tags of OCFL versions?
  1. Will past versions be able to be deleted?
2. How will unversioned changes be be persisted?
3. Where will changes within a transaction be stored prior to committing?
What representation should be used for resources on disk?
1. Some examples here https://gist.github.com/bbpennel/3dd2ec19d3545e0417071958177baa93
Automatically generated checksums
1. If the user does not supply any digests, should Fedora generate any automatically like it has done with sha1's in fcrepo4?
2. OCFL will generate a digest automatically for storage reasons (not necessarily always the same algorithm), should this be surfaced in Fedora?
3. Should the digests included in existing OCFL objects be surfaced in fedora?
Search service synchronous or asynchronous?
Canonicalization of RDF, checksumming metadata, and the possibility of byte-for-byte I/O of metata resources.
Converter framework: should it stay or should it go?
Should we evaluate a "Minimal" Fedora 3 migration, where all datastreams from a fcrepo3 object are placed into a single OCFL object with no modifications?