ISSUE-42: Adding sh:notEqual to potential datatype properties?

sh:notEqual

Adding sh:notEqual to potential datatype properties?

State:

CLOSED

Product:

SHACL Spec

Raised by:

Simon Steyskal

Opened on:

2015-04-07

Description:

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.)

Related Actions Items:

No related actions

Related emails:

1. shapes-ACTION-22: Propose a "more compelling" use case for = and != for property paths (issue-41, issue-42) (from sysbot+tracker@w3.org on 2015-05-07)
2. RDF Data Shapes WG agenda for 07 May 2015 (from eric@w3.org on 2015-05-06)
3. shapes-ISSUE-42 (sh:notEqual): Adding sh:notEqual to potential datatype properties? [SHACL Spec] (from sysbot+tracker@w3.org on 2015-04-07)

Related notes:

Display change log