Replacing sh:and/sh:not with just sh:not #562
Merged
Conversation
This file contains 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
PySHACL complains because we have multiple sh:not negation clauses inside a single shape (the object of sh:node). This alternate form should be equivalent while avoiding the pyshacl pedantry
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.
PySHACL complains because we have multiple sh:not negation clauses inside a single shape (the object of sh:node). This alternate form should be equivalent while avoiding the issues for PySHACL. PySHACL is technically correct in rejecting multiple
sh:notclauses in the same shape, but other SHACL processors don't mind this.