...

• Resource versions could now be managed individually, rather than creating unwanted trees, when the goal is only to version a single resource's metadata.
• Creating a snapshot of an entire tree would need to be triggered with many individual API requests.
• Retrieving or restoring a tree of resources to a particular point in time would require individual API requests with datetime negotiation.
• Creation and management of versions would shift from being a Modeshape-provided feature to the Fedora code base.

Draft Tickets

Add versioning response headers to LDPRv HEAD/GET responses - 

The following headers should be added to responses to HEAD and GET requests to LDPRv's only when the resource is versioned (has the http://fedora.info/definitions/fcrepo#VersionedResource type):

...

• Currently the modeshape fedora will request a "Slug" header be supplied to use as the label of the version. This should be taken out, to be replaced by the Memento-Datetime header, if that's present.  The label should be a timestamp per the Memento DateTime Section of the Memento spec 

Create an LDPCv

Implement the creation of a LDPCv.  

• 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

...