Skip to content

Commit

Permalink
Correct poorly worded assembly constraint explanation.
Browse files Browse the repository at this point in the history
Co-authored-by: David Waltermire <david.waltermire@nist.gov>
  • Loading branch information
aj-stein-nist and david-waltermire committed Aug 22, 2023
1 parent 4abfaef commit f37f2ce
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion website/content/specification/syntax/constraints.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,9 @@ TODO: P3: Address issue https://github.com/usnistgov/metaschema/issues/325

## Enumerated values

One kind of Metaschema constraint is restricting assembly, field, or flag value(s) with `allowed-values` enumerations. Metaschema processors MUST process `allowed-values` enumerations as defined with the `allow-other` attribute.
One kind of Metaschema constraint is restricting field, or flag value(s) with `allowed-values` enumerations. Metaschema processors MUST process `allowed-values` enumerations.

For an `allowed-values` enumeration, the following applies for the `allow-other` attribute:

1. When the `allow-other` attribute is defined as `allow-other="no"`, the processor MUST strictly validate content instances with enumerations: only defined `enum` values are valid for the given target(s).
2. When the `allow-other` attribute is defined as `allow-other="yes"`, the processor MUST loosely validate content instances with enumerations: both `enum` values and other values are valid.
Expand Down

0 comments on commit f37f2ce

Please sign in to comment.