-
Notifications
You must be signed in to change notification settings - Fork 165
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
SHACL - Blank node IDs should be preserved for remote validation reports #4622
Closed
Comments
Can you elaborate on why this is necessary? |
I updated the issue. |
hmottestad
added a commit
that referenced
this issue
Jun 14, 2023
…lign with how RDF data is typically transmitted over HTTP
hmottestad
added a commit
that referenced
this issue
Jun 17, 2023
…lign with how RDF data is typically transmitted over HTTP
hmottestad
added a commit
that referenced
this issue
Oct 3, 2023
…lign with how RDF data is typically transmitted over HTTP
5 tasks
hmottestad
added a commit
that referenced
this issue
Oct 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Blank node IDs should be preserved for remote validation reports because users need to be able to look up data in the repository based on the validation report model.
One typical use case is for retrieving the full SHACL Shape from the repository. PropertyShape(s) are usually blank nodes, and when the report refers to a PropertyShape it uses the blank nodes.
Another use case is where the validation report refers to a blank node from the users data that is causing the validation violation.
The text was updated successfully, but these errors were encountered: