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

Re: Incompatibilities in RDQL implementations

From: Phil Dawes <pdawes@users.sf.net>
Date: Thu, 6 May 2004 17:34:08 +0100
Message-ID: <16538.26880.730818.529936@gargle.gargle.HOWL>
To: Jeen Broekstra <jeen@aduna.biz>
Cc: www-rdf-interest@w3.org, andy.seaborne@hp.com

Hi Jeen,

I've written a quick-and-dirty wrapper which converts rdql to seRQL
construct queries to mimic josekis RDQL and FETCH api. It also
supports content negotiation via http Accept: headers.

I'm not sure how useful this will be, since I wrote the wrapper in
jython. It's a warfile (with jython.jar imbedded) so it should work
out-of-the-box on a servlet container:


You'll need to edit the webapi.py file to reflect your sesame server
URI and storename, then point your browser at


The convert code is in rdqlToSeRQL.py file, and isn't very
feature-complete (it doesn't do AND clauses).

Hope this helps in some vague way!



Jeen Broekstra writes:
 > Phil,
 > Phil Dawes wrote:
 > > I am currently writing wrapper code around Sesame[2] and RAP[3] to
 > > give them web interfaces corresponding to the Joseki webapi[4]. The
 > > point of the exercise is to be able to write web client code that is
 > > store agnostic.
 > We've been having similar plans for Sesame, or at least to update our 
 > Web protocol to be more RESTful, so this sounds very relevant for us! 
 > Let us know if you need any help (apart from the bugfixes in RDQL ;)), 
 > and also: if your code is finished at some point it would be great if 
 > you could submit it so we can include it in a future release of Sesame...
 > Cheers,
 > Jeen
 > -- 
 > Jeen Broekstra          Aduna BV
 > Knowledge Engineer      Julianaplein 14b, 3817 CS Amersfoort
 > http://aduna.biz        The Netherlands
 > tel. +31(0)33 46599877  fax. +31(0)33 46599877
Received on Thursday, 6 May 2004 12:35:26 UTC

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