Details

    • Type: New Feature
    • Status: Closed
    • Priority: Minor
    • Resolution: Implemented
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      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

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                sallen Stephen Allen
                Reporter:
                sallen Stephen Allen
              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: