Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected behavior SPARQL targets #40

Open
rmfranken opened this issue Jan 9, 2025 · 0 comments
Open

Unexpected behavior SPARQL targets #40

rmfranken opened this issue Jan 9, 2025 · 0 comments

Comments

@rmfranken
Copy link

rmfranken commented Jan 9, 2025

Hi there,

since the new release of your version 1.0.1 I was curious to check how your playground performs with some use cases I have that include sparql targets.

I found that although they are seemingly interpreted by your SHACL engine, the shapes including a sh:select are not working as I expect (while they are working how I expect in the TopQuadrant engine).

I have used your playground - and find the following:

I receive 1 error for contract 1, 1 for contract 2, 2 for contract 3 and 3 for contract 4.

I expect no errors for contract 1 and contract 3, and I expect 1 error for contract 2, and 2 errors for contract 4.

Is it safe to say that SPARQL targets are not yet supported? If so - why are they evaluated like this? When I run the included select query on the same data in a SPARQL engine, I receive the expected errors.

Please let me know if I can provide you with any more information to help, I am super happy that there is finally another SHACL implementation out there with SPARQL support (even if it is once again in a language I'm painfully unfamiliar with ;) )

Kind regards,
Robin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant