W3C home > Mailing lists > Public > public-rdf-shapes@w3.org > May 2017

Re: pre-binding as used in SHACL document

From: Irene Polikoff <irene@topquadrant.com>
Date: Fri, 12 May 2017 17:35:53 -0400
Cc: "public-rdf-shapes@w3.org" <public-rdf-shapes@w3.org>
Message-Id: <1ACF2925-13D0-43FA-B72E-F030E0D56F3C@topquadrant.com>
To: "Peter F. Patel-Schneider" <pfpschneider@gmail.com>
Exactly. These definitions were there only for subqueries. They did not intend to be applied in any other situation. This is how they were understood by everyone - as proven by implementations.

The problems you pointed out would only exist if these rules were understood to apply to the top level queries. No one (including, as far as I can tell, yourself - until 3 days ago) interpreted them this way. 

These rules are now removed because they are no longer needed by the sub queries.

As for following the process, the WG did check with the W3M on what changes could be made without going through another CR round.

> On May 12, 2017, at 3:51 PM, Peter F. Patel-Schneider <pfpschneider@gmail.com> wrote:
> 
> None of the examples that I provided
> involve subqueries at all.  What did happen here was that I pointed out that
> the definition of pre-binding as of 9 May 2017 produces unsuitable results for
> quite a few queries that are in the SHACL document.


Received on Friday, 12 May 2017 21:36:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:02:50 UTC