Name
xs:minInclusive — Facet to define a minimum (inclusive) value.
Synopsis
<xs:minInclusive fixed = xs:boolean : “false” id = xs:ID value = anySimpleType {any attributes with non-schema namespace} > Content: (xs:annotation?) </xs:minInclusive>
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:minInclusive
defines an inclusive minimum
value. To be valid, a value must be greater than or equal to the
value of xs:minInclusive
.
This facet constrains the value space.
Restrictions
It is forbidden to define both xs:minInclusive
and
xs:minExclusive
in the same restriction step.
Although not explicitly specified in the Recommendation, it
doesn’t make sense to define several
xs:minInclusive
facets in a single restriction
step either.
Within a restriction step, xs:minInclusive
is also
dependent on xs:maxExclusive
and
xs:maxInclusive
, since using inconsistent values
leads to datatypes with empty value spaces.
xs:minInclusive
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:minInclusive
facet
doesn’t fix the xs:minExclusive ...
Get XML Schema now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.