- From: Peter F. Patel-Schneider <pfpschneider@gmail.com>
- Date: Thu, 29 Oct 2015 10:45:14 -0700
- To: Holger Knublauch <holger@topquadrant.com>, public-data-shapes-wg@w3.org
On 10/28/2015 10:29 PM, Holger Knublauch wrote: > On 10/29/2015 14:14, Peter F. Patel-Schneider wrote: >> Here is my proposal for a better simplification, based on changes to Part 2 of [...] >> >> I here propose several changes the normative bits of the version of Part 2 >> that was prepared for ISSUE-95, >> http://w3c.github.io/data-shapes/shacl/index-ISSUE-95.html, that fix many of >> the problems there. I have not proposed changes for any of the bits marked >> non-normative or any of the examples. [...] >> 9 >> >> [Remove entirely, as there is no defined way to call functions.] > > This is neither true nor helpful. SHACL functions can be called from every > SPARQL query (e.g. constraint or scope). Regardless of whether we keep > sh:NodeValidationFunctions, the general mechanism has proven to be extremely > successful in SPIN, leading to vastly more compact and better maintainable > SPARQL queries. The fact that sh:NodeValidationFunctions are also normal > SPARQL functions means that the business logic can be reused in multiple > places. There are approved requirements for functions, even "concise language" > falls into that category. How are these functions called from SPARQL? I don't see any mechanism for this. peter
Received on Thursday, 29 October 2015 17:45:47 UTC