- From: Kevin Wilkinson <wilkinson@hpl.hp.com>
- Date: Thu, 15 Jul 2004 11:21:50 -0700
- To: public-rdf-dawg@w3.org
this is related to something ericP, andyS and
i were discussing on monday. specifically,
eric suggested the ability to compose queries
run over different data sources was useful.
for example, given a manufacturer data source
of products and a number of vendors that
sell those products, it would be very useful
to compose the two queries:
1) search manufacturer data source for
products that match criteria x,y,z
2) search all vendor sources for prices
on the matching products.
so, the result bindings of #1 become
parameters (argument bindings) for #2.
this can be done in the client application
program. but there are convenience and
performance advantages when done in the
query subsystem (DAWG layer) directly.
enabling query composition requires the
ability to "name" queries and requires
queries to have arguments.
the obvious choice of a name is a URI.
parameterized queries are useful in any case.
seems like a very useful ability (query
composition - also supported in functional
languages like xsrql, i believe).
i don't know if ericP and andyS have
raised the issue at the f2f. but, i'd
like to see it included as a requirement
or an objective. :)
kevin
Dan Connolly wrote:
>
> On Wed, 2004-07-14 at 15:17, Tom Adams wrote:
> > FYI: I know some people are not on the comments list. As I've already
> > replied to one of these comments previously, I'd be happy to reply
> > again to this and the next one???
>
> It's useful (though not completely essential) to propose
> (or at least sketch) a reply here
> in this forum first.
>
> --
> Dan Connolly, W3C http://www.w3.org/People/Connolly/
Received on Thursday, 15 July 2004 14:19:59 UTC