Movatterモバイル変換

Theactual value of thename[attribute], if present on the<simpleType> element,otherwiseabsent

Theactual value of thetargetNamespace[attribute]of the parentschema element information item, if present,otherwiseabsent.

The appropriatecase among the following:

1Ifthe<restriction> alternative is chosen,thenthe type definitionresolved to by theactual value of thebase[attribute] of<restriction>, if present, otherwise thetype definition corresponding to the<simpleType> amongthe[children] of<restriction>.

2Ifthe<list> or<union> alternative is chosen,then·anySimpleType·.

A subset of{restriction,extension,list,union}, determined as follows.[Definition:] LetFS betheactual value of thefinal[attribute], if present, otherwise theactual value of thefinalDefault[attribute] of the ancestorschema element, if present, otherwise the empty string. Then the property value isthe appropriatecase among the following:

1If·FS· is the empty string,thenthe empty set;

2If·FS· is '#all',then{restriction,extension,list,union};

3otherwiseConsider·FS· asa space-separated list, and includerestriction if'restriction' is in that list, and similarly forextension,list andunion.

The appropriatecase among the following:

1Ifthename[attribute] is present,thenabsent

2otherwise the appropriatecase among the following:

2.1Ifthe parent element information item is<attribute>,thenthe correspondingAttribute Declaration

2.2Ifthe parent element information item is<element>,thenthe correspondingElement Declaration

2.3Ifthe parent element information item is<list> or<union>,thentheSimple Type Definitioncorresponding to the grandparent<simpleType> element information item

2.4otherwise(the parent element information item is<restriction>), the appropriatecase among the following:

2.4.1Ifthe grandparent element information item is<simpleType>,thentheSimple Type Definitioncorresponding to the grandparent

2.4.2otherwise(the grandparent element information item is<simpleContent>), theSimple Type Definition which is the{content type} of theComplex Type Definitioncorresponding to the great-grandparent<complexType> element information item.

{variety}

If the<list> alternative is chosen,thenlist, otherwise if the<union> alternative ischosen, thenunion, otherwise (the<restriction>alternative is chosen) the{variety}of the{base type definition}.

{facets}

The appropriatecase among the following:

1Ifthe<restriction> alternative is chosen,thenthe set ofConstraining Facet components obtained byoverlayingthe{facets} of the{base type definition} with theset ofConstraining Facet components corresponding to those[children] of<restriction> which specify facets, asdefined inSchema Component Constraint: Simple Type Restriction (Facets).

2Ifthe<list> alternative is chosen,thena set with one member, awhiteSpace facet with{value} =collapse and{fixed} =true.

3otherwisethe empty set

{fundamental facets}

Based on{variety},{facets},{base type definition} and{member type definitions}, a set ofFundamental Facet components, oneeach as specified inThe ordered Schema Component (§4.2.1.1),The bounded Schema Component (§4.2.2.1),The cardinality Schema Component (§4.2.3.1) andThe numeric Schema Component (§4.2.4.1).

Theannotation mapping of the set of elements containing the<simpleType>, and the<restriction>, the<list>, or the<union>[child], whichever is present, as defined in sectionXML Representation of Annotation Schema Components of[XSD 1.1 Part 1: Structures].

[Definition:] Theancestors of atype definition are its{base type definition} and the·ancestors· of its{base type definition}.(The ancestors of aSimple Type DefinitionT in the type hierarchy are themselvestype definitions; they are distinct fromthe XML elements which may be ancestors, in the XML documenthierarchy, of the<simpleType> element which declaresT.)

If the{variety} isatomic, the following additional propertymapping also applies:

Atomic Simple Type DefinitionSchema Component

Property

Representation

From among the·ancestors· of thisSimple Type Definition, thatSimple Type Definition which corresponds to a·primitive· datatype.

Example

An electronic commerce schema might define a datatype called'SKU'(the barcode number that appears on products) from the·built-in· datatypestring bysupplying a value for the·pattern· facet.

<simpleType name='SKU'>    <restriction base='string'>      <pattern value='\d{3}-[A-Z]{2}'/>    </restriction></simpleType>

In this case, 'SKU' is the name of the new·user-defined· datatype,string isits·base type· and·pattern· is the facet.

If the{variety} islist, the followingadditional property mappings also apply:

List Simple Type DefinitionSchema Component

Property

Representation

The appropriatecase among the following:

1Ifthe{base type definition} is·anySimpleType·,thentheSimple Type Definition (a)resolved to by theactual value of theitemType[attribute] of<list>,or (b) corresponding to the<simpleType> amongthe[children] of<list>, whichever is present.

Note: In thiscase, a<list> element will invariably be present; it willinvariably have either anitemType[attribute] or a<simpleType>[child], but not both.

2otherwise(that is, the{base type definition} is not·anySimpleType·), the{item type definition} of the{base type definition}.

Note: In this case, a<restriction> element will invariably be present.

Example

A system might want to store lists of floating point values.

<simpleType name='listOfFloat'>  <list itemType='float'/></simpleType>

In this case,listOfFloat is the name of the new·user-defined· datatype,float is its·item type· and·list· is thederivation method.

If the{variety} isunion, the followingadditional property mappings also apply:

Union Simple Type DefinitionSchema Component

Property

Representation

Simple type definition ofanySimpleType

The appropriatecase among the following:

1Ifthe{base type definition} is·anySimpleType·,thenthe sequence of (a) theSimple Type Definitions(a)resolved to by the items in theactual value of thememberTypes[attribute] of<union>, ifany, and (b) those corresponding to the<simpleType>samong the[children] of<union>, if any, in order.

Note: In this case, a<union> element will invariably bepresent; it will invariably have either amemberTypes[attribute] or one or more<simpleType>[children],or both.

2otherwise(that is, the{base type definition} is not·anySimpleType·), the{member type definitions} of the{base type definition}.

Note: In this case, a<restriction> element will invariablybe present.

Example

As an example, taken from a typical display oriented text markup language,one might want to express font sizes as an integer between 8 and 72, or withone of the tokens "small", "medium" or "large". The·union·Simple Type Definitionbelow would accomplish that.

<xs:attribute name="size">  <xs:simpleType>    <xs:union>      <xs:simpleType>        <xs:restriction base="xs:positiveInteger">          <xs:minInclusive value="8"/>          <xs:maxInclusive value="72"/>        </xs:restriction>      </xs:simpleType>      <xs:simpleType>        <xs:restriction base="xs:NMTOKEN">          <xs:enumeration value="small"/>          <xs:enumeration value="medium"/>          <xs:enumeration value="large"/>        </xs:restriction>      </xs:simpleType>    </xs:union>  </xs:simpleType></xs:attribute>

<p><font size='large'>A header</font></p><p><font size='12'>this is a test</font></p>

A datatype can be·constructed· from a·primitive· datatype or an·ordinary· datatype by one of three means:by·facet-based restriction·, by·list· or by·union·.

4.1.3 Constraints on XML Representation of Simple Type Definition

Schema Representation Constraint: itemType attribute or simpleType child

Either theitemType[attribute] or the<simpleType>[child] of the<list> elementmustbe present, but not both.

Schema Representation Constraint: base attribute or simpleType child

Either thebase[attribute] or thesimpleType[child] of the<restriction>elementmustbe present, but not both.

Schema Representation Constraint: memberTypes attribute or simpleType children

Either thememberTypes[attribute] of the<union>elementmustbe non-empty ortheremustbe at least onesimpleType[child].

4.1.4 Simple Type Definition Validation Rules

Validation Rule: Facet Valid

A value in a·value space· is facet-valid withrespect to a·constraining facet· component if and only if:

1the value is facet-valid with respect to the particular·constraining facet· as specified below.

Validation Rule: Datatype Valid

A·literal· is datatype-valid with respect to aSimple Type Definitionif and only if it is a member of the·lexical space· of thecorresponding datatype.

Note: Since every value in the·value space· is denoted by some·literal·, and every·literal· in the·lexical space· maps tosome value, the requirement that the·literal· be in the·lexical space· entails the requirement that the value itmaps to should fulfill all of the constraints imposed by the{facets} of the datatype. Ifthe datatype is a·list·, the Datatype Valid constraint alsoentails that each whitespace-delimited token in the listbe datatype-valid against the·item type· of the list.If the datatype is a·union·, the Datatype Valid constraintentails that the·literal· be datatype-valid against atleast one of the·member types·.

That is, the constraints onSimple Type Definitions and ondatatype·derivation· defined in this specification have as aconsequence that a·literal·L is datatype-valid withrespect to aSimple Type DefinitionT if and only ifeitherT corresponds to a·special· datatype orall of the following are true:

1If there is apattern in{facets}, thenL ispattern valid (§4.3.4.4) with respect to thepattern.If there are other·lexical· facetsin{facets}, thenL is facet-valid with respectto them.

2The appropriate case among the following is true:

2.1If the{variety} ofT is·atomic·,thenL is in the·lexical space· of the{primitive type definition} ofT, as defined in theappropriate documentation. LetV be themember of the·value space· of the{primitive type definition} ofT mapped to byL,as defined in the appropriate documentation.

Note: For·built-in··primitives·, the "appropriate documentation" is the relevantsection of this specification. For·implementation-defined··primitives·,it is the normative specification of the·primitive·, whichwill typically be included in, or referred to from, theimplementation's documentation.

2.2If the{variety} ofT is·list·, theneach space-delimited substring ofL is Datatype Valid withrespect to the{item type definition} ofT. LetV be the sequence consisting of the values identified byDatatype Valid for each of those substrings, in order.

2.3If the{variety} ofT is·union·,thenL is Datatype Valid with respect to at least onemember of the{member type definitions}ofT. LetB be the·active basic member· ofT forL. LetV be the value identified by Datatype Valid forL with respect toB.

