W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > July to September 2004

rql implementation

From: Kendall Clark <kendall@monkeyfist.com>
Date: Fri, 17 Sep 2004 06:18:59 -0500
Message-ID: <20040917061859.A19084@monkeyfist.com>
To: public-rdf-dawg@w3.org

Dan was asking about whether any query language implements the stuff I've 
suggested in these messages:

UC&R 4.6 use case and discussion
http://lists.w3.org/Archives/Public/public-rdf-dawg/2004JulSep/0491.html

getting more concrete about 4.6
http://lists.w3.org/Archives/Public/public-rdf-dawg/2004JulSep/0403.html

The first message details Jena API bits, so it's implemented.

The second message details RQL features, so it's implemented.

The question arose about RQL's implementation details. Its web page says,

  The RQL Interpreter (v2.1) has been implemented in C++ on top of an ORDBMS
  (PostgreSQL v7.3 or higher) using a standard client-server architecture
  for Solaris and Linux platforms. It consists of four modules (a) the
  Parser, analyzing the syntax of queries; (b) the Graph Constructor,
  capturing the semantics of queries in terms of typing and
  interdependencies of involved expressions; (c) the SQL Translator, which
  rewrites RQL to efficient SQL queries; and (d) the Evaluation Engine,
  accessing the underlying database via SQL queries.

Which seems a fairly ordinary implementation strategy. It's not exotic in
any obvious sense.

Kendall Clark
-- 
You're one in a million
You've got to burn to shine
Received on Friday, 17 September 2004 11:19:01 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:20 GMT