> the inner anonymous node shapes also have a sh:targetClass
Ahh, I get it now! Because of the target class specifications these blank
nodes target the node (again). Removing those made things work as
expected :).
Thanks for your prompt help!
On Friday, February 10, 2023 at 2:59:00 PM UT
But in the example that you linked to, the 3rd condition is outside of the
sh:or block, which is enclosed by ( ... )
So it's evaluated directly under ex:Person and not as part of sh:or, which only
has two operands.
Holger
> On 10 Feb 2023, at 1:55 pm, A.L. Kleijngeld wrote:
>
> Hi Holger,
>
Hi Holger,
My point is that I expected the overall report status to be "Success: Yes".
If one of the three shapes in the OR succeeds (and like you say, one does),
then there's no actual violation, right?
(Btw, I do understand that during the evaluation of the OR, two node shapes
yield a (simil
But the page says Success: No
and then lists two violations.

I guess the violations shows up twice because the inner anonymous node shapes
also have a sh:targetClass. But the sh:or validates fine because the second
shape about having at least one comment is valid.
Holger
> On 10 Feb 2023,
Hi,
I just read some very enlightening discussions on here that cleared up
sh:or big time for me!
Still, I'm a bit confused.
See: https://s.zazuko.com/3hDRN1r
So, the way I interpret what I've written is as follows.
The indivual is targeted by all three node shapes connected by
the sh:or, i
This is weird.
Yesterday I made an example and I was in doubt whether to check if I did it
right here.
“
A SHACL coding example for the fact that the underlying datatype for the
attribute ‘dbl:numberOfBuildingUnits’ for a dbl:Building is an xsd:integer:
dbl:Building a rdfs:Class, sh:NodeShape