3V, as determined by theappropriate sub-clause of clause2 above,isFacet Valid (§4.1.4) with respect to each member of the{facets} ofT which is a·value-based· (and not a·pre-lexical·or·lexical·)facet.

Note thatwhiteSpace facets andother·pre-lexical· facetsdo not take part in checking DatatypeValid. In cases where this specification is used in conjunction withschema-validation of XML documents, such facets are used tonormalize infoset valuesbefore the normalized resultsare checked for datatype validity. In the case of unions the·pre-lexical· facets to use are those associated withB inclause2.3 above.When more than one·pre-lexical· facet applies, thewhiteSpace facet is applied first; the order in which·implementation-defined· facetsare applied is·implementation-defined·.

4.1.5 Constraints on Simple Type Definition Schema Components

Schema Component Constraint: Applicable Facets

The·constraining facets· which are allowed to be members of{facets}depend onthe{variety} and{primitive type definition} of the type, asfollows:

If{variety} isabsent, then no facets are applicable. (This is true foranySimpleType.)

If{variety} islist, then the applicable facets areassertions,length,minLength,maxLength,pattern,enumeration, andwhiteSpace.

If{variety} isunion, then the applicable facets arepattern,enumeration, andassertions.

If{variety} isatomic, and{primitive type definition} isabsent then no facets are applicable. (This is true foranyAtomicType.)

In all other cases ({variety} isatomic and{primitive type definition} is notabsent), then the applicable facets are shown in the table below.

{primitive type definition}	applicable{facets}
string	length,minLength,maxLength,pattern,enumeration,whiteSpace,assertions
boolean	pattern,whiteSpace,assertions
float	pattern,enumeration,whiteSpace,maxInclusive,maxExclusive,minInclusive,minExclusive,assertions
double	pattern,enumeration,whiteSpace,maxInclusive,maxExclusive,minInclusive,minExclusive,assertions
decimal	totalDigits,fractionDigits,pattern,whiteSpace,enumeration,maxInclusive,maxExclusive,minInclusive,minExclusive,assertions
duration	pattern,enumeration,whiteSpace,maxInclusive,maxExclusive,minInclusive,minExclusive,assertions
dateTime	pattern,enumeration,whiteSpace,maxInclusive,maxExclusive,minInclusive,minExclusive,assertions,explicitTimezone
time	pattern,enumeration,whiteSpace,maxInclusive,maxExclusive,minInclusive,minExclusive,assertions,explicitTimezone
date	pattern,enumeration,whiteSpace,maxInclusive,maxExclusive,minInclusive,minExclusive,assertions,explicitTimezone
gYearMonth	pattern,enumeration,whiteSpace,maxInclusive,maxExclusive,minInclusive,minExclusive,assertions,explicitTimezone
gYear	pattern,enumeration,whiteSpace,maxInclusive,maxExclusive,minInclusive,minExclusive,assertions,explicitTimezone
gMonthDay	pattern,enumeration,whiteSpace,maxInclusive,maxExclusive,minInclusive,minExclusive,assertions,explicitTimezone
gDay	pattern,enumeration,whiteSpace,maxInclusive,maxExclusive,minInclusive,minExclusive,assertions,explicitTimezone
gMonth	pattern,enumeration,whiteSpace,maxInclusive,maxExclusive,minInclusive,minExclusive,assertions,explicitTimezone
hexBinary	length,minLength,maxLength,pattern,enumeration,whiteSpace,assertions
base64Binary	length,minLength,maxLength,pattern,enumeration,whiteSpace,assertions
anyURI	length,minLength,maxLength,pattern,enumeration,whiteSpace,assertions
QName	length,minLength,maxLength,pattern,enumeration,whiteSpace,assertions
NOTATION	length,minLength,maxLength,pattern,enumeration,whiteSpace,assertions

Note: For any·implementation-defined· primitive types, it is·implementation-defined· which constraining facets areapplicable to them.

Similarly, for any·implementation-defined· constraining facets,it is·implementation-defined· which·primitives· theyapply to.

4.1.6 Built-in Simple Type Definitions

TheSimple Type Definition ofanySimpleType ispresent in every schema. It has the following properties:

Property

Value

'anySimpleType'

'http://www.w3.org/2001/XMLSchema'

The empty set

absent

The empty set

The empty set

absent

absent

absent

absent

Simple type definition ofanyAtomicType

The empty sequence

The definition ofanySimpleTypeis the root of the Simple Type Definitionhierarchy;as such it mediates between the other simple type definitions, which all eventually trace back to it via their{base type definition} properties, and the definition ofanyType, which isits{base type definition}.

TheSimple Type Definition ofanyAtomicType ispresent in every schema. It has the following properties:

Property

Value

'anyAtomicType'

'http://www.w3.org/2001/XMLSchema'

The empty set

absent

The empty set

The empty set

atomic

absent

absent

absent

Simple Type Definition corresponding to the built-in primitive datatypes

The empty sequence

Simple type definitions for all the built-in primitive datatypes,namelystring,boolean,float,double,decimal,dateTime,duration,time,date,gMonth,gMonthDay,gDay,gYear,gYearMonth,hexBinary,base64Binary,anyURI are present by definitionin every schema. All have a very similar structure, with only the{name}, the{primitive type definition} (which is self-referential), the{fundamental facets}, and in one case the{facets} varying from one to the next:

Property

Value

[as appropriate]

'http://www.w3.org/2001/XMLSchema'

anyAtomicType Definition

The empty set

{variety}

atomic

[thisSimple Type Definition itself]

{facets}

{awhiteSpace facet with{value} =collapse and{fixed} =true in all cases exceptstring, which has{value} =preserve and{fixed} =false}

{fundamental facets}

[as appropriate]

absent

absent

absent

Simple Type Definition corresponding to the built-in ordinary datatypes

The empty sequence

·Implementation-defined··primitives·must have aSimple Type Definition withthe values shown above, with the following exceptions.

The{facets} propertymust contain awhiteSpace facet, the value of which is·implementation-defined·. Itmay contain other facets,whether defined in this specification or·implementation-defined·.
The value of{fundamental facets}is·implementation-defined·.
The value of{annotations}may be empty, but need not be.

Note: It is a consequence of the rule just given that each·implementation-defined··primitive· will have anexpanded nameby which it can be referred to.

Note:·Implementation-defined· datatypes will normally have a valueother than 'http://www.w3.org/2001/XMLSchema' for the{target namespace}property. That namespace is controlled by the W3C anddatatypes will be added to it only by W3C or its designees.

Similarly,Simple Type Definitions for all the built-in·ordinary·datatypes are present by definition in every schema, with propertiesas specified inOther Built-in Datatypes (§3.4) and as representedin XML inIllustrative XML representations for the built-in ordinary type definitions (§C.2).

Property

Value

[as appropriate]

'http://www.w3.org/2001/XMLSchema'

[as specified in the appropriatesub-section ofOther Built-in Datatypes (§3.4)]

The empty set

{variety}

[atomic orlist, as specified in the appropriatesub-section ofOther Built-in Datatypes (§3.4)]

[if{variety} isatomic, then the{primitive type definition} of the{base type definition}, otherwiseabsent]

{facets}

[as specified in the appropriatesub-section ofOther Built-in Datatypes (§3.4)]

{fundamental facets}

[as specified in the appropriatesub-section ofOther Built-in Datatypes (§3.4)]

absent

if{variety} isatomic, thenabsent, otherwise as specified in the appropriatesub-section ofOther Built-in Datatypes (§3.4)]

absent

As shown in the XML representationsof the ordinary built-in datatypes inIllustrative XML representations for the built-in ordinary type definitions (§C.2)

4.2 Fundamental Facets

        4.2.1ordered
            4.2.1.1The ordered Schema Component
        4.2.2bounded
            4.2.2.1The bounded Schema Component
        4.2.3cardinality
            4.2.3.1The cardinality Schema Component
        4.2.4numeric
            4.2.4.1The numeric Schema Component

[Definition:] Eachfundamental facet is aschema component that provides a limited piece of information aboutsome aspect of each datatype. All·fundamentalfacet· components are defined in this section. For example,cardinality is a·fundamental facet·. Most·fundamental facets· are given a valuefixed with each primitive datatype's definition, and this value is not changed bysubsequent·derivations· (even whenit would perhaps be reasonable to expect an application to give a more accurate value basedon the constraining facets used to define the·derivation·). Thecardinality andbounded facetsare exceptions to this rule; their values may change as a result of certain·derivations·.

Note: Schema components are identified by kind. "Fundamental" is not a kind of component. Each kind of·fundamental facet·("ordered", "bounded", etc.) is a separate kind of schema component.

A·fundamental facet· can occur onlyin the{fundamental facets} of aSimple Type Definition, and this is theonly place where·fundamental facet· componentsoccur. Each kind of·fundamental facet·component occurs (once) in eachSimple Type Definition's{fundamental facets} set.

Note: The value of any·fundamental facet· component can alwaysbe calculated from other properties of its·owner·. Fundamental facets are not required for schema processing,but some applications use them.

4.2.1 ordered

For some datatypes,this document specifies an order relation for their value spaces (seeOrder (§2.2.3)); theordered facet reflectsthis. It takes the valuestotal,partial,andfalse, with the meanings described below.For the·primitive· datatypes, the value of theordered facet isspecified inFundamental Facets (§F.1). For·ordinary· datatypes, the value is inherited without changefrom the·base type·.For a·list·, the value is alwaysfalse;for a·union·, the value is computed as described below.

Afalse value means no order is prescribed; atotal valueassures that the prescribed order is a totalorder; apartial value means that the prescribed order is a partialorder, but not (for the primitive type in question) a total order.

