[
https://issues.apache.org/jira/browse/JENA-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13236257#comment-13236257
]
Stephen Allen commented on JENA-226:
------------------------------------
Yes, the intention is to build something like JDBC's Connection or Sesame's
Repository API for SPARQL-like objects. Those can be remote repositories or
local DatasetGraphs.
I'm still working on defining the high level API, but the motivating problem
was one of efficiently generating RDF from within my client application,
sending that to a remote repository (SPARQL Update or Graph Store Protocol).
I'd want it to be streaming on both ends, since it could be a very large amount
of data. After it was uploaded, I would then like to be able to query it.
All this through an API that provided transaction support while abstracting
away the actual location of the RDF store.
> 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
