[ 
https://issues.apache.org/jira/browse/JENA-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456243#comment-16456243
 ] 

ASF GitHub Bot commented on JENA-632:
-------------------------------------

Github user kinow commented on the issue:

    https://github.com/apache/jena/pull/114
  
    Branch created: 
[JENA-632-before-merge](https://github.com/kinow/jena/tree/JENA-632-before-merge).
 Won't delete it this year, in case we need to revisit.
    
    Followed that by:
    
    ```
    $ git rebase -i HEAD~18
    $   # fixed-up all but the first commit
    $ git diff JENA-632-before-merge 
    $   # empty response, code is identical even though different commit tree
    $ git checkout master
    $ git merge JENA-632-2
    $ git commit --amend
    $   # added This closes #114 message to close this pull request
    $ mvn clean test install -Pdev
    $ git push git-at-apache master
    ```



> 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
>            Assignee: Bruno P. Kinoshita
>            Priority: Minor
>              Labels: java, javacc
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> 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
(v7.6.3#76005)

Reply via email to