Make references to original SHACL consistent #548
Merged
Conversation
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
ajnelson-nist
approved these changes
Aug 28, 2025
There was a problem hiding this comment.
I'm approving because I saw nothing worth blocking the PR with "Request changes."
I think this should wait to merge until after a WG call to briefly discuss a section name. I've added an agenda item for Monday.
I think some of the links to specifications should use full-date URLs because of their back-in-time nature. However, I can see that request being a bit moot if the dateless URLs for the original SHACL specifications are expected to remain forever-static.
HolgerKnublauch
approved these changes
Aug 28, 2025
Co-authored-by: Alex Nelson <alexander.nelson@nist.gov>
Co-authored-by: Alex Nelson <alexander.nelson@nist.gov>
Co-authored-by: Alex Nelson <alexander.nelson@nist.gov>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This de-brands the original SHACL as SHACL 1.0 as that versioning was never originally used and is problematic given that SHACL 1.2 is linked to RDF 1.2 while the original SHACL specification was linked to RDF 1.1.