Hi Jim,
yes it should work for inverse properties, but the .ttl file currently
does not include a validator (SPARQL query) for that case. I didn't
implement that because this part of the spec had been very unstable. The
WG has this week resolved an outstanding syntax issue which I plan to
implement in the coming week: sh:inverseProperty will be deleted and
generalized using sh:path. Then just a single validator will be needed
for the different cases.
Meanwhile, if you need something urgently, you could add the missing
validator in your own copy of the dash.ttl file.
HTH
Holger
On 1/07/2016 1:11, Jim Balhoff wrote:
Hi,
I am trying to use sh:inverseProperty and sh:qualifiedValueShape together in a
SHACL shape. When I try to validate some triples using the SHACL API I get this
output:
[ a <http://datashapes.org/dash#FailureResult> ;
<http://www.w3.org/ns/shacl#message>
"No suitable validator found for constraint" ;
<http://www.w3.org/ns/shacl#sourceConstraint>
_:b0 ;
<http://www.w3.org/ns/shacl#sourceConstraintComponent>
<http://www.w3.org/ns/shacl#QualifiedMaxCountConstraintComponent> ;
<http://www.w3.org/ns/shacl#sourceShape>
<OneBiologicalFatherInverse>
] .
A nearly identical shape that uses sh:property instead of sh:inverseProperty
does work for me. Should this work with sh:inverseProperty? The two shapes and
a tiny data file are here:
https://gist.github.com/balhoff/6bb8edc4e6cca38f800fe21f14a08f8f
Thank you,
Jim
--
You received this message because you are subscribed to the Google Group "TopBraid
Suite Users", the topics of which include the TopBraid Suite family of products and
its base technologies such as SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to [email protected]
---
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].
For more options, visit https://groups.google.com/d/optout.
