W3C home > Mailing lists > Public > public-lod@w3.org > August 2008

RE: BSBM With Triples and Mapped Relational Data in Virtuoso

From: Orri Erling <erling@xs4all.nl>
Date: Sat, 9 Aug 2008 19:35:59 +0200
Message-Id: <200808091737.m79Hb2Wj040589@smtp-vbr14.xs4all.nl>
To: "'Seaborne, Andy'" <andy.seaborne@hp.com>, "'Chris Bizer'" <chris@bizer.de>, <public-lod@w3.org>


We might as well make an interoperable implementation of SPARQL protocol and
client API's for supporting stored procedures and parametrized queries.

What is the Arq way to call a procedure for side effect exactly once over
the web protocol?

As I recall, the Jena query execution factory interface did not have
provisions for parametrized queries.  Now, maybe there is such but what is

Passing bindings for named SPARQL variables as an outermost scope for the
query sounds OK.  Aside this, we do positional parameters  SQL style but
then only through SQL CLI's  or SQL procedures. 

If there are no parameter markers syntactically distinct from variables,
then the set of bound parameters is part of the  query's text, so to say.
So we cache a query's compilation as a function of the source text and the
set of parameter names plus protocol request options.  This is possible.  At
first glance, named parameters seem OK. This is a notch prettier than
positional since the SPARQL syntax is not affected.  

So, if you have a complete spec, re API's and protocol, let's implement it.
Parameters will save 1/3 of BSBM execution time, so we might as well have
them now.


Received on Saturday, 9 August 2008 17:37:46 UTC

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