-
Notifications
You must be signed in to change notification settings - Fork 40
Correct link to "solution" #694
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
base: gh-pages
Are you sure you want to change the base?
Conversation
a920a1a to
e0af305
Compare
robert-david
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if i understood this correctly, but the anchors
https://www.w3.org/TR/shacl12-core/#dfn-binding
https://www.w3.org/TR/shacl12-core/#dfn-solution
still don't work.
HolgerKnublauch
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually I noticed that #668 is not yet approved and has the same fix but in shacl-sparql. I suggest to approve that branch instead and change the links to shacl12-sparql as my PR deletes them from shacl-core.
The TR version is the state of the default to branch ( |
|
A link for solution now goes to SPARQL Query. There is nothing gained by involving SHALCL SPARQL. |
|
@HolgerKnublauch - this needs your review - the previous block remains active. |
Correct link to "solution", remove "binding".
(SHACL Core uses "binding" for prefixes)