Improve and simplify fcr:versions response triples to have links only. #347
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://www.pivotaltracker.com/story/show/70475058
There are two cases of using the fcr:version response triples, one is the html output that need a full version of the RDF triples, another is the RDF response that need improve. As we discussed during the standup meeting this morning, I've separated the html response to have its own rest api method, and filtered the fcr:version triples for the RDF response to contain only the links to the versions as the default output. However, we can still retrieve the full RDF triples for frc:version with parameter recursive=true provided, like "curl -H "Accept: text/turtle" http://localhost:8080/rest/path/to/resource/fcr:versions?recursive=true".