W3C home > Mailing lists > Public > public-data-shapes-wg@w3.org > March 2015

sh:sparqlFilter (was: On the inevitability of SPARQL/SPIN for SHAQL)

From: Holger Knublauch <holger@topquadrant.com>
Date: Tue, 03 Mar 2015 13:21:25 +1000
Message-ID: <54F528B5.7000205@topquadrant.com>
To: public-data-shapes-wg@w3.org
On 3/3/2015 13:04, Peter F. Patel-Schneider wrote:
> Even if other execution languages for SHACL are possible, an execution 
> language selector in SHACL will only balkanize SHACL. 

Related to this, I had thought about allowing something like 
sh:sparqlFilter as syntactic sugar, as illustrated in the following example

     sh:constraint [
         sh:message "All values of myProperty must be IRIs" ;
         sh:path ex:myProperty ;
         sh:sparqlFilter "!isIRI(?value)" ;
     ] .

which would be translated into

SELECT (?this AS ?root) (ex:myProperty AS ?path) ?value
     ?this ex:myProperty ?value .
     FILTER (!isIRI(?value))

This may potentially provide a cleaner separation of selection paths and 
a FILTER condition, probably closer to what Jose suggested in his XPath 
discussion. If SPARQL is the main language, then the property 
sh:sparqlFilter could be called sh:filter.

It however also raises new questions:
- adds complexity to implementers/new users
- many ways of representing the same thing
- some tools may decide to only support those (another balkanization)
- unclear whether FILTER should return true or false (as with ASK)
- it would still only address a (small?) fraction of the overall problem 
- it may invite similar properties such as sh:xpath - unclear whether we 
want this

So that relative benefits of this proposal would need to be carefully 
evaluated. The Simister/Brickley paper [1] had a similar idea.


Received on Tuesday, 3 March 2015 03:22:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:30:17 UTC