Issue 481 - move nodeByExpression and expression to Node Expr spec and give better examples
#492
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
HolgerKnublauch
requested review from
robert-david,
simonstey and
recalcitrantsupplant
|
Note there seems to be something wrong with the W3C specs right now, as all references to external specs are broken. As a result, the preview is full of errors (but the same happens to SHACL Core right now, so this doesn't seem to be our problem). |
robert-david
approved these changes
Aug 11, 2025
TallTed
changed the title
nodeByExpression and expression to Node Expr spec and give better examples
recalcitrantsupplant
approved these changes
Aug 13, 2025
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.
Closes #481