Closed fkleedorfer closed 2 years ago
Turns out, the problem wasn't in a SPARQL query I changed but in a sh:path
expression I also changed. Should have guessed that, but still - shape information in the error message would have helped spot the problem.
I am currently developing some SHACL SPARQL Rules, and debugging is a bit of a hassle because the error message generated by the Jena SPARQL parser is not enriched with information about which rule it is that can't be parsed. E.g.
I understand it may not be easy to provide meaningful information as the rule shape will be a blank node, but if there is something straightforward you can do to help narrow it down, it will be appreciated!
Cheers!
EDIT: The problem, of course, is that I touched multiple SPARQL Rules since the last run and now I don't know which one it is that cannot be parsed.