...
See Pattern 1.2 in https://tools.ietf.org/html/rfc7089#page-18 for details.
Support Datetime negiotation for
...
LDPRvs
Implement support for datetime negotiation for the retrieval of previous versions of a resource as follows:
- GET requests to LDPRv URIs must support the 'Accept-Datetime' header
- It must follow the syntax outlined in https://tools.ietf.org/html/rfc7089#section-2.1.1
- The response must contain headers as outlined in ticket <LDPRm GET response>
- When a datetime is provided, Fedora will respond with the LDPRm chronologically nearest to the given header as follows:
- Returns nearest LDPRm with Memento-Datetime <= provided Accept-Datetime
- Otherwise, it responds with a 404 not found response.
- See: Datetime negotiation example
Add versioning headers for LDPRm HEAD/GET responses
...
- The LDPCv must not be a child of the LDPRv
- It must be a LDPC ( https://fcrepo.github.io/fcrepo-specification/#LDPC )
- It must contain a relationship to its LDPRv (what would this be? a property?)
Delete
...
a LDPCv
See: https://fcrepo.github.io/fcrepo-specification/#ldpcvdelete
- Deletes the LDPCv, which has the affect of also deleting all of the LDPRm's contained by it.
- The versioning interaction model is removed from the LDPRv (http://fedora.info/definitions/fcrepo#VersionedResource).
Delete
...
a LDPRv
(this one might not actually be a ticket, since the behavior, though not totally correct, is in line with what we're targeting.)
...
- This response type is NOT required to include all statements in the LDPCv's graph, only those that are required by the link-format, outlined https://tools.ietf.org/html/rfc7089#page-36
- Including: URI of LDPRv for this timemap, all LDPRms in this LDPCv with their memento date times, timegate link, link to the LDPCv
...
GET on LDPCv must return interaction model
...