Skip to content

Issue 481 - move nodeByExpression and expression to Node Expr spec and give better examples #492

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

Open
wants to merge 7 commits into
base: gh-pages
Choose a base branch
from

Conversation

HolgerKnublauch
Copy link
Contributor

@HolgerKnublauch
Copy link
Contributor Author

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).

@TallTed TallTed changed the title Issue 481 Issue 481 - move nodeByExpression and expression to Node Expr spec and give better examples Aug 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

move nodeByExpression, expression to Node Expr spec and give better examples
3 participants