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

RE: An evaluation of TriQL

From: Seaborne, Andy <andy.seaborne@hp.com>
Date: Thu, 1 Jul 2004 15:16:04 +0100
Message-ID: <E864E95CB35C1C46B72FEA0626A2E8080361606A@0-mail-br1.hpl.hp.com>
To: Yoshio Fukushige <Fukushige.Yoshio@jp.panasonic.com>
Cc: RDF Data Access Working Group <public-rdf-dawg@w3.org>

Yoshio,

Thank you for adding this evaulation.  The more evaluations, the better.


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?

	Andy


-------- Original Message --------
> From: Yoshio Fukushige <>
> Date: 29 June 2004 16:23
> 
> # This is actually the second time I send the following message.
> # It seems the previous message was lost due to some network problem
> # If you have received the previous message, please ignore this.
> 
> Hi all,
> 
> > And we're accepting new evaluations, at least thru
> > tomorrow's telcon. If a new one comes after that,
> > I don't know if I can get it integrated into an
> > agenda by 1 July, but we can play it by ear.
> > 
> 
> I evaluated the TriQL (a query language by Chis Bizer for the named
> graphs). 
> 
> It's almost the same as the one for RDQL, on which TriQL builds,
> but differs in some points, due to its extension for the named graphs:
> 
> 3.4 Subgraph Results
> 4.2 Provenance
> 
> I put the file in
> http://www.w3.org/2004/06/29-Yoshio/TriQLevaluation.html. 
> 
> @@NOTE@@
>  I (mis?)interpreted the design objective 4.5 Aggregate Query as saying
> the aggregation of the source graphs, not the query results.
> 
> If there's any mis-understanding or ambiguous points, please tell me.
> 
> Here is less readable(?) text-version:
> 
> ----------from here----------
> Evaluation result of the TriQL
> 
> NOTE: This evaluation is based on "TriQL - A Query Language for Named
> Graphs"
> (http://www.wiwiss.fu-berlin.de/suhl/bizer/TriQL/), which is called
> hereafter "the document." in this evaluation.
> 
> Convention
> 
> TriQL+
> 
> TriQL supports this requirement today under a suitable protocol binding
> and/or
> query language.
> 
> TriQL-
> 
> the requirement appears to be explicitly outside of the scope of TroQL,
> which is
> not to say that it could NOT be met by a suitable revision of TriQL.
> 
> TriQL?
> 
> need more information to make the determination.
> 
> Sample Query
> 
>   SELECT ?family , ?given
>   FROM   <http://example.org/JohnzVcard.rdf>
>   WHERE  (?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)
>   AND    ?shoeSize > 5
>   AND    ?age >= ?shoeSize
>   USING  vcard FOR <http://www.w3.org/2001/vcard-rdf/3.0#>
> 
> 3.1 RDF Graph Pattern Matching
> 
> TriQL+
> 
>   WHERE  (?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)
> 
> 3.2 Variable Binding Results
> 
> TriQL+
> 
> SELECT ?family , ?given
> 
> From the spec: [[ The variable "?x" will be bound to the label of the
> subject
> resource. All such "x" are returned ]]
> 
> 
> 3.3 Extensible Value Testing
> 
> TriQL-
> 
> Has support for equality and comparison operators for integers and
> matching 
> operation for strings
> 
> 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
> 
>   SELECT ?graph
>   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)
>   AND    ?shoeSize > 5
>   AND    ?age >= ?shoeSize
>   USING  vcard FOR <http://www.w3.org/2001/vcard-rdf/3.0#>
> 
> User could get all triples in the matched graph
> 
>   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#>
> 
> 3.5 Local Queries
> 
> TriQL+
> 
> The EBNF Grammar does not allow file names,for example "example.trig",
> to 
> appear
> after "FROM" , but in an example appeared in the document, it appears.
> 
> 3.6 Optional Match
> 
> TriQL-
> 
> 3.7 Limited Datatype Support
> 
> TriQL+
> 
> AND    ?shoeSize > 5
> AND    ?age >= ?shoeSize
> AND    ?date > "2003-01-01"^^xsd:date
> (the last example is taken from the document)
> 
> 3.8 Bookmarkable Queries
> 
> TriQL-
> 
> 3.10 Result Limits
> 
> TriQL-
> 
> 3.11 Iterative Query
> 
> TriQL-
> 
> 3.12 Streaming Results
> 
> TriQL-
> 
> 4.1 Human-friendly Syntax
> 
> TriQL+
> 
> TriQL queries read like a sentence (like RDQL).
> 
> 4.2 Provenance
> 
> TriQL+
> 
> This point is what the Named Graphs are for.
> 
>   SELECT ?family, ?given, ?graph
>   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)
>   AND    ?shoeSize > 5
>   AND    ?age >= ?shoeSize
>   USING  vcard FOR <http://www.w3.org/2001/vcard-rdf/3.0#>
> 
> 4.3 Non-existant Triples
> 
> TriQL-
> 
> 4.4 User-specifiable Serialization
> 
> TriQL-
> 
> 4.5 Aggregate Query
> 
> TriQL+
> 
> One can specify more than one Source Selector
> 
> 4.6 Additional Semantic Information
> 
> TriQL-
> 
> 4.6a Additoal Semantic Information(variant)
> 
> TriQL-
> 
> 4.7 Bandwidth-efficient Protocol
> 
> TriQL-
> 
> 4.8 Literal Search
> 
> TriQL+
> 
> 4.9 Boolean Query
> 
> TriQL-
> 
> 
> ----------to  here----------
> 
> Cheers,
> Yoshio
Received on Thursday, 1 July 2004 10:16:45 GMT

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