xs:minExclusive — Facet to define a minimum (exclusive) value.
<xs:minExclusive
fixed = xs:boolean : “false”
id = xs:ID
value = anySimpleType
{any attributes with non-schema namespace}
>
Content: (xs:annotation?)
</xs:minExclusive>
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
xs:minExclusive defines an exclusive minimum
value. To be valid, a value must be strictly greater than the value
of xs:minExclusive.
This facet constrains the value space.
It is forbidden to define both xs:minExclusive and
xs:minInclusive in the same restriction step.
Although not explicitly specified in the Recommendation, it
doesn’t make sense to define several
xs:minExclusive facets in a single restriction
step either.
Within a restriction step, xs:minExclusive is also
dependent on xs:maxExclusive and
xs:maxInclusive, since using inconsistent values
leads to datatypes with empty value spaces.
xs:minExclusive must restrict the value space of
its base type, and its value must be in the value space of the base
type.
Fixing the xs:minExclusive facet
doesn’t fix the xs:minInclusive
facet. To fix both facets, define two restriction steps since it is
forbidden to apply these two facets in the same restriction step.