diff --git a/shacl12-core/index.html b/shacl12-core/index.html index 9a21ca67..f2e51773 100644 --- a/shacl12-core/index.html +++ b/shacl12-core/index.html @@ -586,6 +586,9 @@
rdf:type
in the
graph as well as the SHACL superclasses of these values in the graph.
+ Note that some SHACL implementations can be parameterized so that the rdfs:subClassOf
triples
+ that determine the SHACL subclasses may be queried from the shapes graph in addition to the data graph.
+ See .
+ Note that the rdfs:subClassOf
triples may be queried from the shapes graph
+ (see ) in which case the rdfs:subClassOf
triple
+ from the example above would not be required to be in the data graph.
+
owl:imports
links.
+
+
+ Some features of SHACL (such as
+ ,
+ , and
+ ) rely on the notion
+ of SHACL type to determine whether a node is a SHACL instance of a given class.
+ By default, this is determined by looking up rdfs:subClassOf
and rdf:type
triples
+ in the data graph.
+ However, this is insufficient in some cases, as rdfs:subClassOf
triples are often stored as part
+ of the class and/or shape definitions and not the instance data.
+
+ SHACL processors SHOULD offer a parameter subClassOfInShapesGraph
that, if set to true
,
+ should alter the definition of SHACL Type so that the rdfs:subClassOf
triples are queried
+ from the shapes graph in addition to the data graph.
+ The rdf:type
triples are always expected to be in the data graph.
+
sh:expression
; see Issue 357sh:nodeByExpression
, see Issue 408sh:ByTypes
for sh:closed
; see Issue 172sh:class
and sh:datatype
can now also be lists, indicating a union of choices; see Issue 160sh:ReifierShape
; see Issue 300