Closed CFGrote closed 2 weeks ago
I confirm the issue. Nothing to do with the property path. Something weird is going on with n3store, maybe a dependency upgrade issue.
The config is buggy. You have
shapes:SIO_001166
sh:name "annotation"@en ;
sh:node shapes:Go_term ;
(lowercase "o" in "Go_term")
but you have
shapes:GO_term rdf:type sh:NodeShape , owl:NamedIndividual ;
(uppercase "O" in GO_term)
Thanks for catching @tfrancart . That seems to solve it.
In the wake of #602, I now observe the following behaviour:
My shacl config;
Explanation:
Property shape
shapes:SIO_001166
relates NodeShapeshapes:SO_0000316
to NodeShapeshapes:GO_term
via a two part property path. Thesh:targetClass
ofshapes:GO_term
is undefined (actually a BlankNode).The problem is that the generated sparql query contains a
?GO_term rdf:type shapes:GO_term .
clause, which is not matched in the queried graph since the targeted object is a BN. Previously, I was able to fix this kind of problem through thenodeKind sh:Literal
property on the NodeShape. Am I doing it wrong here or is it a problem related to the multipart property path?Screenshot:![image](https://github.com/sparna-git/Sparnatural/assets/15476807/9c77817f-d69d-4546-8e9f-022007772985)
Removing line 5 from the query then produces the expected results:![image](https://github.com/sparna-git/Sparnatural/assets/15476807/c98ecf7f-01b0-430d-8adb-aad94f2f55e6)