- Simple type varieties
- Simple type definitions
- Simple type restrictions
- Facets
- Preventing simple type derivation
This chapter is from the book
This chapter is from the book
This chapter is from the book
9.3 Simple type restrictions
Every simple type is a restriction of another simple type, known as its base type. It is not possible to extend a simple type, except to add attributes, which results in a complex type. This is described in Section 14.4.1, "Simple content extensions." Every new simple type restricts the value space of its base type in some way. Example 9–3 shows a definition of DressSizeType that restricts the built-in type integer.
Example 9–3. Deriving a simple type from a built-in simple type
<xsd:simpleType name="DressSizeType">
<xsd:restriction base="xsd:integer">
<xsd:minInclusive value="2"/>
<xsd:maxInclusive value="18"/>
<xsd:pattern value="\d{1,2}"/>
</xsd:restriction>
</xsd:simpleType>
Simple types may also restrict user-derived simple types that are defined in the same schema document, or even in a different schema document. For example, you could further restrict DressSizeType by defining another simple type, MediumDressSizeType, as shown in Example 9–4.
Example 9–4. Deriving a simple type from a user-derived simple type
<xsd:simpleType name="MediumDressSizeType">
<xsd:restriction base="DressSizeType">
<xsd:minInclusive value="8"/>
<xsd:maxInclusive value="12"/>
</xsd:restriction>
</xsd:simpleType>
A simple type restricts its base type by applying facets to restrict its values. In Example 9–4, the facets minInclusive and maxInclusive are used to restrict the value of MediumDressSizeType to be between 8 and 12 inclusive.
9.3.1 Defining a restriction
The syntax for a restriction element is shown in Table 9–3. You must specify one base type either by using the base attribute, or by defining the simple type anonymously using a simpleType child. The alternative of using a simpleType child is generally only useful when restricting list types, as described in Chapter 11, "Union and list types."
Table 9–3 XSDL syntax: simple type restriction
|
Name |
|||
|
restriction |
|||
|
Parents |
|||
|
simpleType |
|||
|
Attribute name |
Type |
Required/default |
Description |
|
id |
ID |
|
unique ID |
|
base |
QName |
either a base attribute or a simpleType child is required |
simple type that is being restricted |
|
Content |
|||
annotation? , simpleType? , (minExclusive | minInclusive | maxExclusive | maxInclusive | length | minLength | maxLength | totalDigits | fractionDigits | enumeration | pattern | whiteSpace)* |
|||
Within a restriction element, you can specify any of the facets, in any order. However, the only facets that may appear more than once in the same restriction are pattern and enumeration. It is legal to define a restriction that has no facets specified. In this case, the derived type allows the same values as the base type.
9.3.2 Overview of the facets
The available facets are listed in Table 9–4.
The XSDL syntax for applying a facet is shown in Table 9–5. All facets must have a value attribute, which has different valid values depending on the facet. Most facets may also have a fixed attribute, as described in Section 9.3.4, "Fixed facets." Certain facets are not applicable to some types. For example, it does not make sense to apply the fractionDigits facet to a character string type. There is a defined set of applicable facets for each of the built-in types1. If a facet is applicable to a built-in type, it is also applicable to atomic types that are derived from it. For example, since the length facet is applicable to string, if you derive a new type from string, the length facet is also applicable to your new type. Section 9.4, "Facets," describes each of the facets in detail and lists the built-in types to which the facet can apply.
Table 9–4 Facets
|
Facet |
Meaning |
|
minExclusive |
value must be greater than x |
|
minInclusive |
value must be greater than or equal to x |
|
maxInclusive |
value must be less than or equal to x |
|
maxExclusive |
value must be less than x |
|
length |
the length of the value must be equal to x |
|
minLength |
the length of the value must be greater than or equal to x |
|
maxLength |
the length of the value must be less than or equal to x |
|
totalDigits |
the number of significant digits must be less than or equal to x |
|
fractionDigits |
the number of fractional digits must be less than or equal to x |
|
whiteSpace |
the schema processor should either preserve, replace, or collapse whitespace depending on x |
|
enumeration |
x is one of the valid values |
|
pattern |
x is one of the regular expressions that the value may match |
9.3.3 Inheriting and restricting facets
When a simple type restricts its base type, it inherits all of the facets of its base type, its base type's base type, and so on back through its ancestors. Example 9–4 showed a simple type MediumDressSizeType whose base type is DressSizeType. DressSizeType has a pattern facet which restricts its value space to one or two-digit numbers. Because MediumDressSizeType inherits all of the facets from DressSizeType, this same pattern facet applies to MediumDressSizeType also. Example 9–5 shows an equivalent definition of MediumDressSizeType, where it restricts integer and has the pattern facet applied.
Sometimes a simple type definition will include facets that are also specified for one of its ancestors. In Example 9–4, MediumDressSizeType includes minInclusive and maxInclusive, which are also applied to its base type, DressSizeType. The minInclusive and maxInclusive facets of MediumDressSizeType (whose values are 8 and 12, respectively) override those of DressSizeType (2 and 18, respectively).
Table 9–5 XSDL syntax: facet
|
Name |
|||
|
minExclusive, minInclusive, maxExclusive, maxInclusive, length, minLength, maxLength, totalDigits, fractionDigits, enumeration, pattern, whiteSpace |
|||
|
Parents |
|||
|
restriction |
|||
|
Attribute name |
Type |
Required/default |
Description |
|
id |
ID |
|
unique ID |
|
value |
various |
required |
value of the restricting facet |
|
fixed |
boolean |
false; n/a for pattern, enumeration |
whether the facet is fixed and therefore cannot be restricted further, see Section 9.3.4 |
|
Content |
|||
|
annotation? |
|||
Example 9–5. Effective definition of MediumDressSizeType
<xsd:simpleType name="MediumDressSizeType">
<xsd:restriction base="xsd:integer">
<xsd:minInclusive value="8"/>
<xsd:maxInclusive value="12"/>
<xsd:pattern value="\d{1,2}"/>
</xsd:restriction>
</xsd:simpleType>
It is a requirement that the facets of the derived type (in this case MediumDressSizeType) be more restrictive than those of the base type. In Example 9–6, we define a new restriction of DressSizeType, called SmallDressSizeType, and set minInclusive to 0. This type definition is illegal, because it attempts to expand the value space by allowing 0, which was not valid for DressSizeType.
Example 9–6. Illegal attempt to extend a simple type
<xsd:simpleType name="SmallDressSizeType">
<xsd:restriction base="DressSizeType">
<xsd:minInclusive value="0"/>
<xsd:maxInclusive value="6"/>
</xsd:restriction>
</xsd:simpleType>
This rule also applies when you are restricting the built-in types. For example, the short data type has a maxInclusive value of 32767. It is illegal to define a restriction of short that sets maxInclusive to 32768.
Although enumeration facets can appear multiple times in the same type definition, they are treated in much the same way. If both a derived type and its ancestor have a set of enumeration facets, the values of the derived type must be a subset of the values of the ancestor. An example of this is provided in Section 9.4.4, "Enumeration." Likewise, the pattern facets specified in a derived type must allow a subset of the values allowed by the ancestor types. Schema processors will not necessarily check that the regular expressions represent a subset, but it will instead validate instances against the patterns of both the derived type and all the ancestor types, effectively taking the intersection of the pattern values.
9.3.4 Fixed facets
When you define a simple type, you can fix one or more of the facets. This means that further restrictions of this type cannot change the value of the facet. Any of the facets may be fixed, with the exception of pattern and enumeration. Example 9–7 shows our DressSizeType with fixed minExclusive and maxInclusive facets, as indicated by a fixed attribute that is set to true.
Example 9–7. Fixed facets
<xsd:simpleType name="DressSizeType">
<xsd:restriction base="xsd:integer">
<xsd:minInclusive value="2" fixed="true"/>
<xsd:maxInclusive value="18" fixed="true"/>
<xsd:pattern value="\d{1,2}"/>
</xsd:restriction>
</xsd:simpleType>
With this definition of DressSizeType, it would have been illegal to define the MediumDressSizeType as shown in Example 9–4 because it attempts to override the minInclusive and maxInclusive facets, which are now fixed. Some of the built-in types have fixed facets that cannot be overridden. For example, the built-in type integer has its fractionDigits facet fixed at 0, so it is illegal to derive a type from integer and specify a fractionDigits that is not 0.
9.3.4.1 Design hint: When should I fix a facet?
Fixing facets makes your type less flexible, and discourages other schema authors from reusing it. Keep in mind that any types that may be derived from your type must be more restrictive, so you are not at risk that your type will be dramatically changed if its facets are unfixed.
A justification for fixing facets might be that changing that facet value would significantly alter the meaning of the type. For example, suppose you want to define a simple type that represents price. You define a Price type, and fix the fractionDigits at 2. This still allows other schema authors to restrict Price to define other types, such as, for example, a SalePrice type whose values must end in 99. However, they cannot modify the fractionDigits of the type, because this would result in a type not representing a price with both dollars and cents.