Github user afs commented on the issue:
https://github.com/apache/jena/pull/114
The JSON ecosystem moves fast! GraphQL is now significant and how that
might be used is also very interesting. There are different ways to use GraphQL
and maybe it is not the solution to all needs anyway - this ticket is more
about result sets in easy-to-consume JSON than other work in the GraphQL-RDF
area and more about JSON services.
To move this ticket forward, how about putting the feature in with a big
label saying "Experimental - subject to change" and _really_ mean it? By
getting it out, it generates feedback, requirements and insight.
You can ask for result sets in JSON but the JSON
(http://www.w3.org/TR/sparql11-results-json/) or JSON-LD graphs but that isn't
what general data consumers would consider to be "easy-to-consume".
Is the RDF literal to JSON aligned with:
[RDF-JS
mapping](http://jena.staging.apache.org/documentation/query/javascript-functions.html#arguments-and-function-results)?
(which only came along recently).
---
