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

Re: An evaluation of TriQL

From: Yoshio Fukushige <fukushige.yoshio@jp.panasonic.com>
Date: Tue, 6 Jul 2004 17:55:57 +0900
Message-ID: <006501c46337$0db45650$f6e41b85@IRONGEAR>
To: "Seaborne, Andy" <andy.seaborne@hp.com>
Cc: "RDF Data Access Working Group" <public-rdf-dawg@w3.org>

Hello, Andy

Thank you for your pointing out.

> I don't follow this part though:
> > 3.4 Subgraph Results
> >
> > TriQL+?
> >
> > Yes if the graph is written in TriG or TriX.
> >
> > The server could return the NAME of the matched graph
> Returning the name of the graph isn't the same as returning a subgraph
> because it's just a name.  Even if it returned the contents of the named
> graph, it isn't a selected subgraph (its not part of a graph); isn't it a
> subcomponent of the named graph collection?

Your pointing out is right, which means I was wrong.

A user could get the subgraph as a set of triples (each of which is in the
form of a triplet of binding to the variables ?subj, ?pred. ?obj),
but it would be possible only in very limited case.

For it to happen,  matched triples should be in A (named) graph, or the
query which I proposed (cited below) wouldn't match.

x> >   SELECT ?subj, ?pred, ?obj
> >   FROM   <http://example.org/JohnzVcard.rdf>
> >   WHERE  ?graph (?vcard  vcard:FN "John Smith" .
> >     ?vcard  vcard:N  ?name .
> >           ?name   vcard:Family  ?family .
> >    ?name   vcard:Given  ?given)
> >           ?name   vcard:age  ?age.
> >              ?name   vcard:shoeSize  ?shoeSize
> >    ?subj  ?pred ?obj)
> >   AND    ?shoeSize > 5
> >   AND    ?age >= ?shoeSize
> >   USING  vcard FOR <http://www.w3.org/2001/vcard-rdf/3.0#>

And even in that case, it would be doutful whether returning all the triples
in the graph could be called returning a subgraph (in the intended meaning

I change the evaluation result from TriQL? to TriQL-

Thank you very much.

Received on Tuesday, 6 July 2004 04:54:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:00:28 UTC