ISSUE-117: sh:class should not require that its objects be known to be instances of rdfs:Class
non-classes as classes
sh:class should not require that its objects be known to be instances of rdfs:Class
- State:
- CLOSED
- Product:
- SHACL - Core
- Raised by:
- Peter Patel-Schneider
- Opened on:
- 2016-01-11
- Description:
- Currently the spec says:
The property sh:class can be used to verify that each value of the given property is an instance of a given type. The values of sh:class must be classes (instances of rdfs:Class).
In Holger's implementation this is checked in conjunction with the data graph, meaning that a SHACL shape's syntactic correctness depends on the data graph.
Instead, objects sh:class triples should not need to be instances of rdfs:Class. This means that the shape
[ rdf:type sh:Shape; sh:scopeClass pp:Person ;
sh:property [ rdf:type sh:PropertyConstraint;
sh:predicate pp:pet; sh:class pp:Pet; sh:minCount 1 ] ]
should be syntactically correct. - Related Actions Items:
- No related actions
- Related emails:
- Re: shapes-ISSUE-117 (non-classes as classes): sh:class should not require that its objects be known to be instances of rdfs:Class [SHACL - Core] (from holger@topquadrant.com on 2016-01-20)
- Re: shapes-ISSUE-117 (non-classes as classes): sh:class should not require that its objects be known to be instances of rdfs:Class [SHACL - Core] (from arthur.ryman@gmail.com on 2016-01-19)
- shapes-ISSUE-117 (non-classes as classes): sh:class should not require that its objects be known to be instances of rdfs:Class [SHACL - Core] (from sysbot+tracker@w3.org on 2016-01-11)
Related notes:
RESOLUTION: Close ISSUE-117, dropping from Section 3.1.1 sh:class the sentence "The values of sh:class must be classes (instances of rdfs:Class)." and any assertions that sh:predicate must be an rdfs:Property
See https://www.w3.org/2016/02/04-shapes-minutes.html#resolution03
Display change log