SHACL validation incorrectly creates a violation for the sh:or constraint when the NodeShape with the sh:or constraint also has a complex sh:property pointing towards a sh:node (Which is a NodeShape in itself).
Visit https://s.zazuko.com/RJmit for a minimum working example (mwe).
We expect the SHACL report to look like this:
SHACL validation incorrectly creates a violation for the
sh:or
constraint when the NodeShape with thesh:or
constraint also has a complexsh:property
pointing towards ash:node
(Which is a NodeShape in itself).Visit https://s.zazuko.com/RJmit for a minimum working example (mwe). We expect the SHACL report to look like this:
In the mwe the
sh:detail
contains an additional SHACL violation that we don't expect to see in the SHACL report.