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.
potential text, in explicit change to the proposal in
https://www.w3.org/2014/data-shapes/track/issues/185
please do not merge without explicit resolution
I have reinserted explicit ordering of filter evaluation and constraint evaluation in validation
I have not used the word
ordering
. I wonder if an extra statement with this word in would add clarityThus, filter shapes are validated and valid nodes are passed on for validation with respect to the associated shapes or constraints: the processing is ordered.
I have not included the explicit text removed in
139f7de#diff-69303a57193e6c2d7327c8de0fc977caL1069
I think I have captured the sense of it and I am not sure these examples belong in
3. Validation Definition
maybe we add these somewhere else?