Give SHACL findings stable, readable node references - #30
Merged
Conversation
Contributor
|
@claude please review |
mauanga
force-pushed
the
shacl-stable-node-identity
branch
from
July 17, 2026 10:00
079c226 to
0aaec16
Compare
rpanfili
reviewed
Jul 17, 2026
rpanfili
requested changes
Jul 21, 2026
rpanfili
requested changes
Jul 30, 2026
rpanfili
approved these changes
Jul 30, 2026
rpanfili
left a comment
rpanfili
left a comment
Contributor
There was a problem hiding this comment.
Ok, please take care of updating the CHANGELOG file also.
mauanga
force-pushed
the
shacl-stable-node-identity
branch
from
July 31, 2026 08:53
7d2b25b to
2b8f4f8
Compare
mauanga
force-pushed
the
shacl-stable-node-identity
branch
from
July 31, 2026 09:30
2b8f4f8 to
9a2eb54
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Findings pointed at random blank-node hashes for JSON-LD nodes without an @id - they changed every run and matched nothing in the source. Paths came out as hashes too.
Now a finding references a node by its @id, or by a stable JSON pointer (urn:wl:node:/...) when it has none. Paths render as readable names (e.g. address.addressCountry). Real @ids are left alone, and the pointer ids are only used during validation.