RE: Semantic Web Phase 2 Activity - Protocol - Query Language


> >>- OUTER JOIN Queries, (optional matches)
> Saying that a common language should include OUTER JOIN is 
> irrelevant IMHO.

perhaps I did not write correctly what I mean,

because from your answer I think you understood that i wanted to have
some SQL standard stuff written in the Rdf-Query standard. Like "to
implement a RDF-Query, you have to use these internal SQL queries" 
thats not what I meant, the OUTER JOIN problem is a RDF problem you have
when you try to use RDQL (a very popular query language, imho).

If you query
(?x foaf:firstname ?y) (?x foaf:image ?z)

I want to retrieve something like:
y: "Leo"


y: "Leo"
z: null

but with today's RDQL this is more complicated:
if there is no <foaf:image> triple for leo, you don't get any data at
AND THAT IS A PROBLEM, if you have ever programmed RDQL, thats the first
thing you curse.
because you can't retrieve a set of properties, you have to formulate
queries for every single property, its just lame.


So the good ol "SQL OUTER JOIN" problem shows up in RDF again....

> may be missing and come up with a document that specifies 
> what the darn 
> language should be able to do against a store, where a store 
> is nothing 
> but a graph or set of graphs.

agreed. thats what a rdf query language is.
Querying RDF (in some result format) from a graph or model or whatever
speaks RDF.


Received on Tuesday, 11 November 2003 11:03:57 UTC