You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I also tried running pyshacl with -i rdfs flag with same result.
Pyshacl seems to find 9 errors
TopBraid finds 5
I am expecting 3 validation errors from ex-sh-rl:Or1 , 1 from ex-sh-rl:WrongClass and 1 from ex-sh-rl:bothOrsAtOnce
In other words, for some reason, pyshacl is incorrectly saying that my correctClass and correctSuperClass are wrong for every scenario.
I suspect this is a bug in the pyshacl sh:path builder, related to the use of sh:inversePath wrapped around a sh:zeroOrMorePath. I don't remember seeing that kind of pattern before, and there are no tests in the W3C SHACL test suite that cover that pattern, so our implementation may not get that combination quite right.
I first posted this in the SHACL discord lastweek, but wanted to make an issue here officially.
I'm getting a significantly different result from PySHACL vs TopBraid SHACL validation engine.
parameters for pyshacl:
pyshacl -s shapestest.ttl -m -a -f human -j datatest.ttl
command TopBraid:
.\shaclvalidate.bat -datafile 'datatest.ttl' -shapesfile 'shapestest.ttl'
I also tried running pyshacl with -i rdfs flag with same result.
Pyshacl seems to find 9 errors
TopBraid finds 5
I am expecting 3 validation errors from ex-sh-rl:Or1 , 1 from ex-sh-rl:WrongClass and 1 from ex-sh-rl:bothOrsAtOnce
In other words, for some reason, pyshacl is incorrectly saying that my correctClass and correctSuperClass are wrong for every scenario.
why is there a difference?
Data:
Shapes:
The text was updated successfully, but these errors were encountered: