ISSUE-223: Should we disallow shapes with mismatching type
Shapes mismatching type
Should we disallow shapes with mismatching type
- State:
- CLOSED
- Product:
- SHACL - Core
- Raised by:
- Holger Knublauch
- Opened on:
- 2017-02-05
- Description:
- See https://lists.w3.org/Archives/Public/public-rdf-shapes/2017Feb/0001.html it was pointed out that cases like
ex:s1 rdf:type sh:NodeShape ;
sh:targetClass ex:Person ;
sh:path ex:child ;
sh:nodeKind sh:IRI .
can be confusing to users because it's really a property shape despite having sh:NodeShape as type.
While this is an artificially constructed example, a reasonable addition would be to add two syntax rules:
a) SHACL instances of sh:NodeShape cannot have values for sh:path
b) SHACL instances of sh:PropertyShape must have a value for sh:path
making such cases ill-formed shapes. - Related Actions Items:
- No related actions
- Related emails:
- shapes-ISSUE-223 (Shapes mismatching type): Should we disallow shapes with mismatching type [SHACL - Core] (from sysbot+tracker@w3.org on 2017-02-05)
Related notes:
RESOLUTION: CLOSE issue-223 by adding two syntax rules: a) SHACL instances of sh:NodeShape cannot have values for sh:path; b) SHACL instances of sh:PropertyShape must have a value for sh:path
https://www.w3.org/2017/02/08-shapes-minutes.html
Display change log
