Skip to content

Commit

Permalink
Fix typo in target attribute explanation
Browse files Browse the repository at this point in the history
Fix typo pointed out by @wendellpiez in PR review, ignore->ignored, in the section about the target attribute.

Co-authored-by: Wendell Piez <[email protected]>
  • Loading branch information
aj-stein-nist and wendellpiez authored Dec 5, 2023
1 parent e712397 commit f445e53
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion website/content/specification/syntax/constraints.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ When provided, the value of a `@target` MUST be a valid Metapath expression.

If a `@target` value is not defined, a Metaschema processor MUST process the value as `target="."`, the current context of that constraint definition in a module, for a [field](#define-field-constraints) or [flag](#define-flag-constraints).

A *target* can apply to any node(s) in the document instance(s). There is no guarantee the constraint *target* is a child of its respective assembly, field, or flag. Thus, a Metaschema processor MUST resolve the Metapath expression to identify the actual target nodes that the constraint applies to. If no resulting target nodes are identified, then the constraint MUST be ignore.
A *target* can apply to any node(s) in the document instance(s). There is no guarantee the constraint *target* is a child of its respective assembly, field, or flag. Thus, a Metaschema processor MUST resolve the Metapath expression to identify the actual target nodes that the constraint applies to. If no resulting target nodes are identified, then the constraint MUST be ignored.

## Constraint Processing

Expand Down

0 comments on commit f445e53

Please sign in to comment.