Note: The valuefalse in theordered facet does notmean no partial or total orderingexists for the valuespace, only that none is specified by this document for use inchecking upper and lower bounds. Mathematically, any set of valuespossesses at least onetrivial partial ordering, in which every valuepair that is not equal is incomparable.

Note: When new datatypes are derived from datatypes with partial orders,the constraints imposed can sometimes result in a value spacefor which the ordering is total, or trivial. The value of theordered facet is not, however, changed to reflect this.The valuepartial should therefore be interpreted withappropriate caution.

[Definition:] A·value space·, and hence a datatype, is said to beordered if somemembers of the·value space· are drawn from a·primitive· datatype for which the table inFundamental Facets (§F.1) specifiesthe valuetotal orpartial for theordered facet.

Note: Some of the "real-world" datatypes which are the basis for those defined hereinare ordered in some applications, even though no order is prescribed for schema-processingpurposes. For example,boolean is sometimes ordered, andstringand·list· datatypes·constructed· fromordered·atomic· datatypes are sometimes given "lexical"orderings. They arenot ordered for schema-processing purposes.

4.2.1.1 The ordered Schema Component

Schema Component:ordered, a kind ofFundamental Facet

{value}

One of {false,partial,total}. Required.

{value} depends on the·owner's·{variety},{facets}, and{member type definitions}.The appropriatecase among the followingmust be true:

1Ifthe·owner's·{variety} isatomic,then the appropriatecase among the followingmust be true:

1.1Ifthe·owner· is·primitive·,then{value} is as specified in thetable inFundamental Facets (§F.1).

1.2otherwise{value} is the·owner's·{base type definition}'sordered {value}.

2Ifthe·owner's·{variety} islist,then{value} isfalse.

3otherwisethe·owner's·{variety} isunion;the appropriatecase among the followingmust be true:

3.1Ifevery·basic member· of the·owner·has{variety} atomic and has the same{primitive type definition},then{value} is the same as theordered component's{value} in that primitive type definition's{fundamental facets}.

3.2Ifeach member of the·owner's·{member type definitions} has anorderedcomponent in its{fundamental facets} whose{value} isfalse,then{value} isfalse.

3.3otherwise{value} ispartial.

4.2.2 bounded

Some ordered datatypes have the property thatthere is one value greater than or equal to every other value, andanother that isless than or equal to every other value. (In the case of·ordinary·datatypes, these two values arenot necessarily in the value space of the derived datatype,but they will always bein the valuespace of the primitive datatype from which they have been derived.)Thebounded facet value isboolean and isgenerallytrue for suchbounded datatypes. However, it will remainfalse when the mechanism for imposingsuch a bound is difficult to detect, as, for example, when theboundedness occurs because of derivation using apatterncomponent.

4.2.2.1 The bounded Schema Component

Schema Component:bounded, a kind ofFundamental Facet

{value}

An xs:boolean value. Required.

{value} depends on the·owner's·{variety},{facets} and{member type definitions}.

When the·owner·is·primitive·,{value} is as specified in thetable inFundamental Facets (§F.1). Otherwise, when the·owner's·{variety} isatomic,if one ofminInclusive orminExclusiveand one ofmaxInclusive ormaxExclusiveare members ofthe·owner's·{facets} set, then{value} istrue;otherwise{value} isfalse.

When the·owner's·{variety} islist,{value} isfalse.

When the·owner's·{variety} isunion, if{value} istrue for everymember of the·owner's·{member type definitions} set and all of the·owner's··basic members· have the same{primitive type definition}, then{value} istrue; otherwise{value} isfalse.

4.2.3 cardinality

Every value space has a specific number of members. This number can be characterized asfinite orinfinite. (Currently there are no datatypes with infinitevalue spaces larger thancountable.) Thecardinality facet value iseitherfinite orcountably infinite and is generallyfinite for datatypes withfinite value spaces. However, it will remaincountably infinite when the mechanism forcausing finiteness is difficult to detect, as, for example, when finiteness occurs because of aderivation using apattern component.

4.2.3.1 The cardinality Schema Component

Schema Component:cardinality, a kind ofFundamental Facet

{value}

One of {finite,countably infinite}. Required.

{value} depends on the·owner's·{variety},{facets}, and{member type definitions}.

When the·owner· is·primitive·,{value} is as specified in thetable inFundamental Facets (§F.1). Otherwise, whenthe·owner's·{variety} isatomic,{value}iscountably infinite unlessany of the followingconditions are true, in which case{value} isfinite:

the·owner's·{base type definition}'scardinality {value} isfinite,
at least one oflength,maxLength,ortotalDigits is a member of the·owner's·{facets} set,
all of the following are true:
1. one ofminInclusive orminExclusiveis a member of the·owner's·{facets} set
2. one ofmaxInclusive ormaxExclusiveis a member of the·owner's·{facets} set
3. either of the following are true:
  1. fractionDigits is a member of the·owner's·{facets} set
  2. {primitive type definition} is one ofdate,gYearMonth,gYear,gMonthDay,gDay orgMonth

When the·owner's·{variety} islist,iflength or bothminLength andmaxLengthare members of the·owner's·{facets} setand the·owner's·{item type definition}'scardinality {value} isfinitethen{value} isfinite;otherwise{value} iscountably infinite.

When the·owner's·{variety} isunion,ifcardinality's{value} isfinitefor every member of the·owner's·{member type definitions} set then{value} isfinite,otherwise{value}iscountably infinite.

4.2.4 numeric

Some value spaces are made up of things thatare conceptuallynumeric, others arenot. Thenumeric facet value indicates which areconsidered numeric.

4.2.4.1 The numeric Schema Component

Schema Component:numeric, a kind ofFundamental Facet

{value}

An xs:boolean value. Required.

{value} depends on the·owner's·{variety},{facets},{base type definition} and{member type definitions}.

When the·owner· is·primitive·,{value} is as specified in thetable inFundamental Facets (§F.1). Otherwise, when the·owner's·{variety} isatomic,{value} is inherited fromthe·owner's·{base type definition}'snumeric {value}.

When the·owner's·{variety} islist,{value} isfalse.

When the·owner's·{variety} isunion,ifnumeric's{value} istruefor every member of the·owner's·{member type definitions} set then{value} istrue,otherwise{value} isfalse.

4.3 Constraining Facets

[Definition:] Constraining facetsare schema components whose values may be set or changedduring·derivation· (subject to facet-specific controls) to control various aspects of the derived datatype. All·constraining facet· components defined by this specificationaredefined in this section. For example,whiteSpace is a·constraining facet·. ·Constraining Facets· are given a value as part ofthe·derivation·when an·ordinary· datatype is defined by·restricting·a·primitive· or·ordinary· datatype; a few·constraining facets· have default valuesthat are also provided for·primitive· datatypes.

Note: Schema components are identified by kind. "Constraining" is not a kind of component. Each kind of·constraining facet·("whiteSpace", "length", etc.) is a separate kind of schema component.

This specification distinguishes three kinds of constraining facets:

[Definition:] A constraining facet whichis used to normalize an initial·literal· before checkingto see whether the resulting character sequence is a member of a datatype's·lexical space· is apre-lexical facet.
This specification defines just one·pre-lexical· facet:whiteSpace.
[Definition:] A constraining facet whichdirectly restricts the·lexical space· of a datatype is alexical facet.
This specification defines just one·lexical· facet:pattern.
Note: As specified normatively elsewhere,·lexical· facets can have an indirecteffect on the·value space·: if every lexical representation of a valueis removed from the·lexical space·, the value itself is removedfrom the·value space·.
[Definition:] A constraining facet whichdirectly restricts the·value space· of a datatype is avalue-based facet.
Most of the constraining facets defined by this specification are·value-based· facets.
Note: As specified normatively elsewhere,·value-based· facets can have an indirecteffect on the·lexical space·: if a valueis removed from the·value space·, its lexical representationsare removedfrom the·lexical space·.

Conforming processorsmustsupport all the facets defined in this section.It is·implementation-defined· whether a processor supports otherconstraining facets.[Definition:] An·constraining facet· which is not supported bythe processor in use isunknown.

Note: A reference to an·unknown· facet might be a reference toan·implementation-defined· facet supported by some other processor,or might be the result of a typographic error, or mighthave some other explanation.

The descriptions of individual facets givenbelow include both constraints onSimple Type Definition componentsand rules for checking the datatype validity of a given literal againsta given datatype. The validation rules typically depend upon havinga full knowledge of the datatype; full knowledge of the datatype,in turn, depends on having a fully instantiatedSimple Type Definition.A full instantiation of theSimple Type Definition, and the checkingof the component constraints, require knowledge of the·base type·.It follows that if a datatype's·base type· is·unknown·, theSimple Type Definition defining the datatype will be incompletelyinstantiated, and the datatype itself will be·unknown·.Similarly, any datatype defined using an·unknown··constraining facet·will be·unknown·. It is not possible to perform datatype validationas defined here using·unknown· datatypes.

Note: The preceding paragraph does not forbid implementations from attemptingto make use of such partial information as they have about·unknown·datatypes. But the exploitation of such partial knowledge is notdatatype validity checking as defined here and is to be distinguishedfrom it in the implementation's documentation and interface.

4.3.1 length

[Definition:] length is the numberofunits of length, whereunits of lengthvaries depending on the type that is being·derived· from.The value oflengthmust be anonNegativeInteger.

Forstring and datatypes·derived· fromstring,length is measured in units ofcharacters as defined in[XML].ForanyURI,length is measured in units ofcharacters (as forstring).ForhexBinary andbase64Binary and datatypes·derived· from them,length is measured in octets (8 bits) of binary data.For datatypes·constructed· by·list·,length is measured in number of list items.

