All aspects of versioning seem to work in reasonable ways, except the viewing of old versions. Because the old versions are represented differently in JCR, maintaining translations for the RDF (both those that come from properties and those implicit in our resources) is a burden that hasn't been met and is fraught with likely oddities.
In order to ship a product for which future versions are likely to be backwards compatible, it may be prudent to severely limit or eliminate the view of historic versions. The following is a conservative proposal:
- simplify but improve response to GET "path/to/resource/fcr:versions" to just list
- each version canonical URI (which should be in the label)
- each version creation date (currently not displayed)
- eliminate viewing old versions (GET "path/to/resource/fcr:versions/version-label")*
- retain deleting old versions (DELETE "path/to/resource/fcr:versions/version-label")
- retain restoring old versions (PATCH "path/to/resource/fcr:versions/version-label")
- disallow label reuse (return a conflict)
*If we wanted to retain some semblance of views of historic versions the following limitations may need to apply:
- Exclude links to children and parents
- Exclude serialization-related triples
- Disallow viewing historic versions of resources that have been deleted
- Maybe more...
