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

Rob Vesse commented on JENA-226:
--------------------------------

Also we should be careful here because this basically sounds like "write the 
Sesame Repository API in Jena" - I'm not saying it is a bad idea I'm just 
suggesting that we should try and be clear what the specific goals of the new 
feature are 
e.g.

-  What is the proposed high level API?
-  Are we assuming an API that talks only SPARQL or are we postulating a more 
general API (e.g. the Storage API from dotNetRDF which just works in terms of 
coarse operations like Save Graph, Load Graph, Delete Graph, SPARQL Query, 
SPARQL Update etc) for which me may have multiple implementations thereof?
                
> New Client API
> --------------
>
>                 Key: JENA-226
>                 URL: https://issues.apache.org/jira/browse/JENA-226
>             Project: Apache Jena
>          Issue Type: New Feature
>            Reporter: Stephen Allen
>            Assignee: Stephen Allen
>            Priority: Minor
>
> Develop a new API geared towards bridging the gap between local Jena 
> databases and remote SPARQL HTTP endpoints.  This would provide a single 
> object to represent a repository, and provide functions to perform querying 
> and modification of the data in the repository.  These functions would 
> attempt to be as efficient as possible (i.e. streaming modifications to 
> remote servers), while also promoting safe practices such as parameterizing 
> user supplied query inputs to prevent SPARQL-injection attacks.
> I've started writing up some use cases at [1] (would like to move over to the 
> Confluence Wiki shortly).  And I've also started a branch [2] (not much there 
> yet).  Feedback is greatly appreciated.
> [1] http://people.apache.org/~sallen/jena/ClientUseCases.html
> [2] 
> http://svn.apache.org/repos/asf/incubator/jena/Jena2/ARQ/branches/ArqClient

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to