Note: Forstring and datatypes·derived· fromstring,length will not always coincide with "string length" as perceivedby some users or with the number of storage units in some digital representation. Therefore, care should be taken when specifying a value forlengthand in attempting to infer storage requirements from a given value forlength.

·length· provides for:

Constraining a·value space·to values with a specific number ofunits of length,whereunits of lengthvaries depending on{base type definition}.

Example

The following is the definition of a·user-defined·datatype to represent product codes which must beexactly 8 characters in length. By fixing the value of thelength facet we ensure that types derived from productCode canchange or set the values of other facets, such aspattern, butcannot change the length.

<simpleType name='productCode'>   <restriction base='string'>     <length value='8' fixed='true'/>   </restriction></simpleType>

4.3.1.1 The length Schema Component

Schema Component:length, a kind ofConstraining Facet

{annotations}

A sequence ofAnnotation components.

{value}

An xs:nonNegativeInteger value. Required.

{fixed}

An xs:boolean value. Required.

If{fixed} istrue, then types for whichthe current type is the{base type definition} cannot specify avalue forlength other than{value}.

Note: The{fixed} property is defined forparallelism with other facets and for compatibility with version 1.0of this specification. But it is a consequence oflength valid restriction (§4.3.1.4) that the value ofthelength facet cannot be changed, regardless ofwhether{fixed} istrue orfalse.

4.3.1.2 XML Representation of length Schema Components

The XML representation for alength schemacomponent is a<length> element information item. Thecorrespondences between the properties of the information item andproperties of the component are as follows:

XML Representation Summary:length Element Information Item

<length
  fixed =boolean : false
  id =ID
  value =nonNegativeInteger
  {any attributes with non-schema namespace . . .}>
  Content:(annotation?)
</length>

lengthSchema Component

Property

Representation

Theactual value of thevalue[attribute]

Theactual value of thefixed[attribute], if present, otherwisefalse

Theannotation mapping of the<length> element, as defined in sectionXML Representation of Annotation Schema Components of[XSD 1.1 Part 1: Structures].

4.3.1.3 length Validation Rules

Validation Rule: Length Valid

A value in a·value space· is facet-valid withrespect to·length·if and only if:

1 if the{variety} is·atomic· then

1.1if{primitive type definition} isstring oranyURI, then the length of the value,as measured incharactersmust be equal to{value};

1.2if{primitive type definition} ishexBinary orbase64Binary, then the length ofthe value, as measured in octets of the binary data,must be equal to{value};

1.3if{primitive type definition} isQName orNOTATION, then any{value} is facet-valid.

2if the{variety} is·list·,then the length of the value, as measured in list items,must be equal to{value}

The use of·length·onQName,NOTATION, and datatypes·derived· from themis deprecated. Future versions of thisspecification may remove this facet for these datatypes.

4.3.1.4 Constraints on length Schema Components

Schema Component Constraint: length and minLength or maxLength

Iflength is a member of{facets} then

1 It is an error forminLength to be a member of{facets} unless

1.1the{value} ofminLength <= the{value} oflength and

1.2there is some type definition from which this one is derived by one or more·restriction· steps in whichminLength has the same{value} andlength is not specified.

2 It is an error formaxLength to be a member of{facets} unless

2.1the{value} oflength <= the{value} ofmaxLength and

2.2there is some type definition from which this one is derived by one or more restriction steps in whichmaxLength has the same{value} andlength is not specified.

Schema Component Constraint: length valid restriction

It is an·error· iflengthis among the members of{facets} of{base type definition} and{value} isnot equal to the{value} of the parentlength.

4.3.2 minLength

[Definition:] minLength isthe minimum number ofunits of length, whereunits of length varies depending on the type that is being·derived· from.The value ofminLength must be anonNegativeInteger.

Forstring and datatypes·derived· fromstring,minLength is measured in units ofcharacters as defined in[XML].ForhexBinary andbase64Binary and datatypes·derived· from them,minLength is measured in octets (8 bits) of binary data.For datatypes·constructed· by·list·,minLength is measured in number of list items.

Note: Forstring and datatypes·derived· fromstring,minLength will not always coincide with "string length" as perceivedby some users or with the number of storage units in some digital representation.Therefore, care should be taken when specifying a value forminLengthand in attempting to infer storage requirements from a given value forminLength.

·minLength· provides for:

Constraining a·value space·to values with at least a specific number ofunits of length,whereunits of lengthvaries depending on{base type definition}.

Example

The following is the definition of a·user-defined·datatype which requires strings to have at least one character (i.e.,the empty string is not in the·value space·of this datatype).

<simpleType name='non-empty-string'>  <restriction base='string'>    <minLength value='1'/>  </restriction></simpleType>

4.3.2.1 The minLength Schema Component

Schema Component:minLength, a kind ofConstraining Facet

{annotations}

A sequence ofAnnotation components.

{value}

An xs:nonNegativeInteger value. Required.

{fixed}

An xs:boolean value. Required.

If{fixed} istrue, then types for whichthe current type is the{base type definition} cannot specify avalue forminLength other than{value}.

4.3.2.2 XML Representation of minLength Schema Component

The XML representation for aminLength schemacomponent is a<minLength> element information item. Thecorrespondences between the properties of the information item andproperties of the component are as follows:

XML Representation Summary:minLength Element Information Item

<minLength
  fixed =boolean : false
  id =ID
  value =nonNegativeInteger
  {any attributes with non-schema namespace . . .}>
  Content:(annotation?)
</minLength>

minLengthSchema Component

Property

Representation

Theactual value of thevalue[attribute]

Theactual value of thefixed[attribute], if present, otherwisefalse

Theannotation mapping of the<minLength> element, as defined in sectionXML Representation of Annotation Schema Components of[XSD 1.1 Part 1: Structures].

4.3.2.3 minLength Validation Rules

Validation Rule: minLength Valid

A value in a·value space· is facet-valid withrespect to·minLength·, determined as follows:

1 if the{variety} is·atomic· then

1.1if{primitive type definition} isstring oranyURI, then thelength of the value, as measured incharactersmust be greater than or equal to{value};

1.2if{primitive type definition} ishexBinary orbase64Binary, then thelength of the value, as measured in octets of the binary data,must be greater than or equal to{value};

1.3if{primitive type definition} isQName orNOTATION, thenany{value} is facet-valid.

2if the{variety} is·list·,then the length of the value, as measuredin list items,must be greater than or equalto{value}

The use of·minLength·onQName,NOTATION, and datatypes·derived· from themis deprecated. Future versions of thisspecification may remove this facet for these datatypes.

4.3.2.4 Constraints on minLength Schema Components

Schema Component Constraint: minLength <= maxLength

If bothminLength andmaxLengthare members of{facets}, then the{value} ofminLength must be less than or equal to the{value} ofmaxLength.

Schema Component Constraint: minLength valid restriction

It is an·error· ifminLengthis among the members of{facets} of{base type definition} and{value} isless than the{value} of the parentminLength.

4.3.3 maxLength

[Definition:] maxLength isthe maximum number ofunits of length, whereunits of length variesdepending on the type that is being·derived· from.The value ofmaxLength must be anonNegativeInteger.

Forstring and datatypes·derived· fromstring,maxLength is measured in units ofcharacters as defined in[XML].ForhexBinary andbase64Binary and datatypes·derived· from them,maxLength is measured in octets (8 bits) of binary data.For datatypes·constructed· by·list·,maxLength is measured in number of list items.

Note: Forstring and datatypes·derived· fromstring,maxLength will not always coincide with "string length" as perceivedby some users or with the number of storage units in some digital representation.Therefore, care should be taken when specifying a value formaxLengthand in attempting to infer storage requirements from a given value formaxLength.

·maxLength· provides for:

Constraining a·value space·to values with at most a specific number ofunits of length,whereunits of lengthvaries depending on{base type definition}.

Example

The following is the definition of a·user-defined·datatype which might be used to accept form input with an upper limitto the number of characters that are acceptable.

<simpleType name='form-input'>  <restriction base='string'>    <maxLength value='50'/>  </restriction></simpleType>

4.3.3.1 The maxLength Schema Component

Schema Component:maxLength, a kind ofConstraining Facet

{annotations}

A sequence ofAnnotation components.

{value}

An xs:nonNegativeInteger value. Required.

{fixed}

An xs:boolean value. Required.

If{fixed} istrue, then types for whichthe current type is the{base type definition} cannot specify avalue formaxLength other than{value}.

4.3.3.2 XML Representation of maxLength Schema Components

The XML representation for amaxLength schemacomponent is a<maxLength> element information item. Thecorrespondences between the properties of the information item andproperties of the component are as follows:

XML Representation Summary:maxLength Element Information Item

<maxLength
  fixed =boolean : false
  id =ID
  value =nonNegativeInteger
  {any attributes with non-schema namespace . . .}>
  Content:(annotation?)
</maxLength>

maxLengthSchema Component

Property

Representation

Theactual value of thevalue[attribute]

Theactual value of thefixed[attribute], if present, otherwisefalse

Theannotation mapping of the<maxLength> element, as defined in sectionXML Representation of Annotation Schema Components of[XSD 1.1 Part 1: Structures].

4.3.3.3 maxLength Validation Rules

Validation Rule: maxLength Valid

A value in a·value space· is facet-valid withrespect to·maxLength·, determined as follows:

1 if the{variety} is·atomic· then

1.1if{primitive type definition} isstring oranyURI, then thelength of the value, as measured incharactersmust be less than or equal to{value};

1.2if{primitive type definition} ishexBinary orbase64Binary, then thelength of the value, as measured in octets of the binary data,must be less than or equal to{value};

1.3if{primitive type definition} isQName orNOTATION, thenany{value} is facet-valid.

2if the{variety} is·list·,then the length of the value, as measuredin list items,must be less than or equal to{value}

