Name
xs:maxInclusive — Facet to define a maximum (inclusive) value.
Synopsis
<xs:maxInclusive
fixed = xs:boolean : “false”
id = xs:ID
value = anySimpleType
{any attributes with non-schema namespace}
>
Content: (xs:annotation?)
</xs:maxInclusive>
May be included in: xs:restriction (simple type), xs:restriction (simple content)
May be used as facet for: xs:byte, xs:date, xs:dateTime, xs:decimal, xs:double, xs:duration, xs:float, xs:gDay, xs:gMonth, xs:gMonthDay, xs:gYear, xs:gYearMonth, xs:int, xs:integer, xs:long, xs:negativeInteger, xs:nonNegativeInteger, xs:nonPositiveInteger, xs:positiveInteger, xs:short, xs:time, xs:unsignedByte, xs:unsignedInt, xs:unsignedLong, xs:unsignedShort
Description
xs:maxInclusive defines an inclusive maximum
value. To be valid, a value must be less than or equal to the value
of xs:maxInclusive.
This facet constrains the value space.
Restrictions
It is forbidden to define both xs:maxExclusive and
xs:maxInclusive in the same restriction step.
Although not explicitly specified in the Recommendation, it
doesn’t make sense to define several
xs:maxInclusive facets in a single restriction
step either.
Within a restriction step, xs:maxInclusive is also
dependent on xs:minExclusive and
xs:minInclusive, since using inconsistent values
leads to datatypes with empty value spaces.
xs:maxInclusive must restrict the value space of
its base type, and its value must be in the value space of the base
type.
Fixing the maxInclusive facet
doesn’t fix the xs:maxExclusive
facet. To fix both facets, define two restriction steps since it is
forbidden to apply these two facets in the same restriction step.