Versions Compared

Old Version 2

changes.mady.by.user Danny Bernstein

Saved on

compared with

New Version 3

changes.mady.by.user Ben Pennell

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Decisions

Functional Decisions

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

Nearly Decided

  1. Drop support for import of historic mementos in OCFL
    1. Allow or disallow in other backends?

Design Decisions

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

Open Questions

  1. With the proposal of removing the SSR are we thinking that we will also support out of domain subjects?
  2. Remove ContainerService?
  3. 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?
  4. What representation should be used for resources on disk?
    1. Some examples here https://gist.github.com/bbpennel/3dd2ec19d3545e0417071958177baa93
  5. Will Fedora internally track resources by an assigned identifier, or by LDP path?Referential integrity:  yes enforced at the server managed and containment levels.  No for everything user managed.