The use of·maxLength·onQName,NOTATION, and datatypes·derived· from themis deprecated. Future versions of thisspecification may remove this facet for these datatypes.

4.3.3.4 Constraints on maxLength Schema Components

Schema Component Constraint: maxLength valid restriction

It is an·error· ifmaxLengthis among the members of{facets} of{base type definition} and{value} isgreater than the{value} of the parentmaxLength.

4.3.4 pattern

[Definition:] pattern is a constraint on the·value space· of a datatype which is achieved byconstraining the·lexical space· to·literals·which matcheachmember of a set of·regularexpressions·. The value ofpattern mustbe a set of·regular expressions·.

Note: An XML<restriction>containing more than one<pattern> element givesrise to a single·regular expression· in the set; this·regular expression· is an "or" ofthe·regular expressions· thatare the content of the<pattern> elements.

·pattern· provides for:

Constraining a·value space·to values that are denoted by·literals· which match each of a set of·regular expressions·.

Example

The following is the definition of a·user-defined·datatype which is a better representation of postal codes in theUnited States, by limiting strings to those which are matched bya specific·regular expression·.

<simpleType name='better-us-zipcode'>  <restriction base='string'>    <pattern value='[0-9]{5}(-[0-9]{4})?'/>  </restriction></simpleType>

4.3.4.1 The pattern Schema Component

Schema Component:pattern, a kind ofConstraining Facet

{annotations}

A sequence ofAnnotation components.

{value}

A non-empty set of·regular expressions·.

4.3.4.2 XML Representation of pattern Schema Components

The XML representation for apattern schemacomponent is one or more<pattern>element information items. Thecorrespondences between the properties of the information item andproperties of the component are as follows:

XML Representation Summary:pattern Element Information Item

<pattern
  id =ID
  value =string
  {any attributes with non-schema namespace . . .}>
  Content:(annotation?)
</pattern>

patternSchema Component

Property

Representation

[Definition:] LetR be a regularexpression given by the appropriatecase among the following:

1Ifthere is only one<pattern> among the[children] of a<restriction>,thentheactual value of itsvalue[attribute]

2otherwisethe concatenation of theactual values of all the<pattern>[children]'svalue[attributes], in order,separated by '|', so forming a single regular expression with multiple·branches·.

The value is then given by the appropriatecase among the following:

1Ifthe{base type definition} of the·owner· has apattern facet among its{facets},thenthe union of thatpattern facet's{value} and {·R·}

2otherwisejust {·R·}

Theannotation mapping of the set containing all of the<pattern> elements among the[children] of the<restriction> element information item, as defined in sectionXML Representation of Annotation Schema Components of[XSD 1.1 Part 1: Structures].

Note: The{value} property will only have more than one member when·facet-based restriction· involves apattern facet at more than one step in a type derivation. During validation, lexical forms will be checked against every member of the resulting{value}, effectively creating a conjunction of patterns.

In summary,·pattern·facets specified on thesame step in a typederivation areORed together, while·pattern·facets specified ondifferent steps of a type derivationareANDed together.

Thus, to impose two·pattern· constraints simultaneously,schema authors may either write a single·pattern· whichexpresses the intersection of the two·pattern·s they wish toimpose, or define each·pattern· on a separate type derivationstep.

4.3.4.3 Constraints on XML Representation of pattern

Schema Representation Constraint: Pattern value

Theactual value of thevalue[attribute] must be a·regular expression· asdefined inRegular Expressions (§G).

4.3.4.4 pattern Validation Rules

Validation Rule: pattern valid

A·literal· in a·lexical space· is pattern-valid (or: facet-valid withrespect to·pattern·) if and only iffor each·regular expression· in its{value},the·literal· is among the set of character sequences denoted bythe·regular expression·.

Note: As noted inDatatype (§2.1),certain uses of the·pattern· facet mayeliminate from the lexical space the canonical forms of some valuesin the value space; this can be inconvenient for applicationswhich write out the canonical form of a value and rely onbeing able to read it in again as a legal lexical form.This specification provides no recourse in such situations;applications are free to deal with it as they see fit.Caution is advised.

4.3.4.5 Constraints on pattern Schema Components

Schema Component Constraint: Valid restriction of pattern

It is an·error· if there is any member of the{value} of thepattern facet on the{base type definition}which is not also a member of the{value}.

Note: For components constructed from XML representations in schema documents, the satisfaction of this constraint is a consequence of the XML mapping rules:any pattern imposed by a simple type definitionS will always also be imposed by any type derived fromS by·facet-based restriction·.This constraint ensures that components constructed by other means(so-called "born-binary" components) similarly preservepattern facets across·facet-based restriction·.

4.3.5 enumeration

[Definition:] enumeration constrains the·value space·to a specified set of values.

enumeration does not impose an order relation on the·value space· it creates; the value of the·ordered· property of the·derived·datatype remains that of the datatype from which it is·derived·.

·enumeration· provides for:

Constraining a·value space·to a specified set of values.

Example

The following example is aSimple Type Definition for a·user-defined· datatype which limits the valuesof dates to the three US holidays enumerated. ThisSimple Type Definition would appear in a schema authored by an "end-user" andshows how to define a datatype by enumerating the values in its·value space·. The enumerated values must betype-valid·literals· for the·base type·.

<simpleType name='holidays'>    <annotation>        <documentation>some US holidays</documentation>    </annotation>    <restriction base='gMonthDay'>      <enumeration value='--01-01'>        <annotation>            <documentation>New Year's day</documentation>        </annotation>      </enumeration>      <enumeration value='--07-04'>        <annotation>            <documentation>4th of July</documentation>        </annotation>      </enumeration>      <enumeration value='--12-25'>        <annotation>            <documentation>Christmas</documentation>        </annotation>      </enumeration>    </restriction></simpleType>

4.3.5.1 The enumeration Schema Component

Schema Component:enumeration, a kind ofConstraining Facet

{annotations}

A sequence ofAnnotation components.

{value}

A set of values from the·value space· of the{base type definition}.

4.3.5.2 XML Representation of enumeration Schema Components

The XML representation for anenumeration schemacomponent is one or more<enumeration>element information items. Thecorrespondences between the properties of the information item andproperties of the component are as follows:

XML Representation Summary:enumeration Element Information Item

<enumeration
  id =ID
  value =anySimpleType
  {any attributes with non-schema namespace . . .}>
  Content:(annotation?)
</enumeration>

enumerationSchema Component

Property

Representation

The appropriatecase among the following:

1Ifthere is only one<enumeration> among the[children] of a<restriction>,thena set with one member, theactual value of itsvalue[attribute], interpreted as an instance of the{base type definition}.

2otherwisea set of theactual values of all the<enumeration>[children]'svalue[attributes], interpreted as instances of the{base type definition}.

Note: Thevalue[attribute] is declared as havingtype·anySimpleType·, but the{value} property of theenumeration facetmust be a member of the{base type definition}.So in mapping from the XML representationto theenumeration component, theactual value isidentified by using the·lexical mapping· of the{base type definition}.

A (possibly empty) sequence ofAnnotation components, one for each<annotation> among the[children] of the<enumeration>s among the[children] of a<restriction>, in order.

4.3.5.3 Constraints on XML Representation of enumeration

Schema Representation Constraint: Enumeration value

Thenormalized value of thevalue[attribute] must beDatatype Valid (§4.1.4) with respect to the{base type definition} of theSimple Type Definitioncorresponding to the nearest<simpleType> ancestorelement.

4.3.5.4 enumeration Validation Rules

Validation Rule: enumeration valid

A value in a·value space· is facet-valid withrespect to·enumeration· if and only ifthe value is equal or identicaltoone of the values specified in{value}.

Note: As specified normatively elsewhere, for purposes of checkingenumerations, no distinction is made between an atomic valueVand a list of length one containingV as its only item.

In this question, the behavior of this specification is thusthe same as the behavior specified by[XQuery 1.0 and XPath 2.0 Functions and Operators]and related specifications.

4.3.5.5 Constraints on enumeration Schema Components

Schema Component Constraint: enumeration valid restriction

It is an·error· if any member of{value} is not in the·value space·of{base type definition}.

4.3.6 whiteSpace

[Definition:] whiteSpace constrains the·value space·of types·derived· fromstring such thatthe various behaviorsspecified inAttribute Value Normalizationin[XML] are realized. The value ofwhiteSpace must be one of {preserve, replace, collapse}.

preserve

No normalization is done, the value is not changed (this is thebehavior required by[XML] for element content)

replace

All occurrences of #x9 (tab), #xA (line feed) and #xD (carriage return)are replaced with #x20 (space)

collapse

After the processing implied byreplace, contiguoussequences of #x20's are collapsed to a single #x20, and any #x20at the start or end of the string is then removed.

Note: The notation #xA used here (and elsewhere in this specification)represents the Universal Character Set (UCS) code pointhexadecimal A (line feed), which is denoted byU+000A. This notation is to be distinguished from
, which is the XMLcharacter reference to that same UCScode point.

whiteSpace is applicable to all·atomic· and·list· datatypes. For all·atomic·datatypes other thanstring (and types·derived·by·facet-based restriction· from it) the value ofwhiteSpace iscollapse and cannot be changed by a schema author; forstring the value ofwhiteSpace ispreserve; for any type·derived· by·facet-based restriction· fromstring the value ofwhiteSpace canbe any of the three legal values(as long as the value is at least as restrictive asthe value of the·base type·; seeConstraints on whiteSpace Schema Components (§4.3.6.4)). For all datatypes·constructed· by·list· thevalue ofwhiteSpace iscollapse and cannotbe changed by a schema author. For all datatypes·constructed· by·union· whiteSpace does not apply directly; however, thenormalization behavior of·union· types is controlled bythe value ofwhiteSpace on that one of the·basic members· against which the·union·is successfully validated.

