Taken from the specification:
>>>
A node shape is a shape <https://www.w3.org/TR/shacl/#dfn-shape> in the shapes
graph <https://www.w3.org/TR/shacl/#dfn-shapes-graph> that is not the
subject <https://www.w3.org/TR/shacl/#dfn-subject> of a triple
<https://www.w3.org/TR/shacl/#dfn-rdf-triple> with *sh:path* as its
predicate <https://www.w3.org/TR/shacl/#dfn-predicate>. SHACL instances
<https://www.w3.org/TR/shacl/#dfn-shacl-instance> of sh:NodeShape cannot
have a value <https://www.w3.org/TR/shacl/#dfn-value> for the
property sh:path.
>>>
Yet when talking Or Constraint or And Constraint, that takes list of
shapes, we find example like what follow:
>>>>
ex:SuperShape a sh:NodeShape ;
sh:property [ sh:path ex:property ; sh:minCount 1 ; ] .
ex:ExampleAndShape a sh:NodeShape ;
sh:targetNode ex:ValidInstance, ex:InvalidInstance ;
sh:and (
ex:SuperShape
[
sh:path ex:property ;
sh:maxCount 1 ;
] ) .
>>>>
With the following explanation
>>>
The following example illustrates the use of sh:and in a shape to specify
the condition that certain focus nodes have exactly one value
of ex:property. This is achieved via the conjunction of a separate named
shape (ex:SuperShape) which specifies the minimum count, and a *blank node
shape* that additionally specifies the maximum count. As shown
here, sh:and can be used to implement a specialization mechanism between
shapes.
>>>>
How on earth is this a Blank Node shape if it is the subject of an sh:path,
am I missing something ?
```
[
sh:path ex:property ;
sh:maxCount 1 ;
]
```
--
You received this message because you are subscribed to the Google Groups
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/a36d9325-ff9a-4329-86a3-64a463798b1dn%40googlegroups.com.
