Re: pre-binding as used in SHACL document

Exactly not.  The definitions in Appendix A of the SHACL document were the
definition of pre-binding for SHACL.   This definition was changed at the last
hour, with no significant internal review and no chance for external review.

The definition was clear and unambiguous.  There was no option to interpret
"replace all project operations" as other than applying to all project operations.

That the definition produced unsuitable results is a severe problem for SHACL
as specified by the Candidate Recommendation version of
https://www.w3.org/TR/shacl/.  Changes to this definition are significant
changes to SHACL and require the opportunity for review.


Peter F. Patel-Schneider
Nuance Communciations


On 05/12/2017 02:35 PM, Irene Polikoff wrote:
> 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 <mailto: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 23:47:52 UTC