ISSUE-160: Shall we generalize sh:valueShape to sh:shape
Generalize sh:valueShape
Shall we generalize sh:valueShape to sh:shape
- State:
- CLOSED
- Product:
- SHACL - Core
- Raised by:
- Holger Knublauch
- Opened on:
- 2016-05-11
- Description:
- Currently sh:valueShape only applies to property constraints. However, this means that it cannot easily be used in cases like sh:or. Also, there is no reason not to allow it for NodeConstraints.
PROPOSAL: Rename sh:valueShape to sh:shape, add sh:NodeConstraint to its context. - Related Actions Items:
- No related actions
- Related emails:
- Re: shapes-ISSUE-160 (Generalize sh:valueShape): Shall we generalize sh:valueShape to sh:shape [SHACL - Core] (from holger@topquadrant.com on 2016-05-21)
- Re: shapes-ISSUE-160 (Generalize sh:valueShape): Shall we generalize sh:valueShape to sh:shape [SHACL - Core] (from pfpschneider@gmail.com on 2016-05-20)
- Re: shapes-ISSUE-160 (Generalize sh:valueShape): Shall we generalize sh:valueShape to sh:shape [SHACL - Core] (from holger@topquadrant.com on 2016-05-20)
- Re: shapes-ISSUE-160 (Generalize sh:valueShape): Shall we generalize sh:valueShape to sh:shape [SHACL - Core] (from pfpschneider@gmail.com on 2016-05-19)
- shapes-ISSUE-160 (Generalize sh:valueShape): Shall we generalize sh:valueShape to sh:shape [SHACL - Core] (from sysbot+tracker@w3.org on 2016-05-11)
Related notes:
https://github.com/w3c/data-shapes/commit/9f36692adb1d26da02ededeac75133cb0917d4fa
Holger Knublauch, 27 May 2016, 00:23:07RESOLUTION: Close ISSUE-160, renaming sh:valueShape to sh:shape, adding sh:NodeConstraint to its context
See https://www.w3.org/2016/05/26-shapes-minutes.html#resolution05
Display change log
