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

Re: Review of revised property path tests

From: Andy Seaborne <andy.seaborne@epimorphics.com>
Date: Mon, 28 Feb 2011 11:41:58 +0000
Message-ID: <4D6B8A06.3020107@epimorphics.com>
To: Matthew Perry <matthew.perry@oracle.com>
CC: W3C SPARQL Working Group <public-rdf-dawg@w3.org>


On 21/02/11 22:07, Matthew Perry wrote:
> Hi Andy,
>
> I took a look at the revised property path tests.
>
> I have a questions about pp16 and pp25.
>
> The text definition in Section 18.4 allows an endpoint to appear as an
> intermediate node on the path.
>
> In pp16, if we allow this, shouldn't we get these additional solutions:
> {X=:e, Y=:e} for :e - foaf:knows -> :f - foaf:knows -> :e
> {X=:d, Y=:e} for :d - foaf:knows -> :e - foaf:knows -> :f - foaf:knows
> -> :e

I'm a bit lost here - are we talking at cross purposes somehow?


{X=:e, Y=:e} are in the solutions pp16.srx once.  Is that right for 
foaf:knows*? Previously, we did have multiples here but you argued 
against that.

http://lists.w3.org/Archives/Public/public-rdf-dawg/2011JanMar/0158.html
http://lists.w3.org/Archives/Public/public-rdf-dawg/2011JanMar/0169.html

Ditto
{X=:d, Y=:e}

---------------------------------------------------
| X                      | Y                      |
===================================================
| <http://example.org/a> | <http://example.org/a> |
| <http://example.org/a> | <http://example.org/b> |
| <http://example.org/a> | <http://example.org/c> |
| <http://example.org/a> | <http://example.org/c> |
| <http://example.org/b> | <http://example.org/b> |
| <http://example.org/b> | <http://example.org/c> |
| <http://example.org/c> | <http://example.org/c> |
| <http://example.org/d> | <http://example.org/d> |
| <http://example.org/d> | <http://example.org/e> | **
| <http://example.org/d> | <http://example.org/f> |
| <http://example.org/e> | <http://example.org/e> | **
| <http://example.org/e> | <http://example.org/f> |
| <http://example.org/f> | <http://example.org/e> |
| <http://example.org/f> | <http://example.org/f> |
| <http://example.org/h> | <http://example.org/h> |
| "test"                 | "test"                 |
---------------------------------------------------

(this is the srx file, reformatted; not evaluating the query).

> In pp25, we would get this additional solution
> {z=:c} for :a - :p -> :c - :p -> :c

I see the test results for pp25 (<diamond-loop-2.srx) in CVS as:

----------------------
| z                  |
======================
| <http://example/c> |
| <http://example/z> |
| <http://example/b> |
| <http://example/z> |
----------------------

(this is the srx file, reformatted; not evaluating the query).

>
> I don't think we should allow the endpoint to appear as an intermediate
> node on the path, I would rather keep the results as they currently are
> in the tests. From my understanding, the semantics in Section 18.5 do
> not allow an endpoint to appear as an intermediate node.
>
> Thanks,
> Matt
>

	Andy
Received on Monday, 28 February 2011 11:42:38 GMT

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