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

Re: ACTION-brief review of property paths

From: Andy Seaborne <andy.seaborne@talis.com>
Date: Tue, 05 Jan 2010 11:20:48 +0000
Message-ID: <4B432090.5000004@talis.com>
To: Axel Polleres <axel.polleres@deri.org>
CC: SPARQL Working Group <public-rdf-dawg@w3.org>


On 04/01/2010 11:41 PM, Axel Polleres wrote:
> Very short review: This document is in good shape for FPWD, no objections against publication.
> my initial comments have already been answered, cf.
> http://lists.w3.org/Archives/Public/public-rdf-dawg/2010JanMar/0008.html
>
> Two Small things:
>
>
> * Outstanding issues section:
>
> "This feature can be mnore useful if results are return in order"
> ->
> "This feature can be more useful if results are returned in order"
>

Done.

>
> * One thing I am unsure about concerning the precedences:
>    [...]
>    # Unary ^ inverse links
>    # Unary operators *, ?, + and {} forms
>    #  Binary operators / and ^
>    [...]
>
> So, in
>    elt1 ^ elt2 +
> '+' binds stronger than '^'
> but in the "expanded" version
>    elt1 / ^ elt2 +
> it is the other way around? It seems, if this is intended, then
>    "elt1 ^ elt2 +"
> should in fact be expanded to
>    "elt1 / ^(elt2+)"
> ?
>
> If this is an issue indeed, could that be solved by just reordering precedence as follows?
>
>    [...]
>    # Unary operators *, ?, + and {} forms
>    # Unary ^ inverse links
>    [...]

That would be better.  Change made.  In fact, the grammar agrees with you:

PathElt	 	 ::=	 PathPrimary PathMod?
PathEltOrInverse ::=	 PathElt | '^' PathElt

	Andy
Received on Tuesday, 5 January 2010 11:21:22 GMT

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