...
- Do we need a separate memento ontology or can we use PROV-O for most things?
- 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?
- 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?
- 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?
- Should Fedora Modeshape allow snapshot (tree) versioning? What modeshape currently does in that scenario does not create actual mementos for ldp:contained resources.
- Should the mementos that have ldp containment triples reference the current resource in those triples or a memento of those resources? Some of it depends on how the memento was created (as a tree or solo resource).
- i.e., should </a/fcr:versions/vnum> ldp:contains </a/b> or ldp:contains </a/b/fcr:versions/vnum>
- When versioning a tree of resources, what happens if one of the resources in the tree does not have the version interaction model attached to it?
...
Use Cases
Versioning/Authorization Use-Cases
...