Note: For more information onwhiteSpace, see thediscussion on white space normalization inSchema Component Detailsin[XSD 1.1 Part 1: Structures].

·whiteSpace· provides for:

Constraining a·value space· according tothe white space normalization rules.

Example

The following example is theSimple Type Definition forthe·built-in·tokendatatype.

<simpleType name='token'>    <restriction base='normalizedString'>      <whiteSpace value='collapse'/>    </restriction></simpleType>

Note: The values "replace" and "collapse" may appear to provide aconvenient way to "unwrap" text (i.e. undo the effects ofpretty-printing and word-wrapping). In some cases, especiallyhighly constrained data consisting of lists of artificial tokenssuch as part numbers or other identifiers, this appearance iscorrect. For natural-language data, however, the whitespaceprocessing prescribed for these values is not only unreliable butwill systematically remove the information needed to performunwrapping correctly. For Asian scripts, for example, a correctunwrapping process will replace line boundaries not with blanks butwith zero-width separators or nothing. In consequence, it isnormally unwise to use these values for natural-language data, orfor any data other than lists of highly constrained tokens.

4.3.6.1 The whiteSpace Schema Component

Schema Component:whiteSpace, a kind ofConstraining Facet

{annotations}

A sequence ofAnnotation components.

{value}

One of {preserve,replace,collapse}. Required.

{fixed}

An xs:boolean value. Required.

If{fixed} istrue, then types for whichthe current type is the{base type definition} cannot specify avalue forwhiteSpace other than{value}.

4.3.6.2 XML Representation of whiteSpace Schema Components

The XML representation for awhiteSpace schemacomponent is a<whiteSpace> element information item. Thecorrespondences between the properties of the information item andproperties of the component are as follows:

XML Representation Summary:whiteSpace Element Information Item

<whiteSpace
  fixed =boolean : false
  id =ID
  value = (collapse |preserve |replace)
  {any attributes with non-schema namespace . . .}>
  Content:(annotation?)
</whiteSpace>

whiteSpaceSchema Component

Property

Representation

Theactual value of thevalue[attribute]

Theactual value of thefixed[attribute], if present, otherwisefalse

Theannotation mapping of the<whiteSpace> element, as defined in sectionXML Representation of Annotation Schema Components of[XSD 1.1 Part 1: Structures].

4.3.6.3 whiteSpace Validation Rules

Note: There are no·Validation Rule·s associated with·whiteSpace·.For more information, see thediscussion on white space normalization inSchema Component Detailsin[XSD 1.1 Part 1: Structures], in particularthe section3.1.4 White Space Normalization during Validation.

4.3.6.4 Constraints on whiteSpace Schema Components

Schema Component Constraint: whiteSpace valid restriction

It is an·error· ifwhiteSpaceis among the members of{facets} of{base type definition} and any of the following conditions istrue:

1{value} isreplace orpreserveand the{value} of the parentwhiteSpace iscollapse

2{value} ispreserveand the{value} of the parentwhiteSpace isreplace

Note: In order of increasing restrictiveness, the legal values for thewhiteSpace facet arepreserve,collapse, andreplace. The more restrictive keywordsare more restrictive not in the senseof accepting progressively fewer instance documents butin the sense that each corresponds to a progressively smaller,more tightly restricted value space.

4.3.7 maxInclusive

[Definition:] maxInclusive is the inclusive upper bound of the·value space· for a datatype with the·ordered· property. The value ofmaxInclusive must be equal to some valuein the·value space· of the·base type·.

·maxInclusive· provides for:

Constraining a·value space· to values with aspecific inclusive upperbound.

Example

The following is the definition of a·user-defined·datatype which limits values to integers less than or equal to100, using·maxInclusive·.

<simpleType name='one-hundred-or-less'>  <restriction base='integer'>    <maxInclusive value='100'/>  </restriction></simpleType>

4.3.7.1 The maxInclusive Schema Component

Schema Component:maxInclusive, a kind ofConstraining Facet

{annotations}

A sequence ofAnnotation components.

{value}

Required.

A value from the·value space· of the{base type definition}.

{fixed}

An xs:boolean value. Required.

If{fixed} istrue, then types for whichthe current type is the{base type definition} cannot specify avalue formaxInclusive other than{value}.

4.3.7.2 XML Representation of maxInclusive Schema Components

The XML representation for amaxInclusive schemacomponent is a<maxInclusive> element information item. Thecorrespondences between the properties of the information item andproperties of the component are as follows:

XML Representation Summary:maxInclusive Element Information Item

<maxInclusive
  fixed =boolean : false
  id =ID
  value =anySimpleType
  {any attributes with non-schema namespace . . .}>
  Content:(annotation?)
</maxInclusive>

{value} must be equal to some valuein the·value space· of{base type definition}.

maxInclusiveSchema Component

Property

Representation

Theactual value of thevalue[attribute]

Theactual value of thefixed[attribute], if present, otherwisefalse

Theannotation mapping of the<maxInclusive> element, as defined in sectionXML Representation of Annotation Schema Components of[XSD 1.1 Part 1: Structures].

4.3.7.3 maxInclusive Validation Rules

Validation Rule: maxInclusive Valid

A value in an·ordered· ·value space·is facet-valid with respect to·maxInclusive·if and only if the value is less than or equal to{value}, according to thedatatype's order relation.

4.3.7.4 Constraints on maxInclusive Schema Components

Schema Component Constraint: minInclusive <= maxInclusive

It is an·error· for the value specified for·minInclusive· to be greater than the valuespecified for·maxInclusive· for the same datatype.

Schema Component Constraint: maxInclusive valid restriction

It is an·error· if any of the following conditionsis true:

1maxInclusive is among the members of{facets} of{base type definition}and{value} isgreater than the{value} of thatmaxInclusive.

2maxExclusive is among the members of{facets} of{base type definition}and{value} isgreater than or equal to the{value} ofthatmaxExclusive.

3minInclusive is among the members of{facets} of{base type definition}and{value} isless than the{value} of thatminInclusive.

4minExclusive is among the members of{facets} of{base type definition}and{value} isless than or equal to the{value} of thatminExclusive.

4.3.8 maxExclusive

[Definition:] maxExclusive is the exclusive upper bound of the·value space· for a datatype with the·ordered· property. The value ofmaxExclusive must be equal to some valuein the·value space· of the·base type· orbe equal to{value} in{base type definition}.

·maxExclusive· provides for:

Constraining a·value space· to values with aspecific exclusive upperbound.

Example

The following is the definition of a·user-defined·datatype which limits values to integers less than or equal to100, using·maxExclusive·.

<simpleType name='less-than-one-hundred-and-one'>  <restriction base='integer'>    <maxExclusive value='101'/>  </restriction></simpleType>

Note that the·value space· of this datatype is identical tothe previous one (named 'one-hundred-or-less').

4.3.8.1 The maxExclusive Schema Component

Schema Component:maxExclusive, a kind ofConstraining Facet

{annotations}

A sequence ofAnnotation components.

{value}

Required.

A value from the·value space· of the{base type definition}.

{fixed}

An xs:boolean value. Required.

If{fixed} istrue, then types for whichthe current type is the{base type definition} cannot specify avalue formaxExclusive other than{value}.

4.3.8.2 XML Representation of maxExclusive Schema Components

The XML representation for amaxExclusive schemacomponent is a<maxExclusive> element information item. Thecorrespondences between the properties of the information item andproperties of the component are as follows:

XML Representation Summary:maxExclusive Element Information Item

<maxExclusive
  fixed =boolean : false
  id =ID
  value =anySimpleType
  {any attributes with non-schema namespace . . .}>
  Content:(annotation?)
</maxExclusive>

{value} must be equal to some valuein the·value space· of{base type definition}.

maxExclusiveSchema Component

Property

Representation

Theactual value of thevalue[attribute]

Theactual value of thefixed[attribute], if present, otherwisefalse

Theannotation mapping of the<maxExclusive> element, as defined in sectionXML Representation of Annotation Schema Components of[XSD 1.1 Part 1: Structures].

4.3.8.3 maxExclusive Validation Rules

Validation Rule: maxExclusive Valid

A value in an·ordered··value space·is facet-valid with respect to·maxExclusive·if and only if the value is less than{value}, according to thedatatype's order relation.

4.3.8.4 Constraints on maxExclusive Schema Components

Schema Component Constraint: maxInclusive and maxExclusive

It is an·error· for both·maxInclusive· and·maxExclusive·to be specified in the same derivation step of aSimple Type Definition.

Schema Component Constraint: minExclusive <= maxExclusive

It is an·error· for the value specified for·minExclusive· to be greater than the valuespecified for·maxExclusive· for the same datatype.

Schema Component Constraint: maxExclusive valid restriction

It is an·error· if any of the following conditionsis true:

1maxExclusive is among the members of{facets} of{base type definition}and{value} isgreater than the{value} of thatmaxExclusive.

2maxInclusive is among the members of{facets} of{base type definition}and{value} isgreater than the{value} of thatmaxInclusive.

3minInclusive is among the members of{facets} of{base type definition}and{value} isless than or equal to the{value} of thatminInclusive.

4minExclusive is among the members of{facets} of{base type definition}and{value} isless than or equal to the{value} of thatminExclusive.

4.3.9 minExclusive

[Definition:] minExclusive is the exclusive lower bound of the·value space· for a datatype with the·ordered· property. The value ofminExclusive must be equal to some valuein the·value space· of the·base type· orbe equal to{value} in{base type definition}.

·minExclusive· provides for:

Constraining a·value space· to values with aspecific exclusive lower bound.

Example

The following is the definition of a·user-defined·datatype which limits values to integers greater than or equal to100, using·minExclusive·.

