Fwd: loss of functionality

I had a similar question about exactly this case. It's basically 
irreflexivity. Whether this is worth allowing it is another question - I 
have no strong opinion. There is a certain attractiveness in saying that 
"property pair constraints are for property shapes only", and of course 
there is always SPARQL. So one solution is to define a new constraint 
component shx:irreflexive true. That's what the extension mechanism is 
for, and we don't need to cover everything with Core.

Any input?

Holger



-------- Forwarded Message --------
Subject:  loss of functionality
Resent-Date:  Thu, 09 Feb 2017 00:46:12 +0000
Resent-From:  public-rdf-shapes@w3.org
Date:  Wed, 8 Feb 2017 16:45:36 -0800
From:  Peter F. Patel-Schneider <pfpschneider@gmail.com>
To:  public-rdf-shapes@w3.org <public-rdf-shapes@w3.org>



I want to write a shape that checks that there are no self-loops with
predicate ex:p for elements of a class ex:c.

The following shape appears to do the trick:

ex:s1
   sh:targetClass ex:c ;
   sh:disjoint ex:p .

Oops, this is no longer valid SHACL!

How can I now do this?


Peter F. Patel-Schneider
Nuance Communications