Closed rdstn closed 4 years ago
After reading the spec a bit closer I think the correct approach is to omit sh:value for sh:hasValue and for dash:hasValueIn.
If there should be a value for sh:value then it should be mentioned in the spec: https://www.w3.org/TR/shacl/#HasValueConstraintComponent
I really wish that the shacl document could have a nice little table showing which contraint components can be used together and which produce a sh:value.
When using the new extended dash:hasValueIn constraint component, validation reports duplicate the
sh:focusNode
value in thesh:value
field.Example SHACL shape:
Example SPARQL:
The SPARQL produces the following report:
Expected:
This was observed while running RDF4J 3.3.0