- From: Peter F. Patel-Schneider <pfpschneider@gmail.com>
- Date: Mon, 7 Mar 2016 08:29:08 -0800
- To: Holger Knublauch <holger@topquadrant.com>, public-data-shapes-wg@w3.org
On 03/06/2016 08:46 PM, Holger Knublauch wrote: [...] > On 7/03/2016 6:59, Peter F. Patel-Schneider wrote: [...] >> The wording about sh:hasShape seems to imply SPARQL engines that only cover >> the core need not provide a mechanism that mirrors sh:hasShape. This might >> be true at the moment, as recursion is not supported, but may not be true in >> the future. > > I don't see why the current wording implies what you state. In The definition of some constraints assume that SPARQL engines provide a function called sh:hasShape as elaborated in the beginning of section 3. In the advanced sections, SHACL introduces mechanisms to define constraints, scopes and new functions in SPARQL. Implementations that only plan to cover the SHACL Core features are not required to support those mechanisms. it is not obvious what "these mechanisms" refers to. It could be read to cover sh:hasShape. peter
Received on Monday, 7 March 2016 16:29:40 UTC