Page History

...

Design Questions

Open Questions

• What approach should be taken to resolve referential integrity issues causing changes to LDPRms?  
  • https://wiki.duraspace.org/x/TAJsBQ#VersioningDelta/SpecificationNotes-ref-int
  • Also consider if referential integrity should be address across the repository rather than just for LDPRms
• Is it acceptable to only create versions for individual resources rather than trees?
  • https://wiki.duraspace.org/x/TAJsBQ#VersioningDelta/SpecificationNotes-version-single
• How should restoring previous versions of LDPRvs work?
  • https://github.com/fcrepo/fcrepo-specification/issues/217
• How to make an existing LDPR versionable?
  
  • PUT with an empty body may not be acceptable
• Should it be possible to include non-LDPRm children in LDPCvs?
• How can LDPCvs be identified?
  
  • https://github.com/fcrepo/fcrepo-specification/issues/233
• Do we need a separate memento ontology or can we use PROV-O for most things?  There are examples of what a memento and LDPCv might look like here: 
• For information about TimeMap and TimeGate can these resources not list them explicity and just use some known url formatting for this?  We may not need the pointers to the TimeGate  / TimeMap inside the resources.
  • Timegate is LDPRv URL
  • TimeMap is LDPRv URL + "/fcr:versions"  
  • The code that retrieves the memento can construct the "original", "timemap" and "timegate" link headers from it's own URL – is that okay to do?
  If the mementos have containment triples which point to other resource (either LDPRs or LDPRm's) how do we avoid an issue of the child being in two containers? 
  • LDPRm Creation Example
  • Discussed by a subgroup – decided that we need to research this more. 

Answered Questions:

• Fedora Modeshape implementation will cleanup inbound references upon deletion of an object.  How do we keep the mementos intact and immutable if something they reference disappears? 
  • Handling Deletion of Referenced Resources / Mementos

...