OptionalandFacets of the SAME <xs:restriction> beyond this one. XSD facets in
a single restriction are conjunctive — a value must satisfy every
one — but one IDSConstraint expresses only one family, so
parseRestriction keeps the first here and hangs the rest off this
list for matchConstraint to require as well. Unset for the
overwhelmingly common single-family restriction. Matching
(matchConstraint) and the two description paths
(formatConstraint, TranslationService.describeConstraint)
account for it, and so do the IDS-document auditors under audit/
(coherence and predefined-type checks visit every sibling, IDS-010).
OptionalbaseThe originating xs:restriction @base (e.g. xs:double,
xs:integer). Set when the constraint came from an
<xs:restriction> so the auditor can compare against the IFC
dataType's backing type directly.
Optionalfractionxs:fractionDigits — maximum number of digits after the decimal point
Optionallengthxs:length — exact string length
OptionalmaxMaximum exclusive value
OptionalmaxMaximum inclusive value
Optionalmaxxs:maxLength — maximum string length
OptionalminMinimum exclusive value
OptionalminMinimum inclusive value
Optionalminxs:minLength — minimum string length
OptionaltemporalThe bound facets of an xs:date / xs:dateTime / xs:time /
xs:duration restriction, as their validated lexical text. Those
value spaces are not numbers, so the numeric min* / max* fields
above stay unset for them and the bounds live here instead, compared
in the base's own order (#7399).
Optionaltotalxs:totalDigits — maximum number of significant decimal digits
OptionalunparseableFacets whose <xs:*Inclusive|Exclusive|Length|Digits> element was
PRESENT in the source <xs:restriction> but whose @value is not in
the lexical space the facet requires: for a min/max bound, the
restriction @base's (#7399); for a length or digit-count facet, a
non-negative integer — e.g. a typo'd "6O" (letter O), the European
decimal "6,5", or "2024-13-01" under xs:date. Distinct from a facet that was
never present at all: the corresponding numeric field above is
undefined in BOTH cases, but only this list distinguishes "no
such constraint" from "the author tried to constrain this and
failed." matchBounds fails closed (rejects every value) when this
is non-empty, rather than silently treating a botched restriction
as unbounded.
Bounds constraint - numeric range or string length