shapes-ISSUE-42 (sh:notEqual): Adding sh:notEqual to potential datatype properties? [SHACL Spec]

shapes-ISSUE-42 (sh:notEqual): Adding sh:notEqual to potential datatype properties? [SHACL Spec]

http://www.w3.org/2014/data-shapes/track/issues/42

Raised by: Simon Steyskal
On product: SHACL Spec

Hi!

Relating to my previous raised issue concerning property paths..

I was wondering, whether we want to include an additional datatype property like "sh:notEqual" to express that the value of a certain property must not be equal to the provided one. 

E.g. if I have a concept called ex:Track having two associated properties ex:kmLeft and ex:kmRight and I want to state, that the value of both should not be the same as well as > 0, I could write something like:

ex:Track a rdfs:Class;
  sh:property [
    sh:predicate ex:kmLeft;
    sh:minExclusive 0;
    sh:notEqual (Path to kmRight's value)
  ];
  sh:property [
    sh:predicate ex:kmRight;
    sh:minExclusive 0;
    sh:notEqual (Path to kmLeft's value)
  ].

simon

(Of course, I could use sh:sparql to draft such a constraint myself or define a sh:OrConstraint with sh:minExclusive and sh:max:Exclusive.)

Received on Tuesday, 7 April 2015 08:31:19 UTC