W3C home > Mailing lists > Public > www-rdf-interest@w3.org > December 2004

RE: Joseki as a Web Service?

From: Seaborne, Andy <andy.seaborne@hp.com>
Date: Thu, 9 Dec 2004 13:42:44 -0000
Message-ID: <8D5B24B83C6A2E4B9E7EE5FA82627DC9600C9D@sdcexcea01.emea.cpqcorp.net>
To: "Wei Xing" <xing@ucy.ac.cy>, "mail-list-rdf" <www-rdf-interest@w3.org>

Hi there,

Joseki does split into the core engine that handles queries and a
wrapper that handles the protocol specific side.  There is no reason for
being tied to just HTTP GET and the deployments environments you point
out have facilities that are needed.

It has always been my intention to produce a SOAP protocol adapter for
it and the code is structured with the intention of making that
possible.  It just hasn't happened.

The alternative is to have a gateway which speaks SOAP outwards and
passes requests on Joseki over HTTP or over some other connector
protocol that the web server speaks.  Joseki can be deployed in any web
application server such as Tomcat or Jetty so the gateway function
doesn't even have to be a separate machine or process.  This may be a
simpler deployment option for if any overheads don't significantly
impact performance.

Plans at the moment are to track and implement the SPARQL protocol in a
new version (Joseki3) together with a Jena implementation of the query
language part (ARQ).  There is an early prototype of Joseki3 (and ARQ)
and if you are start to invest in the area, you may wish to go with
these, depending on your timescales and robustness needs.  The SPARQL
protocol and query language are sufficiently different that these are
not compatible with the current main releases.

The SPARQL protocol should have concrete bindings for both HTTP GET and
SOAP but my guess is that the HTTP GET one will be first.

If you are interested in developing a SOAP front-end now, which would be
more work than a gateway, then let me know and we can discuss what can
be done to make this easier for you.


SPARQL / query language: working draft:
SPARQL / protocol: working draft:
To be published soon.

Online demo of Joseki3 and ARQ:

Builds of prototypes (liitle documentation - ask questions on jena-dev):
and the code is in CVS on SourceForge.

-------- Original Message --------
> From: Wei Xing <mailto:xing@ucy.ac.cy>
> Date: 9 December 2004 09:54
> Dear Andy:
> I write to you regarding the Joseki implementation.
> My name is Wei Xing, from University of Cyprus. Within two EU IST
> projects (EGEE and CoreGrid),  we are implementing a set of Grid
> services (Gridable Web Services) for sharing  RDF metadata
> among distributed  Grid sites using Jena toolkit.  Thus we  are very
> instered
> of the Joseki.  However,  Joseki  runs as a simple httpd server where
> the published
> Jena model can be accessed via HTTP  GET. This solution might not
> fulfill the reqirements of the Open Grid Service Architecture (OGSA),
> for instance, the SOAP and the security (e.g. X509 based).
> Not sure if your group have a plan  for Joseki merging into Web
> architecture?
> if not, can possible please give me suggestions on how to deploy
> within the Web Service Architecture? Thanks in advance!
> Best regard
> Wei Xing
> --
> ============================================================
> Wei Xing, M.Sc.
> Research Associate                    Tel: 00357-22892663
> Dept. of Computer Science             Fax: 00357-22892701
> University of Cyprus                  email: xing@ucy.ac.cy
> PO Box 20537
> CY1678, Nicosia, CYPRUS
Received on Thursday, 9 December 2004 13:43:17 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:07:54 UTC