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

Re: Incompatibilities in RDQL implementations

From: Chris Bizer <chris@bizer.de>
Date: Thu, 6 May 2004 15:13:31 +0200
Message-ID: <00df01c4336b$edb250a0$0f8d2da0@wrz03295>
To: "Seaborne, Andy" <andy.seaborne@hp.com>, "Phil Dawes" <pdawes@users.sourceforge.net>, <www-rdf-interest@w3.org>


Hi Andy and Phil,

> And that's one of the reasons we have the RDF Data Access Working Group
:-)

Looks like Phil is just doing all the work the working group was planning to
do, by implementing the netAPI for the major stores and by pushing the RDQL
imlementers on agreeing on Andy's W3C submission :-)

> Jena's RDQL accepts all those forms.  Historically, commas and <> on
qnames
> (the qname-like prefixing mechanism) were required.  That got relaxed in
> later versions.  I leave it to the query writer to decide what makes a
query
> readable - it is usally a matter of what they are used to.  If you write
N3
> a lot, <> on the qname-like constructs is odd.

RAP will follow the Jena approach and be flexible or if this is not possible
for any reasons I don't see now implement Andy's W3C RDQL submission. Radek,
the guy who implemented RAP's RDQL engine is on holiday this week, but
agreed to change our parser next week.

> > 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.

Great thing to do :-) We were planning to do the same and I think Andy was
also planning to implement Joseki clients in all programming languages he
knows. Phil: When you are done it would be great if you could send us your
code and we will include it in the next RAP release.

Chris
Received on Thursday, 6 May 2004 09:09:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:52:07 GMT