<simpleType name='more-than-ninety-nine'>  <restriction base='integer'>    <minExclusive value='99'/>  </restriction></simpleType>

Note that the·value space· of this datatype is identical to the followingone (named 'one-hundred-or-more').

4.3.9.1 The minExclusive Schema Component

Schema Component:minExclusive, a kind ofConstraining Facet

{annotations}

A sequence ofAnnotation components.

{value}

Required.

A value from the·value space· of the{base type definition}.

{fixed}

An xs:boolean value. Required.

If{fixed} istrue, then types for whichthe current type is the{base type definition} cannot specify avalue forminExclusive other than{value}.

4.3.9.2 XML Representation of minExclusive Schema Components

The XML representation for aminExclusive schemacomponent is a<minExclusive> element information item. Thecorrespondences between the properties of the information item andproperties of the component are as follows:

XML Representation Summary:minExclusive Element Information Item

<minExclusive
  fixed =boolean : false
  id =ID
  value =anySimpleType
  {any attributes with non-schema namespace . . .}>
  Content:(annotation?)
</minExclusive>

{value} must be equal to some valuein the·value space· of{base type definition}.

minExclusiveSchema Component

Property

Representation

Theactual value of thevalue[attribute]

Theactual value of thefixed[attribute], if present, otherwisefalse

Theannotation mapping of the<minExclusive> element, as defined in sectionXML Representation of Annotation Schema Components of[XSD 1.1 Part 1: Structures].

4.3.9.3 minExclusive Validation Rules

Validation Rule: minExclusive Valid

A value in an·ordered· ·value space·is facet-valid with respect to·minExclusive· if and only ifthe value is greater than{value}, according to thedatatype's order relation.

4.3.9.4 Constraints on minExclusive Schema Components

Schema Component Constraint: minInclusive and minExclusive

It is an·error· for both·minInclusive· and·minExclusive· to be specified in the same derivation step of aSimple Type Definition.

Schema Component Constraint: minExclusive < maxInclusive

It is an·error· for the value specified for·minExclusive· to be greater than or equal to the valuespecified for·maxInclusive· for the same datatype.

Schema Component Constraint: minExclusive valid restriction

It is an·error· if any of the following conditions is true:

1minExclusive is among the members of{facets} of{base type definition}and{value} isless than the{value} of thatminExclusive.

2minInclusive is among the members of{facets} of{base type definition}and{value} isless than the{value} of thatminInclusive.

3maxInclusive is among the members of{facets} of{base type definition} and{value} isgreater than or equal to the{value} of thatmaxInclusive.

4maxExclusive is among the members of{facets} of{base type definition}and{value} isgreater than or equal to the{value} of thatmaxExclusive.

4.3.10 minInclusive

[Definition:] minInclusive is the inclusive lower bound of the·value space· for a datatype with the·ordered· property. The value ofminInclusive must be equal to some value in the·value space· of the·base type·.

·minInclusive· provides for:

Constraining a·value space· to values with aspecific inclusive lowerbound.

Example

The following is the definition of a·user-defined·datatype which limits values to integers greater than or equal to100, using·minInclusive·.

<simpleType name='one-hundred-or-more'>  <restriction base='integer'>    <minInclusive value='100'/>  </restriction></simpleType>

4.3.10.1 The minInclusive Schema Component

Schema Component:minInclusive, a kind ofConstraining Facet

{annotations}

A sequence ofAnnotation components.

{value}

Required.

A value from the·value space· of the{base type definition}.

{fixed}

An xs:boolean value. Required.

If{fixed} istrue, then types for whichthe current type is the{base type definition} cannot specify avalue forminInclusive other than{value}.

4.3.10.2 XML Representation of minInclusive Schema Components

The XML representation for aminInclusive schemacomponent is a<minInclusive> element information item. Thecorrespondences between the properties of the information item andproperties of the component are as follows:

XML Representation Summary:minInclusive Element Information Item

<minInclusive
  fixed =boolean : false
  id =ID
  value =anySimpleType
  {any attributes with non-schema namespace . . .}>
  Content:(annotation?)
</minInclusive>

{value} must be equal to some value in the·value space· of{base type definition}.

minInclusiveSchema Component

Property

Representation

Theactual value of thevalue[attribute]

Theactual value of thefixed[attribute], if present, otherwisefalse

Theannotation mapping of the<minInclusive> element, as defined in sectionXML Representation of Annotation Schema Components of[XSD 1.1 Part 1: Structures].

4.3.10.3 minInclusive Validation Rules

Validation Rule: minInclusive Valid

A value in an·ordered· ·value space·is facet-valid with respect to·minInclusive· if and only ifthe value is greater than or equal to{value}, according to thedatatype's order relation.

4.3.10.4 Constraints on minInclusive Schema Components

Schema Component Constraint: minInclusive < maxExclusive

It is an·error· for the value specified for·minInclusive· to be greater than or equal to the valuespecified for·maxExclusive· for the same datatype.

Schema Component Constraint: minInclusive valid restriction

It is an·error· if any of the following conditionsis true:

1minInclusive is among the members of{facets} of{base type definition}and{value} isless than the{value} ofthatminInclusive.

2maxInclusive is among the members of{facets} of{base type definition}and{value} isgreater the{value} of thatmaxInclusive.

3minExclusive is among the members of{facets} of{base type definition}and{value} isless than or equal to the{value} of thatminExclusive.

4maxExclusive is among the members of{facets} of{base type definition}and{value} isgreater than or equal to the{value} of thatmaxExclusive.

4.3.11 totalDigits

[Definition:] totalDigits restricts the magnitude and arithmetic precision of values in the·value spaces· ofdecimal and datatypes derived from it.

Fordecimal,if the{value} oftotalDigits ist, the effect is to require that values be equal toi / 10ⁿ, for someintegersi andn, with | i | < 10^tand0 ≤ n ≤ t.This has as a consequence that the values are expressibleusing at mostt digits in decimal notation.

The{value} oftotalDigitsmust beapositiveInteger.

The term 'totalDigits' is chosen to reflect the fact thatit restricts the·value space· to those values thatcan be represented lexically using at mosttotalDigits digits indecimal notation, or at mosttotalDigits digitsfor the coefficient, in scientific notation. Note that it does not restrictthe·lexical space· directly; a lexicalrepresentation that adds non-significantleading or trailing zero digits is still permitted.It also has no effect on the values NaN, INF, and -INF.

4.3.11.1 The totalDigits Schema Component

Schema Component:totalDigits, a kind ofConstraining Facet

{annotations}

A sequence ofAnnotation components.

{value}

An xs:positiveInteger value. Required.

{fixed}

An xs:boolean value. Required.

If{fixed} istrue, then types for whichthe current type is the{base type definition}must not specify avalue fortotalDigits other than{value}.

4.3.11.2 XML Representation of totalDigits Schema Components

The XML representation for atotalDigits schemacomponent is a<totalDigits> element information item. Thecorrespondences between the properties of the information item andproperties of the component are as follows:

XML Representation Summary:totalDigits Element Information Item

<totalDigits
  fixed =boolean : false
  id =ID
  value =positiveInteger
  {any attributes with non-schema namespace . . .}>
  Content:(annotation?)
</totalDigits>

totalDigitsSchema Component

Property

Representation

Theactual value of thevalue[attribute]

Theactual value of thefixed[attribute], if present, otherwisefalse

Theannotation mapping of the<totalDigits> element, as defined in sectionXML Representation of Annotation Schema Components of[XSD 1.1 Part 1: Structures].

4.3.11.3 totalDigits Validation Rules

Validation Rule: totalDigits Valid

A valuevis facet-valid with respect to atotalDigits facet with a{value} oft if and only ifv is adecimal value equal toi / 10ⁿ, for someintegersi andn, with | i | < 10^tand0 ≤ n ≤ t.

4.3.11.4 Constraints on totalDigits Schema Components

Schema Component Constraint: totalDigits valid restriction

It is an·error· if the·owner·'s{base type definition}has atotalDigits facet among its{facets}and{value} isgreater than the{value} ofthattotalDigits facet.

4.3.12 fractionDigits

[Definition:] fractionDigitsplaces an upper limit on the arithmetic precision ofdecimal values: if the{value} offractionDigits =f, then the value space isrestricted to values equal toi / 10ⁿ for some integersi andn and 0 ≤n ≤f.The value offractionDigits must be anonNegativeInteger

The termfractionDigits is chosen to reflect the fact that it restricts the·value space· to those values that can be represented lexically in decimal notation using at mostfractionDigits to the right of the decimal point. Note that it does not restrict the·lexical space· directly; a lexical representation that adds non-significantleading or trailing zero digits is still permitted.

Example

The following is the definition of a·user-defined·datatype which could be used to represent the magnitudeof a person's body temperature on the Celsius scale.This definition would appear in a schema authored by an "end-user"and shows how to define a datatype by specifying facet values whichconstrain the range of the·base type·.

<simpleType name='celsiusBodyTemp'>  <restriction base='decimal'>    <fractionDigits value='1'/>    <minInclusive value='32'/> <maxInclusive value='41.7'/>  </restriction></simpleType>

4.3.12.1 The fractionDigits Schema Component

Schema Component:fractionDigits, a kind ofConstraining Facet

{annotations}

A sequence ofAnnotation components.

{value}

An xs:nonNegativeInteger value. Required.

{fixed}

An xs:boolean value. Required.

If{fixed} istrue, thentypes for which the current type is the{base type definition}must notspecify a value forfractionDigits otherthan{value}.

4.3.12.2 XML Representation of fractionDigits Schema Components

The XML representation for afractionDigits schemacomponent is a<fractionDigits> element information item. Thecorrespondences between the properties of the information item andproperties of the component are as follows:

