[
https://issues.apache.org/jira/browse/JENA-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14321155#comment-14321155
]
Bruno P. Kinoshita commented on JENA-632:
-----------------------------------------
>I have seen attempt to produce more complex JSON from RDF. They have their
>place but so does a direct, simple, efficient format.
>One row, one JSON object. Streamed if the underlying query execution streams.
Good point! Thanks Andy!
> To produce that title array, the code would need to see the whole result set
> (very special case - know there is only repeated "title", and only one
> "author" – just expressing that is complicated enough. If the condition is
> broken mid result set, we end up with the "HTTP 200" already sent problem).
I was preparing to try some ways to aggregate the titles into a single array,
and look for ways of doing that. But very happy I asked here before. Let's do
the simpler way, introduce the new JSON statement, write tests, docs, and then
see if we need other more complex methods.
Thanks a lot Andy! Going to use some spare time in this Carnival to work on
this issue :D
Bruno
> Generate JSON from SPARQL directly.
> -----------------------------------
>
> Key: JENA-632
> URL: https://issues.apache.org/jira/browse/JENA-632
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ, Fuseki
> Reporter: Andy Seaborne
> Priority: Minor
> Labels: java, javacc
>
> The capability to generate JSON directly from a SPARQL (or extended SPARQL)
> query would enable the creation of JSON data API over published linked data.
> This project would cover:
> # Design and publication of a design.
> # Refinement of design based on community feed
> # Implementation, including testing.
> # Refinement of implementation based on community feed
> Skills required: Java, some parser work, design and discussion with the user
> community, basic understanding of HTTP and content negotiation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
