You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 7
Next »
Decisions
Functional Decisions
- Drop the Single Subject Restriction
- Only enforce referential integrity on server generated triples
- No automatic enforcement or cleanup of user supplied RDF
- Add Archival Group interaction model
- Fedora will use
Nearly Decided
- Drop support for import of historic mementos in OCFL
- Allow or disallow in other backends?
Design Decisions
- Refactor FedoraResource and its sub-classes to serve primarily as data encapsulation objects.
- Refactor modification operations into separate service classes.
Open Questions
- With the proposal of removing the SSR are we thinking that we will also ?
- OCFL
- Will OCFL versions map directly to Fedora versions? Or will Fedora versions be tags of OCFL versions?
- Will past versions be able to be deleted?
- How will unversioned changes be be persisted?
- Where will changes within a transaction be stored prior to committing?
- What representation should be used for resources on disk?
- Some examples here https://gist.github.com/bbpennel/3dd2ec19d3545e0417071958177baa93
- Will Fedora internally track resources by an assigned identifier, or by LDP path?
- Automatically generated checksums
- If the user does not supply any digests, should Fedora generate any automatically like it has done with sha1's in fcrepo4?
- OCFL will generate a digest automatically for storage reasons (not necessarily always the same algorithm), should this be surfaced in Fedora?
- Should the digests included in existing OCFL objects be surfaced in fedora?
- Search service 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?