XML Representation Summary:fractionDigits Element Information Item

<fractionDigits
  fixed =boolean : false
  id =ID
  value =nonNegativeInteger
  {any attributes with non-schema namespace . . .}>
  Content:(annotation?)
</fractionDigits>

fractionDigitsSchema Component

Property

Representation

Theactual value of thevalue[attribute]

Theactual value of thefixed[attribute], if present, otherwisefalse

Theannotation mapping of the<fractionDigits> element, as defined in sectionXML Representation of Annotation Schema Components of[XSD 1.1 Part 1: Structures].

4.3.12.3 fractionDigits Validation Rules

Validation Rule: fractionDigits Valid

A value is facet-valid withrespect to·fractionDigits· if and only ifthat value is equal toi / 10ⁿ for integeri andn, with 0 ≤n ≤{value}.

4.3.12.4 Constraints on fractionDigits Schema Components

Schema Component Constraint: fractionDigits less than or equal to totalDigits

It is an·error· for the{value} offractionDigitsto be greater thanthat oftotalDigits.

Schema Component Constraint: fractionDigits valid restriction

It is an·error· if·fractionDigits· is among the members of{facets} of{base type definition} and{value} is greater than the{value} of that·fractionDigits·.

4.3.13 Assertions

[Definition:] Assertions constrain the·value space· by requiring the values to satisfy specified XPath ([XPath 2.0]) expressions. The value of theassertions facet is a sequence ofAssertion components as defined in[XSD 1.1 Part 1: Structures].

Example

The following is the definition of a·user-defined· datatype which allows all integers but 0 by using an assertion to disallow the value 0.

<simpleType name='nonZeroInteger'>  <restriction base='integer'>    <assertion test='$value ne 0'/>  </restriction></simpleType>

Example

The following example defines the datatype "triple", whose·value space· is the set of integers evenly divisible by three.

<simpleType name='triple'>  <restriction base='integer'>    <assertion test='$value mod 3 eq 0'/>  </restriction></simpleType>

The same datatype can be defined without the use of assertions, but the pattern necessary to represent the set of triples is long and error-prone:

<simpleType name='triple'>  <restriction base='integer'>    <pattern value=    "([0369]|[147][0369]*[258]|(([258]|[147][0369]*[147])([0369]|[258][0369]*[147])*([147]|[258][0369]*[258]))*"/>  </restriction></simpleType>

The assertion used in the first version of "triple" is likely to be clearer for many readers of the schema document.

4.3.13.1 The assertions Schema Component

Schema Component:assertions, a kind ofConstraining Facet

{annotations}

A sequence ofAnnotation components.

{value}

A sequence ofAssertion components.

4.3.13.2 XML Representation of assertions Schema Components

The XML representation for anassertions schema component is one or more<assertion> element information items. The correspondences between the properties of the information item and properties of the component are as follows:

XML Representation Summary:assertion Element Information Item

<assertion
  id =ID
  test =an XPath expression
  xpathDefaultNamespace = (anyURI | (##defaultNamespace |##targetNamespace |##local))
  {any attributes with non-schema namespace . . .}>
  Content:(annotation?)
</assertion>

assertionsSchema Component

Property

Representation

A sequence whose members areAssertions drawn from the following sources, in order:

1If the{base type definition} of the·owner· has anassertions facet among its{facets}, then theAssertions which appear in the{value} of thatassertions facet.

2Assertions corresponding to the<assertion> element information items among the[children] of<restriction>, if any, in document order. For details of the construction of theAssertion components, seesection 3.13.2 of[XSD 1.1 Part 1: Structures].

The empty sequence.

Note: Annotations specified within an<assertion> element are captured by the individualAssertion component to which it maps.

4.3.13.3 Assertions Validation Rules

The following rule refers to"the nearest built-in" datatypeand to the "XDM representation" of a valueunder a datatype.[Definition:] Forany datatypeT, thenearest built-in datatype toT is the first·built-in· datatype encountered in followingthe chain of links connecting each datatype to its·base type·. IfT is a·built-in· datatype, then thenearest built-in datatype ofT isT itself; otherwise,it is the nearest built-in datatype ofT's·base type·.

[Definition:] For any valueV and any datatypeT, theXDM representation ofV underT is defined recursively as follows. Call the XDM representationX. Then

1IfT =·xs:anySimpleType· or·xs:anyAtomicType· thenX isV,and thedynamictype ofX isxs:untypedAtomic.

2IfT .{variety} =atomic,then letT2 be the·nearest built-in datatype· toT.IfV is a member of the·value space· ofT2, thenX isV and thedynamic typeofX isT2.Otherwise (i.e. ifV is not a member of the·value space· ofT2),X is the·XDM representation· ofV underT2 .{base type definition}.

3IfT .{variety} =list,thenX is a sequence of atomic values, each atomic value being the·XDM representation· of the correspondingitem in the listV underT .{item type definition}.

4IfT .{variety} =union,thenX is the·XDM representation· ofVunder the·active basic member· ofVwhen validated againstT.If there is no·active basic member·,thenV has no·XDM representation· underT.

Note: If the{item type definition} of a·list· is a·union·, or the·active basic member· isa·list·, then several steps may be necessary before the·atomic·datatype which serves as thedynamictype ofX is found.

Because the{item type definition}of a·list· is required to be an·atomic· or·union· datatype,and the·active basic member· of a·union· which accepts the valueV is by definition not a·union·, the recursive rule given above is guaranteed toterminate in a sequence of one or more·atomic· values,each belonging to an·atomic· datatype.

Validation Rule: Assertions Valid

A valueV is facet-valid with respect to anassertions facet belonging to a simple typeTif and only if the {test}property of eachAssertion in its{value}evaluates totrue under theconditions laid out below, without raising anydynamic error ortype error.

Evaluation of {test} is performed as defined in[XPath 2.0], with the following conditions:

1 The XPath expression {test} is evaluated, following the rules given inXPath Evaluation of[XSD 1.1 Part 1: Structures], with the following modifications.

1.1 Thein-scope variables in thestatic context is a set with a single member. Theexpanded QName of that member has no namespace URI and has 'value' as the local name. The (static)type of the member isanyAtomicType*.

Note: The XDM type labelanyAtomicType* simply says that for static typing purposes the variable$value will have a value consisting of a sequence of zero or more atomic values.

1.2There is nocontext item for the evaluation of the XPath expression.

Note: In the terminology of[XPath 2.0], thecontext item is "undefined".

Note: As a consequence the expression '.', or any implicit or explicit reference to the context item, will raise a dynamic error, which will cause the assertion to be treated as false. If an error is detected statically, then the assertion violates the schema component constraintXPath Valid and causes an error to be flagged in the schema.

The variable "$value" can be used to refer to the value being checked.

1.3There is likewise no value for thecontext size and thecontext position in thedynamic context used for evaluation of the assertion.

1.4 Thevariable values in thedynamic context is a set with a single member. Theexpanded QName of that member has no namespace URI and 'value' as the local name. Thevalue of the member is the·XDM representation· ofV underT.

1.5IfV has no·XDM representation· underT, then the XPath expression cannot usefully be evaluated, andV is not facet-valid against theassertions facet ofT.

2The evaluation result is converted to eithertrue orfalse as if by a call to the XPathfn:boolean function.

4.3.13.4 Constraints on assertions Schema Components

Schema Component Constraint: Valid restriction of assertions

The{value} of theassertions facet on the{base type definition}must be a prefix of the{value}.

Note: For components constructed from XML representations in schema documents, the satisfaction of this constraint is a consequence of the XML mapping rules: any assertion imposed by a simple type definitionS will always also be imposed by any type derived fromS by·facet-based restriction·. This constraint ensures that components constructed by other means (so-called "born-binary" components) similarly preserveassertions facets across·facet-based restriction·.

4.3.14 explicitTimezone

[Definition:] explicitTimezone is a three-valued facet which can can be used to require or prohibit the time zone offset in date/time datatypes.

Example

The following·user-defined· datatype accepts onlydate values without a time zone offset,using theexplicitTimezone facet.

<simpleType name='bare-date'>  <restriction base='date'>    <explicitTimezone value='prohibited'/>  </restriction></simpleType>

The same effect could also be achieved using thepattern facet, as shown below,but it is somewhat less clear what is going on in this derivation, and it is better practice to usethe more straightforwardexplicitTimezone for this purpose.

<simpleType name='bare-date'>  <restriction base='date'>    <pattern value='[^:Z]*'/>  </restriction></simpleType>

4.3.14.1 The explicitTimezone Schema Component

Schema Component:explicitTimezone, a kind ofConstraining Facet

{annotations}

A sequence ofAnnotation components.

{value}

One of {required,prohibited,optional}. Required.

{fixed}

An xs:boolean value. Required.

If{fixed} istrue, then datatypes for whichthe current type is the{base type definition} cannot specify avalue forexplicitTimezone other than{value}.

Note: It is a consequence oftimezone valid restriction (§4.3.14.4) that the value oftheexplicitTimezone facet cannot be changed unless thatvalue isoptional, regardless ofwhether{fixed} istrue orfalse. Accordingly,{fixed} is relevant only when{value} isoptional.

4.3.14.2 XML Representation of explicitTimezone Schema Components

The XML representation for anexplicitTimezone schemacomponent is an<explicitTimezone> element information item. Thecorrespondences between the properties of the information item andproperties of the component are as follows:

XML Representation Summary:explicitTimezone Element Information Item

<explicitTimezone
  fixed =boolean : false
  id =ID
  value =NCName
  {any attributes with non-schema namespace . . .}>
  Content:(annotation?)
</explicitTimezone>

explicitTimezoneSchema Component

Property

Representation

Theactual value of thevalue[attribute]

Theactual value of thefixed[attribute], if present, otherwisefalse