ISSUE-136: Can we clarify the names of property pair constraint types?
Property pair names
Can we clarify the names of property pair constraint types?
- State:
- CLOSED
- Product:
- SHACL - Core
- Raised by:
- Holger Knublauch
- Opened on:
- 2016-03-13
- Description:
- We currently use the following terms to represent relationships between properties:
sh:equals (?predicate has same values as the other property)
sh:notEquals (?predicate has different values...)
sh:lessThan (all values of ?predicate must be less than values of other property)
sh:lessThanOrEquals ( <= )
I believe it is too easy for a reader to assume that the values of these properties are not other properties but constants, e.g. "must be less than 10". But for that we already have sh:maxExclusive etc.
We should consider renaming to something like
sh:equalProperty
sh:notEqualProperty
sh:lessThanProperty
sh:lessThanOrEqualProperty - Related Actions Items:
- No related actions
- Related emails:
- Some issues that may be close to resolution (from holger@topquadrant.com on 2016-04-06)
- Re: shapes-ISSUE-136 (Property pair names): Can we clarify the names of property pair constraint types? [SHACL - Core] (from holger@topquadrant.com on 2016-03-16)
- Re: ISSUE-133: multi-occurrence use cases (from holger@topquadrant.com on 2016-03-14)
- Re: shapes-ISSUE-136 (Property pair names): Can we clarify the names of property pair constraint types? [SHACL - Core] (from kcoyle@kcoyle.net on 2016-03-13)
- shapes-ISSUE-136 (Property pair names): Can we clarify the names of property pair constraint types? [SHACL - Core] (from sysbot+tracker@w3.org on 2016-03-13)
Related notes:
RESOLUTION: Close ISSUE-136, keeping sh:equals, sh:lessThan, sh:lessThanOrEquals, changing sh:notEquals to sh:disjoint
See https://www.w3.org/2016/04/07-shapes-minutes.html#resolution03
Display change log