W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > January to March 2009

Re: Next telecon features & beyond

From: Lee Feigenbaum <lee@thefigtrees.net>
Date: Fri, 13 Mar 2009 14:25:38 -0400
Message-ID: <49BAA522.1050107@thefigtrees.net>
To: Alexandre Passant <alexandre.passant@deri.org>
CC: SPARQL Working Group <public-rdf-dawg@w3.org>
Alexandre Passant wrote:
> Hi,
> 
> Le 12 mars 09 à 06:49, Lee Feigenbaum a écrit :
> 
>> Next week I'd like to continue where we left off, with brief 
>> discussions of some of the more "major" suggested features that impact 
>> the query language itself. These include:
>>
>> Assignment
>> Property paths - Andy
>> Aggregates
>> Negation
>> Update
>> Basic Federated Query
>> Parameterized inference/control of inference
> 
> I thinks that Path Length [1] may also be included in that list, as a 
> major feature.
> 
> As it strongly relates to property path: Andy, OpenLink, any objection 
> to merge the two features in a single page ?
> (As path length does not makes any sense without the path itself, it's 
> obvious for the inclusion in that direction, but I want to be sure both 
> of you agree on adding another feature (lenght) to your path initial 
> proposal.)

I don't see these as being the same at all. My understanding is that 
property paths allow me to specify in a regular expression-like way an 
explicit chain that connects two nodes. For path length, you need to 
start having variables match arbitrary-length paths between nodes, 
right? (Once you ahve a variable matching a path, then it's natural to 
add a function to get the length of that path.) And that seems like a 
whole other ball of wax to me.

Am I misunderstanding?

Lee
Received on Friday, 13 March 2009 18:26:28 GMT

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