...
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?
- How should restoring previous versions of LDPRvs work?
- 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?
- Do we need a separate memento ontology? How have people represented Memento information in RDF?
- What does the internal representation of mementos look like?
- Are mementos stored internally as separate resources LDP-RS contained by LDPCv (TimeMap resource) or could/should they be serialized versions stored as LDP-NRs? What other options would work to internally represent the mementos?
- Is it okay to store information in the LDPRm indicating it's archival time (and strip that out when delivering to user)?
- What does the internal representation of mementos look like?
- 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?
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?
...