[
https://issues.apache.org/jira/browse/JENA-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14256022#comment-14256022
]
Andy Seaborne commented on JENA-632:
------------------------------------
Suggestion; make SELECT JSON a whole new top level query type. It's going to
need it's own evaluation call anyway.
{{<SELECT> <JSON> { getQuery().setQueryJsonType() ; } }}
Either sprinkle LOOKAHEAD (2) or a new token "SELECT"<WS>"JSON" --- or maybe
skepp all than and make it {{JSON}} (no {{SELECT}}).
I don't see why the {{<COMMA>}}is a problem.
A JSON meber/value needs a value and the value can be variable or number.
Something like is
{noformat}
<STRING1> <COLON> (<VAR> | <STRING> | <NUMBER>)
{noformat}
Whether the fild part should be a variable is possible one step too far at the
moment.
> 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: gsoc, 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)
