Skip to content
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

validation filter ordering #23

Closed
wants to merge 1 commit into from
Closed

validation filter ordering #23

wants to merge 1 commit into from

Conversation

marqh
Copy link
Member

@marqh marqh commented Nov 9, 2016

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 clarity
Thus, 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

Filter shapes MUST be validated before validating the associated shapes or constraints.
This includes scenarios such as <a href="#ShapeConstraintComponent">
<code>sh:shape</code></a> where a shape is explicitly referenced by another constraint.
However, during the validation of a shape referenced via <code>sh:shape</code>, the 
<a>targets</a> of these shapes are not used to limit the set of focus nodes.
-				</p>

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?

reinsert explicit ordering of filter evaluation and constraint evaluation in validation
@HolgerKnublauch
Copy link
Contributor

Closing as outdated - we have deleted filter shapes altogether.

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.

2 participants