0

The AllegroGraph RDF Store provides multiple channels to communicate through. I am developing a Web Service for that. I have the following questions:

How to implement a Web Service over this SPARQL Endpoint? What are the best practices? CXF or Axis?

Ben Companjen
  • 1,417
  • 10
  • 24
Saravana Kumar
  • 113
  • 3
  • 16
  • A SPARQL endpoint *is* a (REST) web service. Are you sure you need this? – Jeen Broekstra Jan 02 '13 at 07:21
  • @JeenBroekstra Actually I need to query a DataSet from AG where client applications will pass only API ID and not the entire query as parameters. Any pointers would be highly appreciated. – Saravana Kumar Jan 14 '13 at 23:25

1 Answers1

1

The link you provided points to the AllegroGraph API documentation. The documentation says:

The protocol described here is compatible (is a super-set of) with the Sesame 2.0 HTTP protocol and the W3C SPARQL protocol (SPARQL endpoint).

I think you may want to develop a small library that sits between AllegroGraph and the client applications and 'speaks' this protocol, which appears to be a combination of "normal" REST and SPARQL. A client application can then pass the arguments to your library, which translates them to arguments in a SPARQL query or normal REST request.
For these operations, you may be able to use one of the tools mentioned in this answer, or use an SPARQL API like Jena ARQ and a general REST API like JAX-RS, or similar functions in programming language of your project.

Depending on your project, you can integrate these functions (SPARQL and REST calls) with the client application. You could of course provide the services again as a web service (using e.g. CXF or Axis), but if you control the client application(s) this may be too much for your project.

Community
  • 1
  • 1
Ben Companjen
  • 1,417
  • 10
  • 24