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

Re: Shapes Constraint Language (SHACL) Working Draft of 2017-02-02

From: Irene Polikoff <irene@topquadrant.com>
Date: Wed, 8 Feb 2017 01:02:44 -0500
Cc: "<public-rdf-shapes@w3.org>" <public-rdf-shapes@w3.org>
Message-Id: <991773F0-E079-4F62-9F59-6C2353F7F7C0@topquadrant.com>
To: "Peter F. Patel-Schneider" <pfpschneider@gmail.com>
Peter,

The word MAY was not used to talk about this variable in the published draft. Having said this, I think the tension you are describing may have to do with the fact that section 5.3.1 talks about $shapesGraph and $currentShape as optional *if supported*, while sections 5.3 and 6.3 that refer to it said that these variables MUST be used.

Please see modified language for sections 5.3 and 6.3 in the latest editor’s draft. Does this clarify the topic in your view?

Regards,

Irene Polikoff

> On Feb 7, 2017, at 6:18 PM, Peter F. Patel-Schneider <pfpschneider@gmail.com> wrote:
> 
>>> 
>>> * $shapesGraph
>>> 
>>> The status of $shapesGraph is unclear:
>>> "SPARQL variables using the $ marker represent external values that must be
>>> pre-bound or substituted in the SPARQL query before execution."
>>> "SHACL validation engines MAY pre-bind the variable $shapesGraph to provide
>>> access to the shapes graph.”
> 
>> RESPONSE: Please clarify the issue. What is unclear?
> 
> The first sentence says that $-marked variables must be pre-bound or
> substituted.  The second contracts that by using may.  The wording here has
> changed somewhat, but it is still a tension between the two wordings.


Received on Wednesday, 8 February 2017 06:03:22 UTC

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