XML Schema Part 2: Datatypes Second Edition

XML Schema Part 2: Datatypes Second EditionW3C Recommendation 28 October 2004W3C Recommendation 2 May 2001, Second Edition 28 October 2004*--This version:http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/ Latest version:http://www.w3.org/TR/xmlschema-2/ Previous version:http://www.w3.org/TR/2004/PER-xmlschema-2-20040318/ Editors:Paul V. Biron, Kaiser Permanente, for Health Level Seven <Paul.V.Biron@kp.org>Ashok Malhotra, Microsoft (formerly of IBM) <ashokma@microsoft.com> Please refer to the errata for this document, which may include some normative corrections.

This document is also available in these non-normative formats: XML, XHTML with visible change markup, Independent copy of the schema for schema documents, A schema for built-in datatypes only, in a separate namespace, and Independent copy of the DTD for schema documents. See also translations.

rules apply.

AbstractXML Schema: Datatypes is part 2 of the specification of the XML Schema language. It defines facilities for defining datatypes to be used in XML Schemas as well as other XML specifications. The datatype language, which is itself represented in XML 1.0, provides a superset of the capabilities found in XML 1.0 document type definitions (DTDs) for specifying datatypes on elements and attributes.

Status of this DocumentThis section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.

This is a W3C Recommendation, which forms part of the Second Edition of XML Schema. This document has been reviewed by W3C Members and other interested parties and has been endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited as a normative reference from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web.

This document has been produced by the W3C XML Schema Working Group as part of the W3C XML Activity. The goals of the XML Schema language are discussed in the XML Schema Requirements document. The authors of this document are the members of the XML Schema Working Group. Different parts of this specification have different editors.

This document was produced under the 24 January 2002 Current Patent Practice (CPP) as amended by the W3C Patent Policy Transition Procedure. The Working Group maintains a public list of patent disclosures relevant to this document; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) with respect to this specification should disclose the information in accordance with section 6 of the W3C Patent Policy.

The English version of this specification is the only normative version. Information about translations of this document is available at http://www.w3.org/2001/05/xmlschema-translations.

This second edition is not a new version, it merely incorporates the changes dictated by the corrections to errors found in the first edition as agreed by the XML Schema Working Group, as a convenience to readers. A separate list of all such corrections is available at http://www.w3.org/2001/05/xmlschema-errata.

The errata list for this second edition is available at http://www.w3.org/2004/03/xmlschema-errata.

Please report errors in this document to www-xml-schema-comments@w3.org (archive).

Note: Ashok Malhotra's affiliation has changed since the completion of editorial work on this second edition. He is now at Oracle, and can be contacted at <ashok.malhotra@oracle.com>. Table of Contents

1.1 Purpose

1.2 Requirements

1.3 Scope

1.4 Terminology

1.5 Constraints and Contributions

2 Type System

2.1 Datatype

2.2 Value space

2.3 Lexical space

2.4 Facets

2.5 Datatype dichotomies

3 Built-in datatypes

3.1 Namespace considerations

3.2 Primitive datatypes

3.3 Derived datatypes

4 Datatype components

4.1 Simple Type Definition

4.2 Fundamental Facets

4.3 Constraining Facets

5 Conformance

Appendices

B DTD for Datatype Definitions (non-normative)

C Datatypes and Facets

C.1 Fundamental Facets

D ISO 8601 Date and Time Formats

D.1 ISO 8601 Conventions

D.2 Truncated and Reduced Formats

D.3 Deviations from ISO 8601 Formats

E Adding durations to dateTimes

E.1 Algorithm

E.2 Commutativity and Associativity

F Regular Expressions

F.1 Character Classes

G Glossary (non-normative)

H References

H.1 Normative

H.2 Non-normative

I Acknowledgements (non-normative)

1 Introduction1.1 PurposeThe [XML 1.0 (Second Edition)] specification defines limited facilities for applying datatypes to document content in that documents may contain or refer to DTDs that assign types to elements and attributes. However, document authors, including authors of traditional documents and those transporting data in XML, often require a higher degree of type checking to ensure robustness in document understanding and data interchange.

The table below offers two typical examples of XML instances in which datatypes are implicit: the instance on the left represents a billing invoice, the instance on the right a memo or perhaps an email message in XML.

Data orientedDocument oriented<invoice> <orderDate>1999-01-21</orderDate> <shipDate>1999-01-25</shipDate> <billingAddress> <name>Ashok Malhotra</name> <street>123 Microsoft Ave.</street> <city>Hawthorne</city> <state>NY</state> <zip>10532-0000</zip> </billingAddress> <voice>555-1234</voice> <fax>555-4321</fax></invoice>

<memo importance='high' date='1999-03-23'> <from>Paul V. Biron</from> <to>Ashok Malhotra</to> <subject>Latest draft</subject> <body> We need to discuss the latest draft <emph>immediately</emph>. Either email me at <email> mailto:paul.v.biron@kp.org</email> or call <phone>555-9876</phone> </body></memo>

The invoice contains several dates and telephone numbers, the postal abbreviation for a state (which comes from an enumerated list of sanctioned values), and a ZIP code (which takes a definable regular form). The memo contains many of the same types of information: a date, telephone number, email address and an "importance" value (from an enumerated list, such as "low", "medium" or "high"). Applications which process invoices and memos need to raise exceptions if something that was supposed to be a date or telephone number does not conform to the rules for valid dates or telephone numbers.

In both cases, validity constraints exist on the content of the instances that are not expressible in XML DTDs. The limited datatyping facilities in XML have prevented validating XML processors from supplying the rigorous type checking required in these situations. The result has been that individual applications writers have had to implement type checking in an ad hoc manner. This specification addresses the need of both document authors and applications writers for a robust, extensible datatype system for XML which could be incorporated into XML processors. As discussed below, these datatypes could be used in other XML-related standards as well.

1.2 RequirementsThe [XML Schema Requirements] document spells out concrete requirements to be fulfilled by this specification, which state that the XML Schema Language must:

define a type system that is adequate for import/export from database systems (e.g., relational, object, OLAP); distinguish requirements relating to lexical data representation vs. those governing an underlying information set; allow creation of user-defined datatypes, such as datatypes that are derived from existing datatypes and which may constrain certain of its properties (e.g., range, precision, length, format).

1.3 ScopeThis portion of the XML Schema Language discusses datatypes that can be used in an XML Schema. These datatypes can be specified for element content that would be specified as #PCDATA and attribute values of various types in a DTD. It is the intention of this specification that it be usable outside of the context of XML Schemas for a wide range of other XML-related activities such as [XSL] and [RDF Schema].

1.4 TerminologyThe terminology used to describe XML Schema Datatypes is defined in the body of this specification. The terms defined in the following list are used in building those definitions and in describing the actions of a datatype processor:

A feature of this specification included solely to ensure that schemas which use this feature remain compatible with [XML 1.0 (Second Edition)] Conforming documents and processors are permitted to but need not behave as described. (Of strings or names:) Two strings or names being compared must be identical. Characters with multiple possible representations in ISO/IEC 10646 (e.g. characters with both precomposed and base+diacritic forms) match only if they have the same representation in both strings. No case folding is performed. (Of strings and rules in the grammar:) A string matches a grammatical production if it belongs to the language generated by that production. Conforming documents and processors are required to behave as described; otherwise they are in A violation of the rules of this specification; results are undefined. Conforming software error and 1.5 Constraints and ContributionsThis specification provides three different kinds of normative statements about schema components, their representations in XML and their contribution to the schema-validation of information items:

Constraint on Schemas Constraints on the schema components themselves, i.e. conditions components Schema Representation Constraint Constraints on the representation of schema components in XML. Some but not all of these are expressed in Schema for Datatype Definitions (normative) (§A) and DTD for Datatype Definitions (non-normative) (§B). Validation Rule Constraints expressed by schema components which information items 2 Type SystemThis section describes the conceptual framework behind the type system defined in this specification. The framework has been influenced by the [ISO 11404] standard on language-independent datatypes as well as the datatypes for [SQL] and for programming languages such as Java.

The datatypes discussed in this specification are computer representations of well known abstract concepts such as integer and date. It is not the place of this specification to define these abstract concepts; many other publications provide excellent definitions.

2.1 Datatypedatatype is a 3-tuple, consisting of a) a set of distinct values, called its

2.2 Value spacevalue space is the set of values for a given datatype. Each value in the value space of a datatype is denoted by one or more literals in its

The

defined axiomatically from fundamental notions (intensional definition) [see enumerated outright (extensional definition) [see defined by restricting the defined as a combination of values from one or more already defined

equality and might be

2.3 Lexical spaceIn addition to its

lexical space is the set of valid literals for a datatype.

For example, "100" and "1.0E2" are two different literals from the

Note: The literals in the The number of literals for each value has been kept small; for many datatypes there is a one-to-one mapping between literals and values. This makes it easy to exchange the values between different systems. In many cases, conversion from locale-dependent representations will be required on both the originator and the recipient side, both for computer processing and for interaction with humans. Textual, rather than binary, literals are used. This makes hand editing, debugging, and similar activities possible. Where possible, literals correspond to those found in common programming languages and libraries. 2.3.1 Canonical Lexical RepresentationWhile the datatypes defined in this specification have, for the most part, a single lexical representation i.e. each value in the datatype's

canonical lexical representation is a set of literals from among the valid set of literals for a datatype such that there is a one-to-one mapping between literals in the canonical lexical representation and values in the

2.4 Facets 2.4.1 Fundamental facets

2.4.2 Constraining or Non-fundamental facets

facet is a single defining aspect of a

The facets of a datatype serve to distinguish those aspects of one datatype which differ from other datatypes. Rather than being defined solely in terms of a prose description the datatypes in this specification are defined in terms of the synthesis of facet values which together determine the

Facets are of two types: fundamental facets that define the datatype and non-fundamental or constraining facets that constrain the permitted values of a datatype.

2.4.1 Fundamental facetsfundamental facet is an abstract property which serves to semantically characterize the values in a

All fundamental facets are fully described in Fundamental Facets (§4.2).

2.4.2 Constraining or Non-fundamental facetsconstraining facet is an optional property that can be applied to a datatype to constrain its

Constraining the

All constraining facets are fully described in Constraining Facets (§4.3).

2.5 Datatype dichotomies 2.5.1 Atomic vs. list vs. union datatypes

2.5.2 Primitive vs. derived datatypes

2.5.3 Built-in vs. user-derived datatypes

It is useful to categorize the datatypes defined in this specification along various dimensions, forming a set of characterization dichotomies.

2.5.1 Atomic vs. list vs. union datatypesThe first distinction to be made is that between

For example, a single token which

2.5.1.1 Atomic datatypesliterals whose internal structure is specific to the datatype in question.

2.5.1.2 List datatypesSeveral type systems (such as the one described in [ISO 11404]) treat

itemType of that

Example<simpleType name='sizes'> <list itemType='decimal'/></simpleType>

Example<simpleType name='listOfString'> <list itemType='string'/></simpleType>

In the above example, the value of the someElement element is not a When a datatype is

unit of length is measured in number of list items. The value of collapse.

For

Example<xs:simpleType name='myList'><xs:list itemType='xs:integer'/></xs:simpleType><xs:simpleType name='myRestrictedList'><xs:restriction base='myList'><xs:pattern value='123 (\d+\s)*456'/></xs:restriction></xs:simpleType><someElement xsi:type='myRestrictedList'>123 456</someElement><someElement xsi:type='myRestrictedList'>123 987 456</someElement><someElement xsi:type='myRestrictedList'>123 987 567 456</someElement>

The canonical-lexical-representation for the

2.5.1.3 Union datatypesThe

ExampleA prototypical example of a <attributeGroup name="occurs"> <attribute name="minOccurs" type="nonNegativeInteger" use="optional" default="1"/> <attribute name="maxOccurs"use="optional" default="1"> <simpleType> <union> <simpleType> <restriction base='nonNegativeInteger'/> </simpleType> <simpleType> <restriction base='string'> <enumeration value='unbounded'/> </restriction> </simpleType> </union> </simpleType> </attribute> </attributeGroup>

Any number (greater than 1) of

memberTypes of that

The order in which the memberTypes attribute) is significant. During validation, an element or attribute's value is validated against the

ExampleFor example, given the definition below, the first instance of the <size> element validates correctly as an integer (§3.3.13), the second and third as string (§3.2.1). <xsd:element name='size'> <xsd:simpleType> <xsd:union> <xsd:simpleType> <xsd:restriction base='integer'/> </xsd:simpleType> <xsd:simpleType> <xsd:restriction base='string'/> </xsd:simpleType> </xsd:union> </xsd:simpleType> </xsd:element>

<size>1</size> <size>large</size> <size xsi:type='xsd:string'>1</size>

The canonical-lexical-representation for a 2.5.2 Primitive vs. derived datatypesNext, we distinguish between

ab initio. For example, in this specification, float is a well-defined mathematical concept that cannot be defined in terms of other datatypes, while a integer is a special case of the more general datatype decimal.

anySimpleType in the XML Schema namespace. anySimpleType can be considered as the anySimpleType is considered to have an unconstrained lexical space and a

The datatypes defined by this specification fall into both the

In the example above, integer is

Note: A datatype which is As described in more detail in XML Representation of Simple Type Definition Schema Components (§4.1.2), each restrict the

2.5.2.1 Derived by restrictionrestriction from another datatype when values for zero or more

restriction is defined in terms of an existing datatype, referred to as its base type. base types can be either

2.5.2.2 Derived by listA

2.5.2.3 Derived by unionOne datatype can be

2.5.3 Built-in vs. user-derived datatypesUser-derived datatypes are those Conceptually there is no difference between the

Note: A datatype which is 3 Built-in datatypes

Each built-in datatype in this specification (both

the fragment identifier is the name of the datatypeFor example, to address the int datatype, the URI is:

http://www.w3.org/2001/XMLSchema#intAdditionally, each facet definition element can be uniquely addressed via a URI constructed as follows:

the fragment identifier is the name of the facetFor example, to address the maxInclusive facet, the URI is:

http://www.w3.org/2001/XMLSchema#maxInclusiveAdditionally, each facet usage in a built-in datatype definition can be uniquely addressed via a URI constructed as follows:

the fragment identifier is the name of the datatype, followed by a period (".") followed by the name of the facetFor example, to address the usage of the maxInclusive facet in the definition of int, the URI is:

http://www.w3.org/2001/XMLSchema#int.maxInclusive3.1 Namespace considerationsThe

http://www.w3.org/2001/XMLSchemaTo facilitate usage in specifications other than the XML Schema definition language, such as those that do not want to know anything about aspects of the XML Schema definition language other than the datatypes, each

http://www.w3.org/2001/XMLSchema-datatypesThis applies to both

Each

3.2 Primitive datatypes 3.2.1 string

3.2.2 boolean

3.2.3 decimal

3.2.4 float

3.2.5 double

3.2.6 duration

3.2.7 dateTime

3.2.8 time

3.2.9 date

3.2.10 gYearMonth

3.2.11 gYear

3.2.12 gMonthDay

3.2.13 gDay

3.2.14 gMonth

3.2.15 hexBinary

3.2.16 base64Binary

3.2.17 anyURI

3.2.18 QName

3.2.19 NOTATION

The

3.2.1 stringstring datatype represents character strings in XML. The string is the set of finite-length sequences of characters (as defined in [XML 1.0 (Second Edition)]) that

Note: Many human languages have writing systems that require child elements for control of aspects such as bidirectional formating or ruby annotation (see [Ruby] and Section 8.2.4 Overriding the bidirectional algorithm: the BDO element of [HTML 4.01]). Thus, string, as a simple type that can contain only characters but not child elements, is often not suitable for representing text. In such situations, a complex type that allows mixed content should be considered. For more information, see Section 5.5 Any Element, Any Attribute of [XML Schema Language: Part 0 Primer]. Note: As noted in ordered, the fact that this specification does not specify an 3.2.1.1 Constraining facetsstring has the following

lengthminLengthmaxLengthpatternenumerationwhiteSpace3.2.1.2 Derived datatypesThe following string:

normalizedString3.2.2 boolean

3.2.2.1 Lexical representationAn instance of a datatype that is defined as

3.2.2.2 Canonical representationThe canonical representation for boolean is the set of literals {true, false}.

3.2.2.3 Constraining facetsboolean has the following

patternwhiteSpace3.2.3 decimaldecimal is the set of numbers that can be obtained by multiplying an integer by a non-positive power of ten, i.e., expressible as i × 10^-n where i and n are integers and n >= 0. Precision is not reflected in this value space; the number 2.0 is not distinct from the number 2.00. The decimal is the order relation on real numbers, restricted to this subset.

Note: All 3.2.3.1 Lexical representationdecimal has a lexical representation consisting of a finite-length sequence of decimal digits (#x30-#x39) separated by a period as a decimal indicator. An optional leading sign is allowed. If the sign is omitted, "+" is assumed. Leading and trailing zeroes are optional. If the fractional part is zero, the period and following zero(es) can be omitted. For example: -1.23, 12678967.543233, +100000.00, 210.

3.2.3.2 Canonical representationThe canonical representation for decimal is defined by prohibiting certain options from the Lexical representation (§3.2.3.1). Specifically, the preceding optional "+" sign is prohibited. The decimal point is required. Leading and trailing zeroes are prohibited subject to the following: there must be at least one digit to the right and to the left of the decimal point which may be a zero.

3.2.3.3 Constraining facetsdecimal has the following

totalDigitsfractionDigitspatternwhiteSpaceenumerationmaxInclusivemaxExclusiveminInclusiveminExclusive3.2.3.4 Derived datatypesThe following decimal:

integer3.2.4 floatfloat consists of the values m × 2^e, where m is an integer whose absolute value is less than 2^24, and e is an integer between -149 and 104, inclusive. In addition to the basic float also contains the following three special values: positive and negative infinity and not-a-number (NaN). The float is: x < y iff y - x is positive for x and y in the value space. Positive infinity is greater than all other non-NaN values. NaN equals itself but is

Note: "Equality" in this Recommendation is defined to be "identity" (i.e., values that are identical in the Any value float values are

This datatype differs from that of [IEEE 754-1985] in that there is only one NaN and only one zero. This makes the equality and ordering of values in the data space differ from that of [IEEE 754-1985] only in that for schema purposes NaN = NaN.

A literal in the d maps to the normalized value in the float that is closest to d in the sense defined by [Clinger, WD (1990)]; if d is exactly halfway between two such values then the even value is chosen.

3.2.4.1 Lexical representationfloat values have a lexical representation consisting of a mantissa followed, optionally, by the character "E" or "e", followed by an exponent. The exponent

The special values positive and negative infinity and not-a-number have lexical representations INF, -INF and NaN, respectively. Lexical representations for zero may take a positive or negative sign.

For example, -1E4, 1267.43233E12, 12.78e-2, 12 , -0, 0 and INF are all legal literals for float.

3.2.4.2 Canonical representationThe canonical representation for float is defined by prohibiting certain options from the Lexical representation (§3.2.4.1). Specifically, the exponent must be indicated by "E". Leading zeroes and the preceding optional "+" sign are prohibited in the exponent. If the exponent is zero, it must be indicated by "E0". For the mantissa, the preceding optional "+" sign is prohibited and the decimal point is required. Leading and trailing zeroes are prohibited subject to the following: number representations must be normalized such that there is a single digit which is non-zero to the left of the decimal point and at least a single digit to the right of the decimal point unless the value being represented is zero. The canonical representation for zero is 0.0E0.

3.2.4.3 Constraining facetsfloat has the following

patternenumerationwhiteSpacemaxInclusivemaxExclusiveminInclusiveminExclusive3.2.5 doubledouble datatype is patterned after the IEEE double-precision 64-bit floating point type [IEEE 754-1985]. The basic double consists of the values m × 2^e, where m is an integer whose absolute value is less than 2^53, and e is an integer between -1075 and 970, inclusive. In addition to the basic double also contains the following three special values: positive and negative infinity and not-a-number (NaN). The double is: x < y iff y - x is positive for x and y in the value space. Positive infinity is greater than all other non-NaN values. NaN equals itself but is

Note: "Equality" in this Recommendation is defined to be "identity" (i.e., values that are identical in the Any value double values are

A literal in the d maps to the normalized value in the double that is closest to d; if d is exactly halfway between two such values then the even value is chosen. This is the best approximation of d ([Clinger, WD (1990)], [Gay, DM (1990)]), which is more accurate than the mapping required by [IEEE 754-1985].

3.2.5.1 Lexical representationdouble values have a lexical representation consisting of a mantissa followed, optionally, by the character "E" or "e", followed by an exponent. The exponent

The special values positive and negative infinity and not-a-number have lexical representations INF, -INF and NaN, respectively. Lexical representations for zero may take a positive or negative sign.

For example, -1E4, 1267.43233E12, 12.78e-2, 12 , -0, 0 and INF are all legal literals for double.

3.2.5.2 Canonical representationThe canonical representation for double is defined by prohibiting certain options from the Lexical representation (§3.2.5.1). Specifically, the exponent must be indicated by "E". Leading zeroes and the preceding optional "+" sign are prohibited in the exponent. If the exponent is zero, it must be indicated by "E0". For the mantissa, the preceding optional "+" sign is prohibited and the decimal point is required. Leading and trailing zeroes are prohibited subject to the following: number representations must be normalized such that there is a single digit which is non-zero to the left of the decimal point and at least a single digit to the right of the decimal point unless the value being represented is zero. The canonical representation for zero is 0.0E0.

3.2.5.3 Constraining facetsdouble has the following

patternenumerationwhiteSpacemaxInclusivemaxExclusiveminInclusiveminExclusive3.2.6 durationduration represents a duration of time. The duration is a six-dimensional space where the coordinates designate the Gregorian year, month, day, hour, minute, and second components defined in § 5.5.3.2 of [ISO 8601], respectively. These components are ordered in their significance by their order of appearance i.e. as year, month, day, hour, minute, and second.

YYYY) and a minimum fractional second precision of milliseconds or three decimal digits (i.e. s.sss). However, 3.2.6.1 Lexical representationThe lexical representation for duration is the [ISO 8601] extended format PnYn MnDTnH nMnS, where nY represents the number of years, nM the number of months, nD the number of days, 'T' is the date/time separator, nH the number of hours, nM the number of minutes and nS the number of seconds. The number of seconds can include decimal digits to arbitrary precision.

The values of the Year, Month, Day, Hour and Minutes components are not restricted but allow an arbitrary unsigned integer, i.e., an integer that conforms to the pattern [0-9]+.. Similarly, the value of the Seconds component allows an arbitrary unsigned decimal. Following [ISO 8601], at least one digit must follow the decimal point if it appears. That is, the value of the Seconds component must conform to the pattern [0-9]+(\.[0-9]+)?. Thus, the lexical representation of duration does not follow the alternative format of § 5.5.3.2.1 of [ISO 8601].

An optional preceding minus sign ('-') is allowed, to indicate a negative duration. If the sign is omitted a positive duration is indicated. See also ISO 8601 Date and Time Formats (§D).

For example, to indicate a duration of 1 year, 2 months, 3 days, 10 hours, and 30 minutes, one would write: P1Y2M3DT10H30M. One could also indicate a duration of minus 120 days as: -P120D.

Reduced precision and truncated representations of this format are allowed provided they conform to the following:

If the number of years, months, days, hours, minutes, or seconds in any expression equals zero, the number and its corresponding designator The seconds part The designator 'T' must be absent if and only if all of the time items are absent. The designator 'P' must always be present. For example, P1347Y, P1347M and P1Y2MT2H are all allowed; P0Y1347M and P0Y1347M0D are allowed. P-1347M is not allowed although -P1347M is allowed. P1Y2MT is not allowed.

3.2.6.2 Order relation on durationIn general, the duration is a partial order since there is no determinate relationship between certain durations such as one month (P1M) and 30 days (P30D). The duration values x and y is x < y iff s+x < s+y for each qualified dateTime s in the list below. These values for s cause the greatest deviations in the addition of dateTimes and durations. Addition of durations to time instants is defined in Adding durations to dateTimes (§E).

1696-09-01T00:00:00Z1697-02-01T00:00:00Z1903-03-01T00:00:00Z1903-07-01T00:00:00Z

The following table shows the strongest relationship that can be determined between example durations. The symbol <> means that the order relation is indeterminate. Note that because of leap-seconds, a seconds field can vary from 59 to 60. However, because of the way that addition is defined in Adding durations to dateTimes (§E), they are still totally ordered.

RelationP1Y

> P364D

<> P365D

<> P366D

< P367D

P1M

> P27D

<> P28D

<> P29D

<> P30D

<> P31D

< P32D

P5M

> P149D

<> P150D

<> P151D

<> P152D

<> P153D

< P154D

Implementations are free to optimize the computation of the ordering relationship. For example, the following table can be used to compare durations of a small number of months against days.

Months12345678910111213...DaysMinimum28

120

150

181

212

242

273

303

334

365

393

...

Maximum31

123

153

184

215

245

276

306

337

366

397

...

3.2.6.3 Facet Comparison for durationsIn comparing duration values with minInclusive, minExclusive, maxInclusive and maxExclusive facet values indeterminate comparisons should be considered as "false".

3.2.6.4 Totally ordered durationsCertain derived datatypes of durations can be guaranteed have a total order. For this, they must have fields from only one row in the list below and the time zone must either be required or prohibited.

year, monthday, hour, minute, secondFor example, a datatype could be defined to correspond to the [SQL] datatype Year-Month interval that required a four digit year field and a two digit month field but required all other fields to be unspecified. This datatype could be defined as below and would have a total order.

3.2.6.5 Constraining facetsduration has the following

patternenumerationwhiteSpacemaxInclusivemaxExclusiveminInclusiveminExclusive3.2.7 dateTimedateTime values may be viewed as objects with integer-valued year, month, day, hour and minute properties, a decimal-valued second property, and a boolean timezoned property. Each such object also has one decimal-valued method or computed property, timeOnTimeline, whose value is always a decimal number; the values are dimensioned in seconds, the integer 0 is 0001-01-01T00:00:00 and the value of timeOnTimeline for other dateTime values is computed using the Gregorian algorithm as modified for leap-seconds. The timeOnTimeline values form two related "timelines", one for timezoned values and one for non-timezoned values. Each timeline is a copy of the

The dateTime is closely related to the dates and times described in ISO 8601. For clarity, the text above specifies a particular origin point for the timeline. It should be noted, however, that schema processors need not expose the timeOnTimeline value to schema users, and there is no requirement that a timeline-based implementation use the particular origin described here in its internal representation. Other interpretations of the

All timezoned times are Coordinated Universal Time (UTC, sometimes called "Greenwich Mean Time"). Other timezones indicated in lexical representations are converted to UTC during conversion of literals to values. "Local" or untimezoned times are presumed to be the time in the timezone of some unspecified locality as prescribed by the appropriate legal authority; currently there are no legally prescribed timezones which are durations whose magnitude is greater than 14 hours. The value of each numeric-valued property (other than timeOnTimeline) is limited to the maximum value within the interval determined by the next-higher property. For example, the day value can never be 32, and cannot even be 29 for month 02 and year 2002 (February 2002).

Those using this (1.0) version of this Recommendation to represent negative years should be aware that the interpretation of lexical representations beginning with a '-' is likely to change in subsequent versions.

[ISO 8601] makes no mention of the year 0; in [ISO 8601:1998 Draft Revision] the form '0000' was disallowed and this recommendation disallows it as well. However, [ISO 8601:2000 Second Edition], which became available just as we were completing version 1.0, allows the form '0000', representing the year 1 BCE. A number of external commentators have also suggested that '0000' be allowed, as the lexical representation for 1 BCE, which is the normal usage in astronomical contexts. It is the intention of the XML Schema Working Group to allow '0000' as a lexical representation in the dateTime, date, gYear, and gYearMonth datatypes in a subsequent version of this Recommendation. '0000' will be the lexical representation of 1 BCE (which is a leap year), '-0001' will become the lexical representation of 2 BCE (not 1 BCE as in this (1.0) version), '-0002' of 3 BCE, etc.

Note: See the conformance note in (§3.2.6) which applies to this datatype as well.3.2.7.1 Lexical representationThe dateTime consists of finite-length sequences of characters of the form: '-'? yyyy '-' mm '-' dd 'T' hh ':' mm ':' ss ('.' s+)? (zzzzzz)?, where

'-'? yyyy is a four-or-more digit optionally negative-signed numeral that represents the year; if more than four digits, leading zeros are prohibited, and '0000' is prohibited (see the Note above (§3.2.7); also note that a plus sign is not permitted);the remaining '-'s are separators between parts of the date portion;the first mm is a two-digit numeral that represents the month;dd is a two-digit numeral that represents the day;'T' is a separator indicating that time-of-day follows;hh is a two-digit numeral that represents the hour; '24' is permitted if the minutes and seconds represented are zero, and the dateTime value so represented is the first instant of the following day (the hour property of a dateTime object in the ':' is a separator between parts of the time-of-day portion;the second mm is a two-digit numeral that represents the minute;ss is a two-integer-digit numeral that represents the whole seconds;'.' s+ (if present) represents the fractional seconds;zzzzzz (if present) represents the timezone (as described below).For example, 2002-10-10T12:00:00-05:00 (noon on 10 October 2002, Central Daylight Savings Time as well as Eastern Standard Time in the U.S.) is 2002-10-10T17:00:00Z, five hours later than 2002-10-10T12:00:00Z.

For further guidance on arithmetic with dateTimes and durations, see Adding durations to dateTimes (§E).

3.2.7.2 Canonical representationExcept for trailing fractional zero digits in the seconds representation, '24:00:00' time representations, and timezone (for timezoned values), the mapping from literals to values is one-to-one. Where there is more than one possible representation, the canonical representation is as follows:

The 2-digit numeral representing the hour must not be '24';The fractional second string, if present, must not end in '0';for timezoned values, the timezone must be represented with 'Z' (All timezoned dateTime values are UTC.).

3.2.7.3 TimezonesTimezones are durations with (integer-valued) hour and minute properties (with the hour magnitude limited to at most 14, and the minute magnitude limited to at most 59, except that if the hour magnitude is 14, the minute value must be 0); they may be both positive or both negative.

The lexical representation of a timezone is a string of the form: (('+' | '-') hh ':' mm) | 'Z', where

hh is a two-digit numeral (with leading zeros as required) that represents the hours,mm is a two-digit numeral that represents the minutes,'+' indicates a nonnegative duration,'-' indicates a nonpositive duration.The mapping so defined is one-to-one, except that '+00:00', '-00:00', and 'Z' all represent the same zero-length duration timezone, UTC; 'Z' is its canonical representation.

When a timezone is added to a UTC dateTime, the result is the date and time "in that timezone". For example, 2002-10-10T12:00:00+05:00 is 2002-10-10T07:00:00Z and 2002-10-10T00:00:00+05:00 is 2002-10-09T19:00:00Z.

3.2.7.4 Order relation on dateTimedateTime value objects on either timeline are totally ordered by their timeOnTimeline values; between the two timelines, dateTime value objects are ordered by their timeOnTimeline values when their timeOnTimeline values differ by more than fourteen hours, with those whose difference is a duration of 14 hours or less being

In general, the dateTime is a partial order since there is no determinate relationship between certain instants. For example, there is no determinate ordering between (a) 2000-01-20T12:00:00 and (b) 2000-01-20T12:00:00Z. Based on timezones currently in use, (c) could vary from 2000-01-20T12:00:00+12:00 to 2000-01-20T12:00:00-13:00. It is, however, possible for this range to expand or contract in the future, based on local laws. Because of this, the following definition uses a somewhat broader range of indeterminate values: +14:00..-14:00.

The following definition uses the notation S[year] to represent the year field of S, S[month] to represent the month field, and so on. The notation (Q & "-14:00") means adding the timezone -14:00 to Q, where Q did not already have a timezone. This is a logical explanation of the process. Actual implementations are free to optimize as long as they produce the same results.

The ordering between two dateTimes P and Q is defined by the following algorithm:

A.Normalize P and Q. That is, if there is a timezone present, but it is not Z, convert it to Z using the addition operation defined in Adding durations to dateTimes (§E)

Thus 2000-03-04T23:00:00+03:00 normalizes to 2000-03-04T20:00:00ZB. If P and Q either both have a time zone or both do not have a time zone, compare P and Q field by field from the year field down to the second field, and return a result as soon as it can be determined. That is:

If P[i] is not specified and Q[i] is, or vice versa, stop and return P <> QIf P[i] < Q[i], stop and return P < QIf P[i] > Q[i], stop and return P > QStop and return P = QC.Otherwise, if P contains a time zone and Q does not, compare as follows:

P > Q if P > (Q with time zone -14:00)P <> Q otherwise, that is, if (Q with time zone +14:00) < P < (Q with time zone -14:00)D. Otherwise, if P does not contain a time zone and Q does, compare as follows:

P > Q if (P with time zone +14:00) > Q.P <> Q otherwise, that is, if (P with time zone +14:00) < Q < (P with time zone -14:00)Examples:

DeterminateIndeterminate2000-01-15T00:00:00 < 2000-02-15T00:00:00

2000-01-01T12:00:00 <> 1999-12-31T23:00:00Z

2000-01-15T12:00:00 < 2000-01-16T12:00:00Z

2000-01-16T12:00:00 <> 2000-01-16T12:00:00Z

2000-01-16T00:00:00 <> 2000-01-16T12:00:00Z

3.2.7.5 Totally ordered dateTimesCertain derived types from dateTime can be guaranteed have a total order. To do so, they must require that a specific set of fields are always specified, and that remaining fields (if any) are always unspecified. For example, the date datatype without time zone is defined to contain exactly year, month, and day. Thus dates without time zone have a total order among themselves.

3.2.7.6 Constraining facetsdateTime has the following

patternenumerationwhiteSpacemaxInclusivemaxExclusiveminInclusiveminExclusive3.2.8 timetime is the space of time of day values as defined in § 5.3 of [ISO 8601]. Specifically, it is a set of zero-duration daily time instances.

Since the lexical representation allows an optional time zone indicator, time values are partially ordered because it may not be able to determine the order of two values one of which has a time zone and the other does not. The order relation on time values is the Order relation on dateTime (§3.2.7.4) using an arbitrary date. See also Adding durations to dateTimes (§E). Pairs of time values with or without time zone indicators are totally ordered.

Note: See the conformance note in (§3.2.6) which applies to the seconds part of this datatype as well.3.2.8.1 Lexical representationThe lexical representation for time is the left truncated lexical representation for dateTime: hh:mm:ss.sss with optional following time zone indicator. For example, to indicate 1:20 pm for Eastern Standard Time which is 5 hours behind Coordinated Universal Time (UTC), one would write: 13:20:00-05:00. See also ISO 8601 Date and Time Formats (§D).

3.2.8.2 Canonical representationThe canonical representation for time is defined by prohibiting certain options from the Lexical representation (§3.2.8.1). Specifically, either the time zone must be omitted or, if present, the time zone must be Coordinated Universal Time (UTC) indicated by a "Z". Additionally, the canonical representation for midnight is 00:00:00.

3.2.8.3 Constraining facetstime has the following

patternenumerationwhiteSpacemaxInclusivemaxExclusiveminInclusiveminExclusive3.2.9 datedate consists of top-open intervals of exactly one day in length on the timelines of dateTime, beginning on the beginning moment of each day (in each timezone), i.e. '00:00:00', up to but not including '24:00:00' (which is identical with '00:00:00' of the next day). For nontimezoned values, the top-open intervals disjointly cover the nontimezoned timeline, one per day. For timezoned values, the intervals begin at every minute and therefore overlap.

A "date object" is an object with year, month, and day properties just like those of dateTime objects, plus an optional timezone-valued timezone property. (As with values of dateTime timezones are a special case of durations.) Just as a dateTime object corresponds to a point on one of the timelines, a date object corresponds to an interval on one of the two timelines as just described.

Timezoned date values track the starting moment of their day, as determined by their timezone; said timezone is generally recoverable for canonical representations. recoverable timezone is that duration which is the result of subtracting the first moment (or any moment) of the timezoned date from the first moment (or the corresponding moment) UTC on the same date. date

For example: the first moment of 2002-10-10+13:00 is 2002-10-10T00:00:00+13, which is 2002-10-09T11:00:00Z, which is also the first moment of 2002-10-09-11:00. Therefore 2002-10-10+13:00 is 2002-10-09-11:00; they are the same interval.

Note: For most timezones, either the first moment or last moment of the day (a dateTime value, always UTC) will have a date portion different from that of the date itself! However, noon of that date (the midpoint of the interval) in that (normalized) timezone will always have the same date portion as the date itself, even when that noon point in time is normalized to UTC. For example, 2002-10-10-05:00 begins during 2002-10-09Z and 2002-10-10+05:00 ends during 2002-10-11Z, but noon of both 2002-10-10-05:00 and 2002-10-10+05:00 falls in the interval which is 2002-10-10Z. Note: See the conformance note in (§3.2.6) which applies to the year part of this datatype as well.3.2.9.1 Lexical representationFor the following discussion, let the "date portion" of a dateTime or date object be an object similar to a dateTime or date object, with similar year, month, and day properties, but no others, having the same value for these properties as the original dateTime or date object.

The date consists of finite-length sequences of characters of the form: '-'? yyyy '-' mm '-' dd zzzzzz? where the date and optional timezone are represented exactly the same way as they are for dateTime. The first moment of the interval is that represented by: '-' yyyy '-' mm '-' dd 'T00:00:00' zzzzzz? and the least upper bound of the interval is the timeline point represented (noncanonically) by: '-' yyyy '-' mm '-' dd 'T24:00:00' zzzzzz?.

Note: The date will always be a duration between '+12:00' and '11:59'. Timezone lexical representations, as explained for dateTime, can range from '+14:00' to '-14:00'. The result is that literals of dates with very large or very negative timezones will map to a "normalized" date value with a date itself. 3.2.9.2 Canonical representationGiven a member of the date date portion of the canonical representation (the entire representation for nontimezoned values, and all but the timezone representation for timezoned values) is always the date portion of the dateTime canonical representation of the interval midpoint (the dateTime representation, truncated on the right to eliminate 'T' and all following characters). For timezoned values, append the canonical representation of the

3.2.10 gYearMonthgYearMonth represents a specific gregorian month in a specific gregorian year. The gYearMonth is the set of Gregorian calendar months as defined in § 5.2.1 of [ISO 8601]. Specifically, it is a set of one-month long, non-periodic instances e.g. 1999-10 to represent the whole month of 1999-10, independent of how many days this month has.

Since the lexical representation allows an optional time zone indicator, gYearMonth values are partially ordered because it may not be possible to unequivocally determine the order of two values one of which has a time zone and the other does not. If gYearMonth values are considered as periods of time, the order relation on gYearMonth values is the order relation on their starting instants. This is discussed in Order relation on dateTime (§3.2.7.4). See also Adding durations to dateTimes (§E). Pairs of gYearMonth values with or without time zone indicators are totally ordered.

Note: Because month/year combinations in one calendar only rarely correspond to month/year combinations in other calendars, values of this type are not, in general, convertible to simple values corresponding to month/year combinations in other calendars. This type should therefore be used with caution in contexts where conversion to other calendars is desired. Note: See the conformance note in (§3.2.6) which applies to the year part of this datatype as well.3.2.10.1 Lexical representationThe lexical representation for gYearMonth is the reduced (right truncated) lexical representation for dateTime: CCYY-MM. No left truncation is allowed. An optional following time zone qualifier is allowed. To accommodate year values outside the range from 0001 to 9999, additional digits can be added to the left of this representation and a preceding "-" sign is allowed.

For example, to indicate the month of May 1999, one would write: 1999-05. See also ISO 8601 Date and Time Formats (§D).

3.2.10.2 Constraining facetsgYearMonth has the following

patternenumerationwhiteSpacemaxInclusivemaxExclusiveminInclusiveminExclusive3.2.11 gYeargYear represents a gregorian calendar year. The gYear is the set of Gregorian calendar years as defined in § 5.2.1 of [ISO 8601]. Specifically, it is a set of one-year long, non-periodic instances e.g. lexical 1999 to represent the whole year 1999, independent of how many months and days this year has.

Since the lexical representation allows an optional time zone indicator, gYear values are partially ordered because it may not be possible to unequivocally determine the order of two values one of which has a time zone and the other does not. If gYear values are considered as periods of time, the order relation on gYear values is the order relation on their starting instants. This is discussed in Order relation on dateTime (§3.2.7.4). See also Adding durations to dateTimes (§E). Pairs of gYear values with or without time zone indicators are totally ordered.

Note: Because years in one calendar only rarely correspond to years in other calendars, values of this type are not, in general, convertible to simple values corresponding to years in other calendars. This type should therefore be used with caution in contexts where conversion to other calendars is desired. Note: See the conformance note in (§3.2.6) which applies to the year part of this datatype as well.3.2.11.1 Lexical representationThe lexical representation for gYear is the reduced (right truncated) lexical representation for dateTime: CCYY. No left truncation is allowed. An optional following time zone qualifier is allowed as for dateTime. To accommodate year values outside the range from 0001 to 9999, additional digits can be added to the left of this representation and a preceding "-" sign is allowed.

For example, to indicate 1999, one would write: 1999. See also ISO 8601 Date and Time Formats (§D).

3.2.11.2 Constraining facetsgYear has the following

patternenumerationwhiteSpacemaxInclusivemaxExclusiveminInclusiveminExclusive3.2.12 gMonthDaygMonthDay is a gregorian date that recurs, specifically a day of the year such as the third of May. Arbitrary recurring dates are not supported by this datatype. The gMonthDay is the set of calendar dates, as defined in § 3 of [ISO 8601]. Specifically, it is a set of one-day long, annually periodic instances.

Since the lexical representation allows an optional time zone indicator, gMonthDay values are partially ordered because it may not be possible to unequivocally determine the order of two values one of which has a time zone and the other does not. If gMonthDay values are considered as periods of time, in an arbitrary leap year, the order relation on gMonthDay values is the order relation on their starting instants. This is discussed in Order relation on dateTime (§3.2.7.4). See also Adding durations to dateTimes (§E). Pairs of gMonthDay values with or without time zone indicators are totally ordered.

Note: Because day/month combinations in one calendar only rarely correspond to day/month combinations in other calendars, values of this type do not, in general, have any straightforward or intuitive representation in terms of most other calendars. This type should therefore be used with caution in contexts where conversion to other calendars is desired. 3.2.12.1 Lexical representationThe lexical representation for gMonthDay is the left truncated lexical representation for date: --MM-DD. An optional following time zone qualifier is allowed as for date. No preceding sign is allowed. No other formats are allowed. See also ISO 8601 Date and Time Formats (§D).

This datatype can be used to represent a specific day in a month. To say, for example, that my birthday occurs on the 14th of September ever year.

3.2.12.2 Constraining facetsgMonthDay has the following

patternenumerationwhiteSpacemaxInclusivemaxExclusiveminInclusiveminExclusive3.2.13 gDaygDay is a gregorian day that recurs, specifically a day of the month such as the 5th of the month. Arbitrary recurring days are not supported by this datatype. The gDay is the space of a set of calendar dates as defined in § 3 of [ISO 8601]. Specifically, it is a set of one-day long, monthly periodic instances.

This datatype can be used to represent a specific day of the month. To say, for example, that I get my paycheck on the 15th of each month.

Since the lexical representation allows an optional time zone indicator, gDay values are partially ordered because it may not be possible to unequivocally determine the order of two values one of which has a time zone and the other does not. If gDay values are considered as periods of time, in an arbitrary month that has 31 days, the order relation on gDay values is the order relation on their starting instants. This is discussed in Order relation on dateTime (§3.2.7.4). See also Adding durations to dateTimes (§E). Pairs of gDay values with or without time zone indicators are totally ordered.

Note: Because days in one calendar only rarely correspond to days in other calendars, values of this type do not, in general, have any straightforward or intuitive representation in terms of most other calendars. This type should therefore be used with caution in contexts where conversion to other calendars is desired. 3.2.13.1 Lexical representationThe lexical representation for gDay is the left truncated lexical representation for date: ---DD . An optional following time zone qualifier is allowed as for date. No preceding sign is allowed. No other formats are allowed. See also ISO 8601 Date and Time Formats (§D).

3.2.13.2 Constraining facetsgDay has the following

patternenumerationwhiteSpacemaxInclusivemaxExclusiveminInclusiveminExclusive3.2.14 gMonthgMonth is a gregorian month that recurs every year. The gMonth is the space of a set of calendar months as defined in § 3 of [ISO 8601]. Specifically, it is a set of one-month long, yearly periodic instances.

This datatype can be used to represent a specific month. To say, for example, that Thanksgiving falls in the month of November.

Since the lexical representation allows an optional time zone indicator, gMonth values are partially ordered because it may not be possible to unequivocally determine the order of two values one of which has a time zone and the other does not. If gMonth values are considered as periods of time, the order relation on gMonth is the order relation on their starting instants. This is discussed in Order relation on dateTime (§3.2.7.4). See also Adding durations to dateTimes (§E). Pairs of gMonth values with or without time zone indicators are totally ordered.

Note: Because months in one calendar only rarely correspond to months in other calendars, values of this type do not, in general, have any straightforward or intuitive representation in terms of most other calendars. This type should therefore be used with caution in contexts where conversion to other calendars is desired. 3.2.14.1 Lexical representationThe lexical representation for gMonth is the left and right truncated lexical representation for date: --MM. An optional following time zone qualifier is allowed as for date. No preceding sign is allowed. No other formats are allowed. See also ISO 8601 Date and Time Formats (§D).

3.2.14.2 Constraining facetsgMonth has the following

patternenumerationwhiteSpacemaxInclusivemaxExclusiveminInclusiveminExclusive3.2.15 hexBinaryhexBinary represents arbitrary hex-encoded binary data. The hexBinary is the set of finite-length sequences of binary octets.

3.2.15.1 Lexical RepresentationhexBinary has a lexical representation where each binary octet is encoded as a character tuple, consisting of two hexadecimal digits ([0-9a-fA-F]) representing the octet code. For example, "0FB7" is a hex encoding for the 16-bit integer 4023 (whose binary representation is 111110110111).

3.2.15.2 Canonical RepresentationThe canonical representation for hexBinary is defined by prohibiting certain options from the Lexical Representation (§3.2.15.1). Specifically, the lower case hexadecimal digits ([a-f]) are not allowed.

3.2.15.3 Constraining facetshexBinary has the following

lengthminLengthmaxLengthpatternenumerationwhiteSpace3.2.16 base64Binarybase64Binary represents Base64-encoded arbitrary binary data. The base64Binary is the set of finite-length sequences of binary octets. For base64Binary data the entire binary stream is encoded using the Base64 Alphabet in [RFC 2045].

The lexical forms of base64Binary values are limited to the 65 characters of the Base64 Alphabet defined in [RFC 2045], i.e., a-z, A-Z, 0-9, the plus sign (+), the forward slash (/) and the equal sign (=), together with the characters defined in [XML 1.0 (Second Edition)] as white space. No other characters are allowed.

For compatibility with older mail gateways, [RFC 2045] suggests that base64 data should have lines limited to at most 76 characters in length. This line-length limitation is not mandated in the lexical forms of base64Binary data and must not be enforced by XML Schema processors.

The lexical space of base64Binary is given by the following grammar (the notation is that used in [XML 1.0 (Second Edition)]); legal lexical forms must match the Base64Binary production.

Base64Binary ::= ((B64S B64S B64S B64S)*

((B64S B64S B64S B64) |

(B64S B64S B16S '=') |

(B64S B04S '=' #x20? '=')))?

B64S ::= B64 #x20?

B16S ::= B16 #x20?

B04S ::= B04 #x20?

B04 ::= [AQgw]

B16 ::= [AEIMQUYcgkosw048]

B64 ::= [A-Za-z0-9+/]

Note that this grammar requires the number of non-whitespace characters in the lexical form to be a multiple of four, and for equals signs to appear only at the end of the lexical form; strings which do not meet these constraints are not legal lexical forms of base64Binary because they cannot successfully be decoded by base64 decoders.

Note: The above definition of the lexical space is more restrictive than that given in [RFC 2045] as regards whitespace -- this is not an issue in practice. Any string compatible with the RFC can occur in an element or attribute validated by this type, because the collapse, which means that all leading and trailing whitespace will be stripped, and all internal whitespace collapsed to single space characters, before the above grammar is enforced.The canonical lexical form of a base64Binary data value is the base64 encoding of the value which matches the Canonical-base64Binary production in the following grammar:

Canonical-base64Binary ::= (B64 B64 B64 B64)*

((B64 B64 B16 '=') | (B64 B04 '=='))?

Note: For some values the canonical form defined above does not conform to [RFC 2045], which requires breaking with linefeeds at appropriate intervals.The length of a base64Binary value is the number of octets it contains. This may be calculated from the lexical form by removing whitespace and padding characters and performing the calculation shown in the pseudo-code below:

lex2 := killwhitespace(lexform) -- remove whitespace characters

lex3 := strip_equals(lex2) -- strip padding characters at end

length := floor (length(lex3) * 3 / 4) -- calculate length

Note on encoding: [RFC 2045] explicitly references US-ASCII encoding. However, decoding of base64Binary data in an XML entity is to be performed on the Unicode characters obtained after character encoding processing as specified by [XML 1.0 (Second Edition)]

3.2.16.1 Constraining facetsbase64Binary has the following

lengthminLengthmaxLengthpatternenumerationwhiteSpace3.2.17 anyURIanyURI represents a Uniform Resource Identifier Reference (URI). An anyURI value can be absolute or relative, and may have an optional fragment identifier (i.e., it may be a URI Reference). This type should be used to specify the intention that the value fulfills the role of a URI as defined by [RFC 2396], as amended by [RFC 2732].

The mapping from anyURI values to URIs is as defined by the URI reference escaping procedure defined in Section 5.4 Locator Attribute of [XML Linking Language] (see also Section 8 Character Encoding in URI References of [Character Model]). This means that a wide range of internationalized resource identifiers can be specified when an anyURI is called for, and still be understood as URIs per [RFC 2396], as amended by [RFC 2732], where appropriate to identify resources.

Note: Section 5.4 Locator Attribute of [XML Linking Language] requires that relative URI references be absolutized as defined in [XML Base] before use. This is an XLink-specific requirement and is not appropriate for XML Schema, since neither the Note: Each URI scheme imposes specialized syntax rules for URIs in that scheme, including restrictions on the syntax of allowed fragment identifiers. Because it is impractical for processors to check that a value is a context-appropriate URI reference, this specification follows the lead of [RFC 2396] (as amended by [RFC 2732]) in this matter: such rules and restrictions are not part of type validity and are not checked by 3.2.17.1 Lexical representationThe anyURI is finite-length character sequences which, when the algorithm defined in Section 5.4 of [XML Linking Language] is applied to them, result in strings which are legal URIs according to [RFC 2396], as amended by [RFC 2732].

Note: Spaces are, in principle, allowed in the anyURI, however, their use is highly discouraged (unless they are encoded by %20). 3.2.17.2 Constraining facetsanyURI has the following

lengthminLengthmaxLengthpatternenumerationwhiteSpace3.2.18 QNameQName represents XML qualified names. The QName is the set of tuples {namespace name, local part}, where namespace name is an anyURI and local part is an NCName. The QName is the set of strings that

Note: The mapping between literals in the QName requires a namespace declaration to be in scope for the context in which QName is used. 3.2.18.1 Constraining facetsQName has the following

lengthminLengthmaxLengthpatternenumerationwhiteSpaceThe use of

3.2.19 NOTATIONNOTATION represents the NOTATION attribute type from [XML 1.0 (Second Edition)]. The NOTATION is the set of QNames of notations declared in the current schema. The NOTATION is the set of all names of notations declared in the current schema (in the form of QNames).

Schema Component Constraint: enumeration facet value required for NOTATION

It is an NOTATION to be used directly in a schema. Only datatypes that are NOTATION by specifying a value for For compatibility (see Terminology (§1.4)) NOTATION should be used only on attributes and should only be used in schemas with no target namespace.

3.2.19.1 Constraining facetsNOTATION has the following

lengthminLengthmaxLengthpatternenumerationwhiteSpaceThe use of

3.3 Derived datatypes 3.3.1 normalizedString

3.3.2 token

3.3.3 language

3.3.4 NMTOKEN

3.3.5 NMTOKENS

3.3.6 Name

3.3.7 NCName

3.3.8 ID

3.3.9 IDREF

3.3.10 IDREFS

3.3.11 ENTITY

3.3.12 ENTITIES

3.3.13 integer

3.3.14 nonPositiveInteger

3.3.15 negativeInteger

3.3.16 long

3.3.17 int

3.3.18 short

3.3.19 byte

3.3.20 nonNegativeInteger

3.3.21 unsignedLong

3.3.22 unsignedInt

3.3.23 unsignedShort

3.3.24 unsignedByte

3.3.25 positiveInteger

This section gives conceptual definitions for all

3.3.1 normalizedStringnormalizedString represents white space normalized strings. The normalizedString is the set of strings that do not contain the carriage return (#xD), line feed (#xA) nor tab (#x9) characters. The normalizedString is the set of strings that do not contain the carriage return (#xD), line feed (#xA) nor tab (#x9) characters. The normalizedString is string.

3.3.1.1 Constraining facetsnormalizedString has the following

lengthminLengthmaxLengthpatternenumerationwhiteSpace3.3.1.2 Derived datatypesThe following normalizedString:

token3.3.2 tokentoken represents tokenized strings. The token is the set of strings that do not contain the carriage return (#xD), line feed (#xA) nor tab (#x9) characters, that have no leading or trailing spaces (#x20) and that have no internal sequences of two or more spaces. The token is the set of strings that do not contain the carriage return (#xD), line feed (#xA) nor tab (#x9) characters, that have no leading or trailing spaces (#x20) and that have no internal sequences of two or more spaces. The token is normalizedString.

3.3.2.1 Constraining facetstoken has the following

lengthminLengthmaxLengthpatternenumerationwhiteSpace3.3.2.2 Derived datatypesThe following token:

languageNMTOKENName3.3.3 languagelanguage represents natural language identifiers as defined by by [RFC 3066] . The language is the set of all strings that are valid language identifiers as defined [RFC 3066] . The language is the set of all strings that conform to the pattern [a-zA-Z]{1,8}(-[a-zA-Z0-9]{1,8})* . The language is token.

3.3.3.1 Constraining facetslanguage has the following

lengthminLengthmaxLengthpatternenumerationwhiteSpace3.3.4 NMTOKENNMTOKEN represents the NMTOKEN attribute type from [XML 1.0 (Second Edition)]. The NMTOKEN is the set of tokens that NMTOKEN is the set of strings that NMTOKEN is token.

For compatibility (see Terminology (§1.4)) NMTOKEN should be used only on attributes.

3.3.4.1 Constraining facetsNMTOKEN has the following

lengthminLengthmaxLengthpatternenumerationwhiteSpace3.3.4.2 Derived datatypesThe following NMTOKEN:

NMTOKENS3.3.5 NMTOKENSNMTOKENS represents the NMTOKENS attribute type from [XML 1.0 (Second Edition)]. The NMTOKENS is the set of finite, non-zero-length sequences of NMTOKENS is the set of space-separated lists of tokens, of which each token is in the NMTOKENS is NMTOKEN.

For compatibility (see Terminology (§1.4)) NMTOKENS should be used only on attributes.

3.3.5.1 Constraining facetsNMTOKENS has the following

lengthminLengthmaxLengthenumerationwhiteSpacepattern3.3.6 NameName represents XML Names. The Name is the set of all strings which Name is the set of all strings which Name is token.

3.3.6.1 Constraining facetsName has the following

lengthminLengthmaxLengthpatternenumerationwhiteSpace3.3.6.2 Derived datatypesThe following Name:

NCName3.3.7 NCNameNCName represents XML "non-colonized" Names. The NCName is the set of all strings which NCName is the set of all strings which NCName is Name.

3.3.7.1 Constraining facetsNCName has the following

lengthminLengthmaxLengthpatternenumerationwhiteSpace3.3.7.2 Derived datatypesThe following NCName:

IDIDREFENTITY3.3.8 IDID represents the ID attribute type from [XML 1.0 (Second Edition)]. The ID is the set of all strings that ID is the set of all strings that ID is NCName.

For compatibility (see Terminology (§1.4)) ID should be used only on attributes.

3.3.8.1 Constraining facetsID has the following

lengthminLengthmaxLengthpatternenumerationwhiteSpace3.3.9 IDREFIDREF represents the IDREF attribute type from [XML 1.0 (Second Edition)]. The IDREF is the set of all strings that IDREF is the set of strings that IDREF is NCName.

For compatibility (see Terminology (§1.4)) this datatype should be used only on attributes.

3.3.9.1 Constraining facetsIDREF has the following

lengthminLengthmaxLengthpatternenumerationwhiteSpace3.3.9.2 Derived datatypesThe following IDREF:

IDREFS3.3.10 IDREFSIDREFS represents the IDREFS attribute type from [XML 1.0 (Second Edition)]. The IDREFS is the set of finite, non-zero-length sequences of IDREFs. The IDREFS is the set of space-separated lists of tokens, of which each token is in the IDREFS is IDREF.

For compatibility (see Terminology (§1.4)) IDREFS should be used only on attributes.

3.3.10.1 Constraining facetsIDREFS has the following

lengthminLengthmaxLengthenumerationwhiteSpacepattern3.3.11 ENTITYENTITY represents the ENTITY attribute type from [XML 1.0 (Second Edition)]. The ENTITY is the set of all strings that ENTITY is the set of all strings that ENTITY is NCName.

Note: The ENTITY is scoped to a specific instance document. For compatibility (see Terminology (§1.4)) ENTITY should be used only on attributes.

3.3.11.1 Constraining facetsENTITY has the following

lengthminLengthmaxLengthpatternenumerationwhiteSpace3.3.11.2 Derived datatypesThe following ENTITY:

ENTITIES3.3.12 ENTITIESENTITIES represents the ENTITIES attribute type from [XML 1.0 (Second Edition)]. The ENTITIES is the set of finite, non-zero-length sequences of ENTITIES is the set of space-separated lists of tokens, of which each token is in the ENTITIES is ENTITY.

Note: The ENTITIES is scoped to a specific instance document. For compatibility (see Terminology (§1.4)) ENTITIES should be used only on attributes.

3.3.12.1 Constraining facetsENTITIES has the following

lengthminLengthmaxLengthenumerationwhiteSpacepattern3.3.13 integerinteger is integer is the infinite set {...,-2,-1,0,1,2,...}. The integer is decimal.

3.3.13.1 Lexical representationinteger has a lexical representation consisting of a finite-length sequence of decimal digits (#x30-#x39) with an optional leading sign. If the sign is omitted, "+" is assumed. For example: -1, 0, 12678967543233, +100000.

3.3.13.2 Canonical representationThe canonical representation for integer is defined by prohibiting certain options from the Lexical representation (§3.3.13.1). Specifically, the preceding optional "+" sign is prohibited and leading zeroes are prohibited.

3.3.13.3 Constraining facetsinteger has the following

totalDigitsfractionDigitspatternwhiteSpaceenumerationmaxInclusivemaxExclusiveminInclusiveminExclusive3.3.13.4 Derived datatypesThe following integer:

nonPositiveIntegerlongnonNegativeInteger3.3.14 nonPositiveIntegernonPositiveInteger is nonPositiveInteger is the infinite set {...,-2,-1,0}. The nonPositiveInteger is integer.

3.3.14.1 Lexical representationnonPositiveInteger has a lexical representation consisting of an optional preceding sign followed by a finite-length sequence of decimal digits (#x30-#x39). The sign may be "+" or may be omitted only for lexical forms denoting zero; in all other lexical forms, the negative sign ("-") must be present. For example: -1, 0, -12678967543233, -100000.

3.3.14.2 Canonical representationThe canonical representation for nonPositiveInteger is defined by prohibiting certain options from the Lexical representation (§3.3.14.1). In the canonical form for zero, the sign must be omitted. Leading zeroes are prohibited.

3.3.14.3 Constraining facetsnonPositiveInteger has the following

totalDigitsfractionDigitspatternwhiteSpaceenumerationmaxInclusivemaxExclusiveminInclusiveminExclusive3.3.14.4 Derived datatypesThe following nonPositiveInteger:

negativeInteger3.3.15 negativeIntegernegativeInteger is negativeInteger is the infinite set {...,-2,-1}. The negativeInteger is nonPositiveInteger.

3.3.15.1 Lexical representationnegativeInteger has a lexical representation consisting of a negative sign ("-") followed by a finite-length sequence of decimal digits (#x30-#x39). For example: -1, -12678967543233, -100000.

3.3.15.2 Canonical representationThe canonical representation for negativeInteger is defined by prohibiting certain options from the Lexical representation (§3.3.15.1). Specifically, leading zeroes are prohibited.

3.3.15.3 Constraining facetsnegativeInteger has the following

totalDigitsfractionDigitspatternwhiteSpaceenumerationmaxInclusivemaxExclusiveminInclusiveminExclusive3.3.16 longlong is long is integer.

3.3.16.1 Lexical representationlong has a lexical representation consisting of an optional sign followed by a finite-length sequence of decimal digits (#x30-#x39). If the sign is omitted, "+" is assumed. For example: -1, 0, 12678967543233, +100000.

3.3.16.2 Canonical representationThe canonical representation for long is defined by prohibiting certain options from the Lexical representation (§3.3.16.1). Specifically, the the optional "+" sign is prohibited and leading zeroes are prohibited.

3.3.16.3 Constraining facetslong has the following

totalDigitsfractionDigitspatternwhiteSpaceenumerationmaxInclusivemaxExclusiveminInclusiveminExclusive3.3.16.4 Derived datatypesThe following long:

int3.3.17 intint is int is long.

3.3.17.1 Lexical representationint has a lexical representation consisting of an optional sign followed by a finite-length sequence of decimal digits (#x30-#x39). If the sign is omitted, "+" is assumed. For example: -1, 0, 126789675, +100000.

3.3.17.2 Canonical representationThe canonical representation for int is defined by prohibiting certain options from the Lexical representation (§3.3.17.1). Specifically, the the optional "+" sign is prohibited and leading zeroes are prohibited.

3.3.17.3 Constraining facetsint has the following

totalDigitsfractionDigitspatternwhiteSpaceenumerationmaxInclusivemaxExclusiveminInclusiveminExclusive3.3.17.4 Derived datatypesThe following int:

short3.3.18 shortshort is short is int.

3.3.18.1 Lexical representationshort has a lexical representation consisting of an optional sign followed by a finite-length sequence of decimal digits (#x30-#x39). If the sign is omitted, "+" is assumed. For example: -1, 0, 12678, +10000.

3.3.18.2 Canonical representationThe canonical representation for short is defined by prohibiting certain options from the Lexical representation (§3.3.18.1). Specifically, the the optional "+" sign is prohibited and leading zeroes are prohibited.

3.3.18.3 Constraining facetsshort has the following

totalDigitsfractionDigitspatternwhiteSpaceenumerationmaxInclusivemaxExclusiveminInclusiveminExclusive3.3.18.4 Derived datatypesThe following short:

byte3.3.19 bytebyte is byte is short.

3.3.19.1 Lexical representationbyte has a lexical representation consisting of an optional sign followed by a finite-length sequence of decimal digits (#x30-#x39). If the sign is omitted, "+" is assumed. For example: -1, 0, 126, +100.

3.3.19.2 Canonical representationThe canonical representation for byte is defined by prohibiting certain options from the Lexical representation (§3.3.19.1). Specifically, the the optional "+" sign is prohibited and leading zeroes are prohibited.

3.3.19.3 Constraining facetsbyte has the following

totalDigitsfractionDigitspatternwhiteSpaceenumerationmaxInclusivemaxExclusiveminInclusiveminExclusive3.3.20 nonNegativeIntegernonNegativeInteger is nonNegativeInteger is the infinite set {0,1,2,...}. The nonNegativeInteger is integer.

3.3.20.1 Lexical representationnonNegativeInteger has a lexical representation consisting of an optional sign followed by a finite-length sequence of decimal digits (#x30-#x39). If the sign is omitted, the positive sign ("+") is assumed. If the sign is present, it must be "+" except for lexical forms denoting zero, which may be preceded by a positive ("+") or a negative ("-") sign. For example: 1, 0, 12678967543233, +100000.

3.3.20.2 Canonical representationThe canonical representation for nonNegativeInteger is defined by prohibiting certain options from the Lexical representation (§3.3.20.1). Specifically, the the optional "+" sign is prohibited and leading zeroes are prohibited.

3.3.20.3 Constraining facetsnonNegativeInteger has the following

totalDigitsfractionDigitspatternwhiteSpaceenumerationmaxInclusivemaxExclusiveminInclusiveminExclusive3.3.20.4 Derived datatypesThe following nonNegativeInteger:

unsignedLongpositiveInteger3.3.21 unsignedLongunsignedLong is unsignedLong is nonNegativeInteger.

3.3.21.1 Lexical representationunsignedLong has a lexical representation consisting of a finite-length sequence of decimal digits (#x30-#x39). For example: 0, 12678967543233, 100000.

3.3.21.2 Canonical representationThe canonical representation for unsignedLong is defined by prohibiting certain options from the Lexical representation (§3.3.21.1). Specifically, leading zeroes are prohibited.

3.3.21.3 Constraining facetsunsignedLong has the following

totalDigitsfractionDigitspatternwhiteSpaceenumerationmaxInclusivemaxExclusiveminInclusiveminExclusive3.3.21.4 Derived datatypesThe following unsignedLong:

unsignedInt3.3.22 unsignedIntunsignedInt is unsignedInt is unsignedLong.

3.3.22.1 Lexical representationunsignedInt has a lexical representation consisting of a finite-length sequence of decimal digits (#x30-#x39). For example: 0, 1267896754, 100000.

3.3.22.2 Canonical representationThe canonical representation for unsignedInt is defined by prohibiting certain options from the Lexical representation (§3.3.22.1). Specifically, leading zeroes are prohibited.

3.3.22.3 Constraining facetsunsignedInt has the following

totalDigitsfractionDigitspatternwhiteSpaceenumerationmaxInclusivemaxExclusiveminInclusiveminExclusive3.3.22.4 Derived datatypesThe following unsignedInt:

unsignedShort3.3.23 unsignedShortunsignedShort is unsignedShort is unsignedInt.

3.3.23.1 Lexical representationunsignedShort has a lexical representation consisting of a finite-length sequence of decimal digits (#x30-#x39). For example: 0, 12678, 10000.

3.3.23.2 Canonical representationThe canonical representation for unsignedShort is defined by prohibiting certain options from the Lexical representation (§3.3.23.1). Specifically, the leading zeroes are prohibited.

3.3.23.3 Constraining facetsunsignedShort has the following

totalDigitsfractionDigitspatternwhiteSpaceenumerationmaxInclusivemaxExclusiveminInclusiveminExclusive3.3.23.4 Derived datatypesThe following unsignedShort:

unsignedByte3.3.24 unsignedByteunsignedByte is unsignedByte is unsignedShort.

3.3.24.1 Lexical representationunsignedByte has a lexical representation consisting of a finite-length sequence of decimal digits (#x30-#x39). For example: 0, 126, 100.

3.3.24.2 Canonical representationThe canonical representation for unsignedByte is defined by prohibiting certain options from the Lexical representation (§3.3.24.1). Specifically, leading zeroes are prohibited.

3.3.24.3 Constraining facetsunsignedByte has the following

totalDigitsfractionDigitspatternwhiteSpaceenumerationmaxInclusivemaxExclusiveminInclusiveminExclusive3.3.25 positiveIntegerpositiveInteger is positiveInteger is the infinite set {1,2,...}. The positiveInteger is nonNegativeInteger.

3.3.25.1 Lexical representationpositiveInteger has a lexical representation consisting of an optional positive sign ("+") followed by a finite-length sequence of decimal digits (#x30-#x39). For example: 1, 12678967543233, +100000.

3.3.25.2 Canonical representationThe canonical representation for positiveInteger is defined by prohibiting certain options from the Lexical representation (§3.3.25.1). Specifically, the optional "+" sign is prohibited and leading zeroes are prohibited.

3.3.25.3 Constraining facetspositiveInteger has the following

totalDigitsfractionDigitspatternwhiteSpaceenumerationmaxInclusivemaxExclusiveminInclusiveminExclusive4 Datatype componentsThe following sections provide full details on the properties and significance of each kind of schema component involved in datatype definitions. For each property, the kinds of values it is allowed to have is specified. Any property not identified as optional is required to be present; optional properties which are not present have absent as their value. Any property identified as a having a set, subset or

For more information on the notion of datatype (schema) components, see Schema Component Details of [XML Schema Part 1: Structures].

4.1 Simple Type Definition 4.1.1 The Simple Type Definition Schema Component

4.1.2 XML Representation of Simple Type Definition Schema Components

4.1.3 Constraints on XML Representation of Simple Type Definition

4.1.4 Simple Type Definition Validation Rules

4.1.5 Constraints on Simple Type Definition Schema Components

4.1.6 Simple Type Definition for anySimpleType

Simple Type definitions provide for:

Establishing the Attaching a unique name (actually a QName) to the 4.1.1 The Simple Type Definition Schema ComponentThe Simple Type Definition schema component has the following properties:

Either absent or a namespace name, as defined in [Namespaces in XML]. atomic, list, union}. Depending on the value of {variety}, further properties are defined as follows: A An A non-empty sequence of simple type definitions. A set of Fundamental facets (§2.4.1) If the datatype has been {restriction, list, union}. Datatypes are identified by their {name} and {target namespace}. Except for anonymous datatypes (those with no {name}), datatype definitions

If {variety} is

The value of {facets} consists of the set of

The value of {fundamental facets} consists of the set of

If {final} is the empty set then the type can be used in deriving other types; the explicit values restriction, list and union prevent further derivations by

4.1.2 XML Representation of Simple Type Definition Schema ComponentsThe XML representation for a Simple Type Definition schema component is a <simpleType> element information item. The correspondences between the properties of the information item and properties of the component are as follows:

#all | List of (list | union | restriction))

id = ID

name = NCName

{any attributes with non-schema namespace . . .}>

Content: (annotation?, (restriction | list | union))

</simpleType>

Schema ComponentPropertyRepresentation{name}

The actual value of the name [attribute], if present, otherwise null

{final}

A set corresponding to the actual value of the final [attribute], if present, otherwise the actual value of the finalDefault [attribute] of the ancestor schema element information item, if present, otherwise the empty string, as follows: the empty set;{restriction, list, union};Note: Although the finalDefault [attribute] of schema may include values other than restriction, list or union, those values are ignored in the determination of {final}

{target namespace}

The actual value of the targetNamespace [attribute] of the parent schema element information item.

{annotation}

The annotation corresponding to the <annotation> element information item in the [children], if present, otherwise null

A restriction, by list or by union.

4.1.2.1 Derivation by restriction

id = ID

{any attributes with non-schema namespace . . .}>

</restriction>

Schema ComponentPropertyRepresentation{variety}

The actual value of {variety} of {base type definition}

{facets}

The union of the set of Facets (§2.4) components resolved to by the facet [children] merged with {facets} from {base type definition}, subject to the Facet Restriction Valid constraints specified in Facets (§2.4).

{base type definition}

The Simple Type Definition component resolved to by the actual value of the base [attribute] or the <simpleType> [children], whichever is present.

ExampleAn electronic commerce schema might define a datatype called Sku (the barcode number that appears on products) from the <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 4.1.2.2 Derivation by list

itemType = QName

{any attributes with non-schema namespace . . .}>

Content: (annotation?, simpleType?)

</list>

Schema ComponentPropertyRepresentation{variety}

list

{item type definition}

The Simple Type Definition component resolved to by the actual value of the itemType [attribute] or the <simpleType> [children], whichever is present.

ExampleA 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 As mentioned in List datatypes (§2.5.1.2), when a datatype is

For each of unit of length is measured in number of list items. The value of collapse.

4.1.2.3 Derivation by union

memberTypes = List of QName

{any attributes with non-schema namespace . . .}>

Content: (annotation?, simpleType*)

</union>

Schema ComponentPropertyRepresentation{variety}

union

{member type definitions}

The sequence of Simple Type Definition components resolved to by the items in the actual value of the memberTypes [attribute], if any, in order, followed by the Simple Type Definition components resolved to by the <simpleType> [children], if any, in order. If {variety} is union for any Simple Type Definition components resolved to above, then the Simple Type Definition is replaced by its {member type definitions}.

ExampleAs 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 with one of the tokens "small", "medium" or "large". The <xsd:attribute name="size"> <xsd:simpleType> <xsd:union> <xsd:simpleType> <xsd:restriction base="xsd:positiveInteger"> <xsd:minInclusive value="8"/> <xsd:maxInclusive value="72"/> </xsd:restriction> </xsd:simpleType> <xsd:simpleType> <xsd:restriction base="xsd:NMTOKEN"> <xsd:enumeration value="small"/> <xsd:enumeration value="medium"/> <xsd:enumeration value="large"/> </xsd:restriction> </xsd:simpleType> </xsd:union> </xsd:simpleType></xsd:attribute>

A headerthis is a test

As mentioned in Union datatypes (§2.5.1.3), when a datatype is

4.1.3 Constraints on XML Representation of Simple Type DefinitionSchema Representation Constraint: Single Facet Value

Unless otherwise specifically allowed by this specification (Multiple patterns (§4.3.4.3) and Multiple enumerations (§4.3.5.3)) any given Schema Representation Constraint: itemType attribute or simpleType child

Either the itemType [attribute] or the <simpleType> [child] of the <list> element must be present, but not both. Schema Representation Constraint: base attribute or simpleType child

Either the base [attribute] or the simpleType [child] of the <restriction> element must be present, but not both. Schema Representation Constraint: memberTypes attribute or simpleType children

Either the memberTypes [attribute] of the <union> element must be non-empty or there must be at least one simpleType [child]. 4.1.4 Simple Type Definition Validation RulesValidation Rule: Facet Valid

A value in a Validation Rule: Datatype Valid

A string is datatype-valid with respect to a datatype definition if: 1 it 4.1.5 Constraints on Simple Type Definition Schema ComponentsSchema Component Constraint: applicable facets

The {base type definition}applicable {facets}If {variety} is list, then [all datatypes]

length, minLength, maxLength, pattern, enumeration, whiteSpace

If {variety} is union, then [all datatypes]

pattern, enumeration

else if {variety} is atomic, then string

length, minLength, maxLength, pattern, enumeration, whiteSpace

boolean

pattern, whiteSpace

float

pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive

double

pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive

decimal

totalDigits, fractionDigits, pattern, whiteSpace, enumeration, maxInclusive, maxExclusive, minInclusive, minExclusive

duration

pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive

dateTime

pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive

time

pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive

date

pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive

gYearMonth

pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive

gYear

pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive

gMonthDay

pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive

gDay

pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive

gMonth

pattern, enumeration, whiteSpace, maxInclusive, maxExclusive, minInclusive, minExclusive

hexBinary

length, minLength, maxLength, pattern, enumeration, whiteSpace

base64Binary

length, minLength, maxLength, pattern, enumeration, whiteSpace

anyURI

length, minLength, maxLength, pattern, enumeration, whiteSpace

QName

length, minLength, maxLength, pattern, enumeration, whiteSpace

NOTATION

length, minLength, maxLength, pattern, enumeration, whiteSpace

Schema Component Constraint: list of atomic

If {variety} is Schema Component Constraint: no circular unions

If {variety} is 4.1.6 Simple Type Definition for anySimpleTypeThere is a simple type definition nearly equivalent to the simple version of the ur-type definition present in every schema by definition. It has the following properties:

http://www.w3.org/2001/XMLSchema the ur-type definition

4.2 Fundamental Facets 4.2.1 equal

4.2.2 ordered

4.2.3 bounded

4.2.4 cardinality

4.2.5 numeric

4.2.1 equalEvery

for any a and b in the a is equal to b, denoted a = b, or a is not equal to b, denoted a != b there is no pair a and b from the a = b and a != b for all a in the a = a for any a and b in the a = b if and only if b = a for any a, b and c in the a = b and b = c, then a = c for any a and b in the a = b, then a and b cannot be distinguished (i.e., equality is identity) the

On every datatype, the operation Equal is defined in terms of the equality property of the a, b drawn from the Equal(a,b) is true if a = b, and false otherwise.

Note that in consequence of the above:

given A and B are disjoint, every pair of values a from A and b from B, a != btwo values which are members of the if a datatype T is then the T is the union of . Some values in the T are also values in the A. Other values in the T will be values in the B and so on. Values in the T which are also in the A can be compared with other values in the A according to the above rules. Similarly for values of type T and B and all the other if a datatype T' is T then the T' is a subset of the T. Values in the T and T' can be compared according to the above rules if datatypes T' and T'' are T then the T' and T'' may overlap. Values in the T' and T'' can be compared according to the above rules Note: There is no schema component corresponding to the equal 4.2.2 orderedorder relation on a

ordered if there exists an

partial order is an irreflexive, asymmetric and transitive.

for no a in the a < a (irreflexivity) for all a and b in the a b is used to indicate the case when a != b and neither a b.

a <> b, a and b are incomparable,comparable.

total order is an a and b is it the case that a <> b.

for all a and b in the a < b or b < a or a = b Note: The fact that this specification does not define an

indicating whether an 4.2.2.1 The ordered Schema Component{false, partial, total}. {value} depends on {variety}, {facets} and {member type definitions} in the Simple Type Definition component in which a

When {variety} is

When {variety} is false.

When {variety} is partial unless one of the following:

If every member of {member type definitions} is derived from a common ancestor other than the simple ur-type, then {value} is the same as that ancestor's ordered facet If every member of {member type definitions} has a {value} of false for the ordered facet, then {value} is false 4.2.3 boundedu in an inclusive upper bound of a V is a subset of U) if for all v in V, u >= v.

u in an exclusive upper bound of a V is a subset of U) if for all v in V, u > v.

l in an inclusive lower bound of a V is a subset of L) if for all v in V, l <= v.

l in an exclusive lower bound of a V is a subset of L) if for all v in V, l < v.

bounded if its

indicating whether a 4.2.3.1 The bounded Schema Component{value} depends on {variety}, {facets} and {member type definitions} in the Simple Type Definition component in which a

When {variety} is true; else {value} is false.

When {variety} is true for every member of {member type definitions} and all members of {member type definitions} share a common ancestor, then {value} is true; else {value} is false.

4.2.4 cardinalitycardinality. Some

It is sometimes useful to categorize

indicating whether the finite or countably infinite 4.2.4.1 The cardinality Schema Component{finite, countably infinite}. {value} depends on {variety}, {facets} and {member type definitions} in the Simple Type Definition component in which a

When {variety} is finite, then {value} is finite.

When {variety} is countably infinite and either of the following conditions are true, then {value} is finite; else {value} is countably infinite:

all of the following are true: one of either of the following are true: {base type definition} is one of date, gYearMonth, gYear, gMonthDay, gDay or gMonth or any type When {variety} is finite; else {value} is countably infinite.

When {variety} is finite for every member of {member type definitions}, then {value} is finite; else {value} is countably infinite.

4.2.5 numericnumeric if its values are conceptually quantities (in some mathematical number system).

non-numeric.

indicating whether a 4.2.5.1 The numeric Schema Component{value} depends on {variety}, {facets}, {base type definition} and {member type definitions} in the Simple Type Definition component in which a

When {variety} is

When {variety} is false.

When {variety} is true for every member of {member type definitions}, then {value} is true; else {value} is false.

4.3 Constraining Facets 4.3.1 length

4.3.2 minLength

4.3.3 maxLength

4.3.4 pattern

4.3.5 enumeration

4.3.6 whiteSpace

4.3.7 maxInclusive

4.3.8 maxExclusive

4.3.9 minExclusive

4.3.10 minInclusive

4.3.11 totalDigits

4.3.12 fractionDigits

4.3.1 lengthlength is the number of units of length, where units of length varies depending on the type that is being length

For string and datatypes length is measured in units of characters as defined in [XML 1.0 (Second Edition)]. For anyURI, length is measured in units of characters (as for string). For hexBinary and base64Binary and datatypes length is measured in octets (8 bits) of binary data. For datatypes length is measured in number of list items.

Note: For string and datatypes length will not always coincide with "string length" as perceived by some users or with the number of storage units in some digital representation. Therefore, care should be taken when specifying a value for length and in attempting to infer storage requirements from a given value for length.

Constraining a units of length, where units of length varies depending on {base type definition}. ExampleThe following is the definition of a length facet we ensure that types derived from productCode can change or set the values of other facets, such as pattern, but cannot change the length. <simpleType name='productCode'> <restriction base='string'> <length value='8' fixed='true'/> </restriction></simpleType>

4.3.1.1 The length Schema ComponentIf {fixed} is true, then types for which the current type is the {base type definition} cannot specify a value for length other than {value}.

4.3.1.2 XML Representation of length Schema ComponentsThe XML representation for a length schema component is a <length> element information item. The correspondences between the properties of the information item and properties of the component are as follows:

id = ID

value = nonNegativeInteger

{any attributes with non-schema namespace . . .}>

Content: (annotation?)

</length>

PropertyRepresentation{value}

The actual value of the value [attribute]

{fixed}

The actual value of the fixed [attribute], if present, otherwise false

{annotation}

The annotations corresponding to all the <annotation> element information items in the [children], if any.

4.3.1.3 length Validation RulesValidation Rule: Length Valid

A value in a The use of

4.3.1.4 Constraints on length Schema ComponentsSchema Component Constraint: length and minLength or maxLength

If length is a member of {facets} then 1 It is an error for minLength to be a member of {facets} unless 1.1 the {value} of minLength <= the {value} of length and1.2 there is type definition from which this one is derived by one or more restriction steps in which minLength has the same {value} and length is not specified.2 It is an error for maxLength to be a member of {facets} unless 2.1 the {value} of length <= the {value} of maxLength and2.2 there is type definition from which this one is derived by one or more restriction steps in which maxLength has the same {value} and length is not specified.Schema Component Constraint: length valid restriction

It is an 4.3.2 minLengthminLength is the minimum number of units of length, where units of length varies depending on the type that is being minLength

For string and datatypes minLength is measured in units of characters as defined in [XML 1.0 (Second Edition)]. For hexBinary and base64Binary and datatypes minLength is measured in octets (8 bits) of binary data. For datatypes minLength is measured in number of list items.

Note: For string and datatypes minLength will not always coincide with "string length" as perceived by some users or with the number of storage units in some digital representation. Therefore, care should be taken when specifying a value for minLength and in attempting to infer storage requirements from a given value for minLength.

Constraining a units of length, where units of length varies depending on {base type definition}. ExampleThe following is the definition of a <simpleType name='non-empty-string'> <restriction base='string'> <minLength value='1'/> </restriction></simpleType>

4.3.2.1 The minLength Schema ComponentIf {fixed} is true, then types for which the current type is the {base type definition} cannot specify a value for minLength other than {value}.

4.3.2.2 XML Representation of minLength Schema ComponentThe XML representation for a minLength schema component is a <minLength> element information item. The correspondences between the properties of the information item and properties of the component are as follows:

id = ID

value = nonNegativeInteger

{any attributes with non-schema namespace . . .}>

Content: (annotation?)

</minLength>

PropertyRepresentation{value}

The actual value of the value [attribute]

{fixed}

The actual value of the fixed [attribute], if present, otherwise false

{annotation}

The annotations corresponding to all the <annotation> element information items in the [children], if any.

4.3.2.3 minLength Validation RulesValidation Rule: minLength Valid

A value in a The use of

4.3.2.4 Constraints on minLength Schema ComponentsSchema Component Constraint: minLength <= maxLength

If both minLength and maxLength are members of {facets}, then the {value} of minLength Schema Component Constraint: minLength valid restriction

It is an 4.3.3 maxLengthmaxLength is the maximum number of units of length, where units of length varies depending on the type that is being maxLength

For string and datatypes maxLength is measured in units of characters as defined in [XML 1.0 (Second Edition)]. For hexBinary and base64Binary and datatypes maxLength is measured in octets (8 bits) of binary data. For datatypes maxLength is measured in number of list items.

Note: For string and datatypes maxLength will not always coincide with "string length" as perceived by some users or with the number of storage units in some digital representation. Therefore, care should be taken when specifying a value for maxLength and in attempting to infer storage requirements from a given value for maxLength.

Constraining a units of length, where units of length varies depending on {base type definition}. ExampleThe following is the definition of a <simpleType name='form-input'> <restriction base='string'> <maxLength value='50'/> </restriction></simpleType>

4.3.3.1 The maxLength Schema ComponentIf {fixed} is true, then types for which the current type is the {base type definition} cannot specify a value for maxLength other than {value}.

4.3.3.2 XML Representation of maxLength Schema ComponentsThe XML representation for a maxLength schema component is a <maxLength> element information item. The correspondences between the properties of the information item and properties of the component are as follows:

id = ID

value = nonNegativeInteger

{any attributes with non-schema namespace . . .}>

Content: (annotation?)

</maxLength>

PropertyRepresentation{value}

The actual value of the value [attribute]

{fixed}

The actual value of the fixed [attribute], if present, otherwise false

{annotation}

The annotations corresponding to all the <annotation> element information items in the [children], if any.

4.3.3.3 maxLength Validation RulesValidation Rule: maxLength Valid

A value in a The use of

4.3.3.4 Constraints on maxLength Schema ComponentsSchema Component Constraint: maxLength valid restriction

It is an 4.3.4 patternpattern is a constraint on the pattern

Constraining a ExampleThe following is the definition of a <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 Component4.3.4.2 XML Representation of pattern Schema ComponentsThe XML representation for a pattern schema component is a <pattern> element information item. The correspondences between the properties of the information item and properties of the component are as follows:

value = string

{any attributes with non-schema namespace . . .}>

Content: (annotation?)

</pattern>

{value} PropertyRepresentation{value}

The actual value of the value [attribute]

{annotation}

The annotations corresponding to all the <annotation> element information items in the [children], if any.

4.3.4.3 Constraints on XML Representation of patternSchema Representation Constraint: Multiple patterns

If multiple <pattern> element information items appear as [children] of a <simpleType>, the [value]s should be combined as if they appeared in a single Note: It is a consequence of the schema representation constraint Multiple patterns (§4.3.4.3) and of the rules for same step in a type derivation are ORed together, while different steps of a type derivation are ANDed together. Thus, to impose two

4.3.4.4 pattern Validation RulesValidation Rule: pattern valid

A literal in a 4.3.5 enumerationenumeration constrains the

enumeration does not impose an order relation on the

Constraining a ExampleThe following example is a datatype definition for a <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 Component4.3.5.2 XML Representation of enumeration Schema ComponentsThe XML representation for an enumeration schema component is an <enumeration> element information item. The correspondences between the properties of the information item and properties of the component are as follows:

value = anySimpleType

{any attributes with non-schema namespace . . .}>

Content: (annotation?)

</enumeration>

{value} PropertyRepresentation{value}

The actual value of the value [attribute]

{annotation}

The annotations corresponding to all the <annotation> element information items in the [children], if any.

4.3.5.3 Constraints on XML Representation of enumerationSchema Representation Constraint: Multiple enumerations

If multiple <enumeration> element information items appear as [children] of a <simpleType> the {value} of the enumeration component should be the set of all such [value]s. 4.3.5.4 enumeration Validation RulesValidation Rule: enumeration valid

A value in a 4.3.5.5 Constraints on enumeration Schema ComponentsSchema Component Constraint: enumeration valid restriction

It is an 4.3.6 whiteSpacewhiteSpace constrains the whiteSpace must be one of {preserve, replace, collapse}.

replace, contiguous sequences of #x20's are collapsed to a single #x20, and leading and trailing #x20's are removed. Note: The notation #xA used here (and elsewhere in this specification) represents the Universal Character Set (UCS) code point hexadecimal A (line feed), which is denoted by U+000A. This notation is to be distinguished from 
, which is the XML character reference to that same UCS code point. whiteSpace is applicable to all whiteSpace is collapse and cannot be changed by a schema author; for string the value of whiteSpace is preserve; for any type whiteSpace can be any of the three legal values. For all datatypes whiteSpace is collapse and cannot be changed by a schema author. For all datatypes whiteSpace does not apply directly; however, the normalization behavior of whiteSpace on that one of the

Note: For more information on whiteSpace, see the discussion on white space normalization in Schema Component Details in [XML Schema Part 1: Structures].

Constraining a ExampleThe following example is the datatype definition for the token <simpleType name='token'> <restriction base='normalizedString'> <whiteSpace value='collapse'/> </restriction></simpleType>

4.3.6.1 The whiteSpace Schema Component{preserve, replace, collapse}. If {fixed} is true, then types for which the current type is the {base type definition} cannot specify a value for whiteSpace other than {value}.

4.3.6.2 XML Representation of whiteSpace Schema ComponentsThe XML representation for a whiteSpace schema component is a <whiteSpace> element information item. The correspondences between the properties of the information item and properties of the component are as follows:

id = ID

value = (collapse | preserve | replace)

{any attributes with non-schema namespace . . .}>

Content: (annotation?)

</whiteSpace>

PropertyRepresentation{value}

The actual value of the value [attribute]

{fixed}

The actual value of the fixed [attribute], if present, otherwise false

{annotation}

The annotations corresponding to all the <annotation> element information items in the [children], if any.

4.3.6.3 whiteSpace Validation RulesNote: There are no 4.3.6.4 Constraints on whiteSpace Schema ComponentsSchema Component Constraint: whiteSpace valid restriction

It is an replace or preserve and the {value} of the parent whiteSpace is collapse 2 {value} is preserve and the {value} of the parent whiteSpace is replace 4.3.7 maxInclusivemaxInclusive is the maxInclusive

Constraining a ExampleThe following is the definition of a <simpleType name='one-hundred-or-less'> <restriction base='integer'> <maxInclusive value='100'/> </restriction></simpleType>

4.3.7.1 The maxInclusive Schema ComponentIf {fixed} is true, then types for which the current type is the {base type definition} cannot specify a value for maxInclusive other than {value}.

4.3.7.2 XML Representation of maxInclusive Schema ComponentsThe XML representation for a maxInclusive schema component is a <maxInclusive> element information item. The correspondences between the properties of the information item and properties of the component are as follows:

id = ID

value = anySimpleType

{any attributes with non-schema namespace . . .}>

Content: (annotation?)

</maxInclusive>

{value} PropertyRepresentation{value}

The actual value of the value [attribute]

{fixed}

The actual value of the fixed [attribute], if present, otherwise false, if present, otherwise false

{annotation}

The annotations corresponding to all the <annotation> element information items in the [children], if any.

4.3.7.3 maxInclusive Validation RulesValidation Rule: maxInclusive Valid

A value in an true, then the value false (i.e., {base type definition} is one of the date and time related datatypes), then the value 4.3.7.4 Constraints on maxInclusive Schema ComponentsSchema Component Constraint: minInclusive <= maxInclusive

It is an Schema Component Constraint: maxInclusive valid restriction

It is an 4.3.8 maxExclusivemaxExclusive is the maxExclusive

Constraining a ExampleThe following is the definition of a <simpleType name='less-than-one-hundred-and-one'> <restriction base='integer'> <maxExclusive value='101'/> </restriction></simpleType>

Note that the 4.3.8.1 The maxExclusive Schema ComponentIf {fixed} is true, then types for which the current type is the {base type definition} cannot specify a value for maxExclusive other than {value}.

4.3.8.2 XML Representation of maxExclusive Schema ComponentsThe XML representation for a maxExclusive schema component is a <maxExclusive> element information item. The correspondences between the properties of the information item and properties of the component are as follows:

id = ID

value = anySimpleType

{any attributes with non-schema namespace . . .}>

Content: (annotation?)

</maxExclusive>

{value} PropertyRepresentation{value}

The actual value of the value [attribute]

{fixed}

The actual value of the fixed [attribute], if present, otherwise false

{annotation}

The annotations corresponding to all the <annotation> element information items in the [children], if any.

4.3.8.3 maxExclusive Validation RulesValidation Rule: maxExclusive Valid

A value in an true, then the value false (i.e., {base type definition} is one of the date and time related datatypes), then the value 4.3.8.4 Constraints on maxExclusive Schema ComponentsSchema Component Constraint: maxInclusive and maxExclusive

It is an Schema Component Constraint: minExclusive <= maxExclusive

It is an Schema Component Constraint: maxExclusive valid restriction

It is an 4.3.9 minExclusiveminExclusive is the minExclusive

Constraining a ExampleThe following is the definition of a <simpleType name='more-than-ninety-nine'> <restriction base='integer'> <minExclusive value='99'/> </restriction></simpleType>

Note that the 4.3.9.1 The minExclusive Schema ComponentIf {fixed} is true, then types for which the current type is the {base type definition} cannot specify a value for minExclusive other than {value}.

4.3.9.2 XML Representation of minExclusive Schema ComponentsThe XML representation for a minExclusive schema component is a <minExclusive> element information item. The correspondences between the properties of the information item and properties of the component are as follows:

id = ID

value = anySimpleType

{any attributes with non-schema namespace . . .}>

Content: (annotation?)

</minExclusive>

{value} PropertyRepresentation{value}

The actual value of the value [attribute]

{fixed}

The actual value of the fixed [attribute], if present, otherwise false

{annotation}

The annotations corresponding to all the <annotation> element information items in the [children], if any.

4.3.9.3 minExclusive Validation RulesValidation Rule: minExclusive Valid

A value in an true, then the value false (i.e., {base type definition} is one of the date and time related datatypes), then the value 4.3.9.4 Constraints on minExclusive Schema ComponentsSchema Component Constraint: minInclusive and minExclusive

It is an Schema Component Constraint: minExclusive < maxInclusive

It is an Schema Component Constraint: minExclusive valid restriction

It is an 4.3.10 minInclusiveminInclusive is the minInclusive

Constraining a ExampleThe following is the definition of a <simpleType name='one-hundred-or-more'> <restriction base='integer'> <minInclusive value='100'/> </restriction></simpleType>

4.3.10.1 The minInclusive Schema ComponentIf {fixed} is true, then types for which the current type is the {base type definition} cannot specify a value for minInclusive other than {value}.

4.3.10.2 XML Representation of minInclusive Schema ComponentsThe XML representation for a minInclusive schema component is a <minInclusive> element information item. The correspondences between the properties of the information item and properties of the component are as follows:

id = ID

value = anySimpleType

{any attributes with non-schema namespace . . .}>

Content: (annotation?)

</minInclusive>

{value} PropertyRepresentation{value}

The actual value of the value [attribute]

{fixed}

The actual value of the fixed [attribute], if present, otherwise false

{annotation}

The annotations corresponding to all the <annotation> element information items in the [children], if any.

4.3.10.3 minInclusive Validation RulesValidation Rule: minInclusive Valid

A value in an true, then the value false (i.e., {base type definition} is one of the date and time related datatypes), then the value 4.3.10.4 Constraints on minInclusive Schema ComponentsSchema Component Constraint: minInclusive < maxExclusive

It is an Schema Component Constraint: minInclusive valid restriction

It is an 4.3.11 totalDigitstotalDigits controls the maximum number of values in the i × 10^-n where i and n are integers such that |i| < 10^totalDigits and 0 <= n <= totalDigits. The value of totalDigits

The term totalDigits is chosen to reflect the fact that it restricts the totalDigits digits. Note that it does not restrict the

4.3.11.1 The totalDigits Schema ComponentIf {fixed} is true, then types for which the current type is the {base type definition} cannot specify a value for totalDigits other than {value}.

4.3.11.2 XML Representation of totalDigits Schema ComponentsThe XML representation for a totalDigits schema component is a <totalDigits> element information item. The correspondences between the properties of the information item and properties of the component are as follows:

id = ID

value = positiveInteger

{any attributes with non-schema namespace . . .}>

Content: (annotation?)

</totalDigits>

PropertyRepresentation{value}

The actual value of the value [attribute]

{fixed}

The actual value of the fixed [attribute], if present, otherwise false

{annotation}

The annotations corresponding to all the <annotation> element information items in the [children], if any.

4.3.11.3 totalDigits Validation RulesValidation Rule: totalDigits Valid

A value in a i × 10^-n where i and n are integers such that |i| < 10^{value} and 0 <= n <= {value}. 4.3.11.4 Constraints on totalDigits Schema ComponentsSchema Component Constraint: totalDigits valid restriction

It is an 4.3.12 fractionDigitsfractionDigits controls the size of the minimum difference between values in the decimal, by restricting the i × 10^-n where i and n are integers and 0 <= n <= fractionDigits. The value of fractionDigits

The term fractionDigits is chosen to reflect the fact that it restricts the fractionDigits to the right of the decimal point. Note that it does not restrict the

ExampleThe following is the definition of a <simpleType name='celsiusBodyTemp'> <restriction base='decimal'> <totalDigits value='4'/> <fractionDigits value='1'/> <minInclusive value='36.4'/> <maxInclusive value='40.5'/> </restriction></simpleType>

4.3.12.1 The fractionDigits Schema ComponentIf {fixed} is true, then types for which the current type is the {base type definition} cannot specify a value for fractionDigits other than {value}.

4.3.12.2 XML Representation of fractionDigits Schema ComponentsThe XML representation for a fractionDigits schema component is a <fractionDigits> element information item. The correspondences between the properties of the information item and properties of the component are as follows:

id = ID

value = nonNegativeInteger

{any attributes with non-schema namespace . . .}>

Content: (annotation?)

</fractionDigits>

PropertyRepresentation{value}

The actual value of the value [attribute]

{fixed}

The actual value of the fixed [attribute], if present, otherwise false

{annotation}

The annotations corresponding to all the <annotation> element information items in the [children], if any.

4.3.12.3 fractionDigits Validation RulesValidation Rule: fractionDigits Valid

A value in a i × 10^-n where i and n are integers and 0 <= n <= {value}. 4.3.12.4 Constraints on fractionDigits Schema ComponentsSchema Component Constraint: fractionDigits less than or equal to totalDigits

It is an Schema Component Constraint: fractionDigits valid restriction

It is an 5 ConformanceThis specification describes two levels of conformance for datatype processors. The first is required of all processors. Support for the other will depend on the application environments for which the processor is intended.

Minimally conforming processors

conformance to the XML Representation of Schemas, and

Note: By separating the conformance requirements relating to the concrete syntax of XML schema documents, this specification admits processors which validate using schemas stored in optimized binary representations, dynamically created schemas represented as programming language data structures, or implementations in which particular schemas are compiled into executable code such as C or Java. Such processors can be said to be A Schema for Datatype Definitions (normative)<!DOCTYPE xs:schema PUBLIC "-//W3C//DTD XMLSCHEMA 200102//EN" "XMLSchema.dtd" [ <!ENTITY % schemaAttrs 'xmlns:hfp CDATA #IMPLIED'> <!ELEMENT hfp:hasFacet EMPTY> <!ATTLIST hfp:hasFacet name NMTOKEN #REQUIRED> <!ELEMENT hfp:hasProperty EMPTY> <!ATTLIST hfp:hasProperty name NMTOKEN #REQUIRED value CDATA #REQUIRED> <!ATTLIST xs:simpleType id ID #IMPLIED> <!ATTLIST xs:maxExclusive id ID #IMPLIED> <!ATTLIST xs:minExclusive id ID #IMPLIED> <!ATTLIST xs:maxInclusive id ID #IMPLIED> <!ATTLIST xs:minInclusive id ID #IMPLIED> <!ATTLIST xs:totalDigits id ID #IMPLIED> <!ATTLIST xs:fractionDigits id ID #IMPLIED> <!ATTLIST xs:length id ID #IMPLIED> <!ATTLIST xs:minLength id ID #IMPLIED> <!ATTLIST xs:maxLength id ID #IMPLIED> <!ATTLIST xs:enumeration id ID #IMPLIED> <!ATTLIST xs:pattern id ID #IMPLIED> <!ATTLIST xs:appinfo id ID #IMPLIED> <!ATTLIST xs:documentation id ID #IMPLIED> <!ATTLIST xs:list id ID #IMPLIED> <!ATTLIST xs:union id ID #IMPLIED> ]><?xml version='1.0'?><xs:schema xmlns:hfp="http://www.w3.org/2001/XMLSchema-hasFacetAndProperty" xmlns:xs="http://www.w3.org/2001/XMLSchema" blockDefault="#all" elementFormDefault="qualified" xml:lang="en" targetNamespace="http://www.w3.org/2001/XMLSchema" version="Id: datatypes.xsd,v 1.4 2004/05/29 10:26:33 ht Exp "> <xs:annotation> <xs:documentation source="../datatypes/datatypes-with-errata.html"> The schema corresponding to this document is normative, with respect to the syntactic constraints it expresses in the XML Schema language. The documentation (within <documentation> elements) below, is not normative, but rather highlights important aspects of the W3C Recommendation of which this is a part </xs:documentation> </xs:annotation> <xs:annotation> <xs:documentation> First the built-in primitive datatypes. These definitions are for information only, the real built-in definitions are magic. </xs:documentation> <xs:documentation> For each built-in datatype in this schema (both primitive and derived) can be uniquely addressed via a URI constructed as follows: 1) the base URI is the URI of the XML Schema namespace 2) the fragment identifier is the name of the datatype For example, to address the int datatype, the URI is: http://www.w3.org/2001/XMLSchema#int Additionally, each facet definition element can be uniquely addressed via a URI constructed as follows: 1) the base URI is the URI of the XML Schema namespace 2) the fragment identifier is the name of the facet For example, to address the maxInclusive facet, the URI is: http://www.w3.org/2001/XMLSchema#maxInclusive Additionally, each facet usage in a built-in datatype definition can be uniquely addressed via a URI constructed as follows: 1) the base URI is the URI of the XML Schema namespace 2) the fragment identifier is the name of the datatype, followed by a period (".") followed by the name of the facet For example, to address the usage of the maxInclusive facet in the definition of int, the URI is: http://www.w3.org/2001/XMLSchema#int.maxInclusive </xs:documentation> </xs:annotation> <xs:simpleType name="string" id="string"> <xs:annotation> <xs:appinfo> <hfp:hasFacet name="length"/> <hfp:hasFacet name="minLength"/> <hfp:hasFacet name="maxLength"/> <hfp:hasFacet name="pattern"/> <hfp:hasFacet name="enumeration"/> <hfp:hasFacet name="whiteSpace"/> <hfp:hasProperty name="ordered" value="false"/> <hfp:hasProperty name="bounded" value="false"/> <hfp:hasProperty name="cardinality" value="countably infinite"/> <hfp:hasProperty name="numeric" value="false"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#string"/> </xs:annotation> <xs:restriction base="xs:anySimpleType"> <xs:whiteSpace value="preserve" id="string.preserve"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="boolean" id="boolean"> <xs:annotation> <xs:appinfo> <hfp:hasFacet name="pattern"/> <hfp:hasFacet name="whiteSpace"/> <hfp:hasProperty name="ordered" value="false"/> <hfp:hasProperty name="bounded" value="false"/> <hfp:hasProperty name="cardinality" value="finite"/> <hfp:hasProperty name="numeric" value="false"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#boolean"/> </xs:annotation> <xs:restriction base="xs:anySimpleType"> <xs:whiteSpace fixed="true" value="collapse" id="boolean.whiteSpace"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="float" id="float"> <xs:annotation> <xs:appinfo> <hfp:hasFacet name="pattern"/> <hfp:hasFacet name="enumeration"/> <hfp:hasFacet name="whiteSpace"/> <hfp:hasFacet name="maxInclusive"/> <hfp:hasFacet name="maxExclusive"/> <hfp:hasFacet name="minInclusive"/> <hfp:hasFacet name="minExclusive"/> <hfp:hasProperty name="ordered" value="partial"/> <hfp:hasProperty name="bounded" value="true"/> <hfp:hasProperty name="cardinality" value="finite"/> <hfp:hasProperty name="numeric" value="true"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#float"/> </xs:annotation> <xs:restriction base="xs:anySimpleType"> <xs:whiteSpace fixed="true" value="collapse" id="float.whiteSpace"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="double" id="double"> <xs:annotation> <xs:appinfo> <hfp:hasFacet name="pattern"/> <hfp:hasFacet name="enumeration"/> <hfp:hasFacet name="whiteSpace"/> <hfp:hasFacet name="maxInclusive"/> <hfp:hasFacet name="maxExclusive"/> <hfp:hasFacet name="minInclusive"/> <hfp:hasFacet name="minExclusive"/> <hfp:hasProperty name="ordered" value="partial"/> <hfp:hasProperty name="bounded" value="true"/> <hfp:hasProperty name="cardinality" value="finite"/> <hfp:hasProperty name="numeric" value="true"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#double"/> </xs:annotation> <xs:restriction base="xs:anySimpleType"> <xs:whiteSpace fixed="true" value="collapse" id="double.whiteSpace"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="decimal" id="decimal"> <xs:annotation> <xs:appinfo> <hfp:hasFacet name="totalDigits"/> <hfp:hasFacet name="fractionDigits"/> <hfp:hasFacet name="pattern"/> <hfp:hasFacet name="whiteSpace"/> <hfp:hasFacet name="enumeration"/> <hfp:hasFacet name="maxInclusive"/> <hfp:hasFacet name="maxExclusive"/> <hfp:hasFacet name="minInclusive"/> <hfp:hasFacet name="minExclusive"/> <hfp:hasProperty name="ordered" value="total"/> <hfp:hasProperty name="bounded" value="false"/> <hfp:hasProperty name="cardinality" value="countably infinite"/> <hfp:hasProperty name="numeric" value="true"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#decimal"/> </xs:annotation> <xs:restriction base="xs:anySimpleType"> <xs:whiteSpace fixed="true" value="collapse" id="decimal.whiteSpace"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="duration" id="duration"> <xs:annotation> <xs:appinfo> <hfp:hasFacet name="pattern"/> <hfp:hasFacet name="enumeration"/> <hfp:hasFacet name="whiteSpace"/> <hfp:hasFacet name="maxInclusive"/> <hfp:hasFacet name="maxExclusive"/> <hfp:hasFacet name="minInclusive"/> <hfp:hasFacet name="minExclusive"/> <hfp:hasProperty name="ordered" value="partial"/> <hfp:hasProperty name="bounded" value="false"/> <hfp:hasProperty name="cardinality" value="countably infinite"/> <hfp:hasProperty name="numeric" value="false"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#duration"/> </xs:annotation> <xs:restriction base="xs:anySimpleType"> <xs:whiteSpace fixed="true" value="collapse" id="duration.whiteSpace"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="dateTime" id="dateTime"> <xs:annotation> <xs:appinfo> <hfp:hasFacet name="pattern"/> <hfp:hasFacet name="enumeration"/> <hfp:hasFacet name="whiteSpace"/> <hfp:hasFacet name="maxInclusive"/> <hfp:hasFacet name="maxExclusive"/> <hfp:hasFacet name="minInclusive"/> <hfp:hasFacet name="minExclusive"/> <hfp:hasProperty name="ordered" value="partial"/> <hfp:hasProperty name="bounded" value="false"/> <hfp:hasProperty name="cardinality" value="countably infinite"/> <hfp:hasProperty name="numeric" value="false"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#dateTime"/> </xs:annotation> <xs:restriction base="xs:anySimpleType"> <xs:whiteSpace fixed="true" value="collapse" id="dateTime.whiteSpace"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="time" id="time"> <xs:annotation> <xs:appinfo> <hfp:hasFacet name="pattern"/> <hfp:hasFacet name="enumeration"/> <hfp:hasFacet name="whiteSpace"/> <hfp:hasFacet name="maxInclusive"/> <hfp:hasFacet name="maxExclusive"/> <hfp:hasFacet name="minInclusive"/> <hfp:hasFacet name="minExclusive"/> <hfp:hasProperty name="ordered" value="partial"/> <hfp:hasProperty name="bounded" value="false"/> <hfp:hasProperty name="cardinality" value="countably infinite"/> <hfp:hasProperty name="numeric" value="false"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#time"/> </xs:annotation> <xs:restriction base="xs:anySimpleType"> <xs:whiteSpace fixed="true" value="collapse" id="time.whiteSpace"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="date" id="date"> <xs:annotation> <xs:appinfo> <hfp:hasFacet name="pattern"/> <hfp:hasFacet name="enumeration"/> <hfp:hasFacet name="whiteSpace"/> <hfp:hasFacet name="maxInclusive"/> <hfp:hasFacet name="maxExclusive"/> <hfp:hasFacet name="minInclusive"/> <hfp:hasFacet name="minExclusive"/> <hfp:hasProperty name="ordered" value="partial"/> <hfp:hasProperty name="bounded" value="false"/> <hfp:hasProperty name="cardinality" value="countably infinite"/> <hfp:hasProperty name="numeric" value="false"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#date"/> </xs:annotation> <xs:restriction base="xs:anySimpleType"> <xs:whiteSpace fixed="true" value="collapse" id="date.whiteSpace"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="gYearMonth" id="gYearMonth"> <xs:annotation> <xs:appinfo> <hfp:hasFacet name="pattern"/> <hfp:hasFacet name="enumeration"/> <hfp:hasFacet name="whiteSpace"/> <hfp:hasFacet name="maxInclusive"/> <hfp:hasFacet name="maxExclusive"/> <hfp:hasFacet name="minInclusive"/> <hfp:hasFacet name="minExclusive"/> <hfp:hasProperty name="ordered" value="partial"/> <hfp:hasProperty name="bounded" value="false"/> <hfp:hasProperty name="cardinality" value="countably infinite"/> <hfp:hasProperty name="numeric" value="false"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#gYearMonth"/> </xs:annotation> <xs:restriction base="xs:anySimpleType"> <xs:whiteSpace fixed="true" value="collapse" id="gYearMonth.whiteSpace"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="gYear" id="gYear"> <xs:annotation> <xs:appinfo> <hfp:hasFacet name="pattern"/> <hfp:hasFacet name="enumeration"/> <hfp:hasFacet name="whiteSpace"/> <hfp:hasFacet name="maxInclusive"/> <hfp:hasFacet name="maxExclusive"/> <hfp:hasFacet name="minInclusive"/> <hfp:hasFacet name="minExclusive"/> <hfp:hasProperty name="ordered" value="partial"/> <hfp:hasProperty name="bounded" value="false"/> <hfp:hasProperty name="cardinality" value="countably infinite"/> <hfp:hasProperty name="numeric" value="false"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#gYear"/> </xs:annotation> <xs:restriction base="xs:anySimpleType"> <xs:whiteSpace fixed="true" value="collapse" id="gYear.whiteSpace"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="gMonthDay" id="gMonthDay"> <xs:annotation> <xs:appinfo> <hfp:hasFacet name="pattern"/> <hfp:hasFacet name="enumeration"/> <hfp:hasFacet name="whiteSpace"/> <hfp:hasFacet name="maxInclusive"/> <hfp:hasFacet name="maxExclusive"/> <hfp:hasFacet name="minInclusive"/> <hfp:hasFacet name="minExclusive"/> <hfp:hasProperty name="ordered" value="partial"/> <hfp:hasProperty name="bounded" value="false"/> <hfp:hasProperty name="cardinality" value="countably infinite"/> <hfp:hasProperty name="numeric" value="false"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#gMonthDay"/> </xs:annotation> <xs:restriction base="xs:anySimpleType"> <xs:whiteSpace fixed="true" value="collapse" id="gMonthDay.whiteSpace"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="gDay" id="gDay"> <xs:annotation> <xs:appinfo> <hfp:hasFacet name="pattern"/> <hfp:hasFacet name="enumeration"/> <hfp:hasFacet name="whiteSpace"/> <hfp:hasFacet name="maxInclusive"/> <hfp:hasFacet name="maxExclusive"/> <hfp:hasFacet name="minInclusive"/> <hfp:hasFacet name="minExclusive"/> <hfp:hasProperty name="ordered" value="partial"/> <hfp:hasProperty name="bounded" value="false"/> <hfp:hasProperty name="cardinality" value="countably infinite"/> <hfp:hasProperty name="numeric" value="false"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#gDay"/> </xs:annotation> <xs:restriction base="xs:anySimpleType"> <xs:whiteSpace fixed="true" value="collapse" id="gDay.whiteSpace"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="gMonth" id="gMonth"> <xs:annotation> <xs:appinfo> <hfp:hasFacet name="pattern"/> <hfp:hasFacet name="enumeration"/> <hfp:hasFacet name="whiteSpace"/> <hfp:hasFacet name="maxInclusive"/> <hfp:hasFacet name="maxExclusive"/> <hfp:hasFacet name="minInclusive"/> <hfp:hasFacet name="minExclusive"/> <hfp:hasProperty name="ordered" value="partial"/> <hfp:hasProperty name="bounded" value="false"/> <hfp:hasProperty name="cardinality" value="countably infinite"/> <hfp:hasProperty name="numeric" value="false"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#gMonth"/> </xs:annotation> <xs:restriction base="xs:anySimpleType"> <xs:whiteSpace fixed="true" value="collapse" id="gMonth.whiteSpace"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="hexBinary" id="hexBinary"> <xs:annotation> <xs:appinfo> <hfp:hasFacet name="length"/> <hfp:hasFacet name="minLength"/> <hfp:hasFacet name="maxLength"/> <hfp:hasFacet name="pattern"/> <hfp:hasFacet name="enumeration"/> <hfp:hasFacet name="whiteSpace"/> <hfp:hasProperty name="ordered" value="false"/> <hfp:hasProperty name="bounded" value="false"/> <hfp:hasProperty name="cardinality" value="countably infinite"/> <hfp:hasProperty name="numeric" value="false"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#binary"/> </xs:annotation> <xs:restriction base="xs:anySimpleType"> <xs:whiteSpace fixed="true" value="collapse" id="hexBinary.whiteSpace"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="base64Binary" id="base64Binary"> <xs:annotation> <xs:appinfo> <hfp:hasFacet name="length"/> <hfp:hasFacet name="minLength"/> <hfp:hasFacet name="maxLength"/> <hfp:hasFacet name="pattern"/> <hfp:hasFacet name="enumeration"/> <hfp:hasFacet name="whiteSpace"/> <hfp:hasProperty name="ordered" value="false"/> <hfp:hasProperty name="bounded" value="false"/> <hfp:hasProperty name="cardinality" value="countably infinite"/> <hfp:hasProperty name="numeric" value="false"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#base64Binary"/> </xs:annotation> <xs:restriction base="xs:anySimpleType"> <xs:whiteSpace fixed="true" value="collapse" id="base64Binary.whiteSpace"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="anyURI" id="anyURI"> <xs:annotation> <xs:appinfo> <hfp:hasFacet name="length"/> <hfp:hasFacet name="minLength"/> <hfp:hasFacet name="maxLength"/> <hfp:hasFacet name="pattern"/> <hfp:hasFacet name="enumeration"/> <hfp:hasFacet name="whiteSpace"/> <hfp:hasProperty name="ordered" value="false"/> <hfp:hasProperty name="bounded" value="false"/> <hfp:hasProperty name="cardinality" value="countably infinite"/> <hfp:hasProperty name="numeric" value="false"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#anyURI"/> </xs:annotation> <xs:restriction base="xs:anySimpleType"> <xs:whiteSpace fixed="true" value="collapse" id="anyURI.whiteSpace"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="QName" id="QName"> <xs:annotation> <xs:appinfo> <hfp:hasFacet name="length"/> <hfp:hasFacet name="minLength"/> <hfp:hasFacet name="maxLength"/> <hfp:hasFacet name="pattern"/> <hfp:hasFacet name="enumeration"/> <hfp:hasFacet name="whiteSpace"/> <hfp:hasProperty name="ordered" value="false"/> <hfp:hasProperty name="bounded" value="false"/> <hfp:hasProperty name="cardinality" value="countably infinite"/> <hfp:hasProperty name="numeric" value="false"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#QName"/> </xs:annotation> <xs:restriction base="xs:anySimpleType"> <xs:whiteSpace fixed="true" value="collapse" id="QName.whiteSpace"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="NOTATION" id="NOTATION"> <xs:annotation> <xs:appinfo> <hfp:hasFacet name="length"/> <hfp:hasFacet name="minLength"/> <hfp:hasFacet name="maxLength"/> <hfp:hasFacet name="pattern"/> <hfp:hasFacet name="enumeration"/> <hfp:hasFacet name="whiteSpace"/> <hfp:hasProperty name="ordered" value="false"/> <hfp:hasProperty name="bounded" value="false"/> <hfp:hasProperty name="cardinality" value="countably infinite"/> <hfp:hasProperty name="numeric" value="false"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#NOTATION"/> <xs:documentation> NOTATION cannot be used directly in a schema; rather a type must be derived from it by specifying at least one enumeration facet whose value is the name of a NOTATION declared in the schema. </xs:documentation> </xs:annotation> <xs:restriction base="xs:anySimpleType"> <xs:whiteSpace fixed="true" value="collapse" id="NOTATION.whiteSpace"/> </xs:restriction> </xs:simpleType> <xs:annotation> <xs:documentation> Now the derived primitive types </xs:documentation> </xs:annotation> <xs:simpleType name="normalizedString" id="normalizedString"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#normalizedString"/> </xs:annotation> <xs:restriction base="xs:string"> <xs:whiteSpace value="replace" id="normalizedString.whiteSpace"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="token" id="token"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#token"/> </xs:annotation> <xs:restriction base="xs:normalizedString"> <xs:whiteSpace value="collapse" id="token.whiteSpace"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="language" id="language"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#language"/> </xs:annotation> <xs:restriction base="xs:token"> <xs:pattern value="[a-zA-Z]{1,8}(-[a-zA-Z0-9]{1,8})*" id="language.pattern"> <xs:annotation> <xs:documentation source="http://www.ietf.org/rfc/rfc3066.txt"> pattern specifies the content of section 2.12 of XML 1.0e2 and RFC 3066 (Revised version of RFC 1766). </xs:documentation> </xs:annotation> </xs:pattern> </xs:restriction> </xs:simpleType> <xs:simpleType name="IDREFS" id="IDREFS"> <xs:annotation> <xs:appinfo> <hfp:hasFacet name="length"/> <hfp:hasFacet name="minLength"/> <hfp:hasFacet name="maxLength"/> <hfp:hasFacet name="enumeration"/> <hfp:hasFacet name="whiteSpace"/> <hfp:hasFacet name="pattern"/> <hfp:hasProperty name="ordered" value="false"/> <hfp:hasProperty name="bounded" value="false"/> <hfp:hasProperty name="cardinality" value="countably infinite"/> <hfp:hasProperty name="numeric" value="false"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#IDREFS"/> </xs:annotation> <xs:restriction> <xs:simpleType> <xs:list itemType="xs:IDREF"/> </xs:simpleType> <xs:minLength value="1" id="IDREFS.minLength"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="ENTITIES" id="ENTITIES"> <xs:annotation> <xs:appinfo> <hfp:hasFacet name="length"/> <hfp:hasFacet name="minLength"/> <hfp:hasFacet name="maxLength"/> <hfp:hasFacet name="enumeration"/> <hfp:hasFacet name="whiteSpace"/> <hfp:hasFacet name="pattern"/> <hfp:hasProperty name="ordered" value="false"/> <hfp:hasProperty name="bounded" value="false"/> <hfp:hasProperty name="cardinality" value="countably infinite"/> <hfp:hasProperty name="numeric" value="false"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#ENTITIES"/> </xs:annotation> <xs:restriction> <xs:simpleType> <xs:list itemType="xs:ENTITY"/> </xs:simpleType> <xs:minLength value="1" id="ENTITIES.minLength"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="NMTOKEN" id="NMTOKEN"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#NMTOKEN"/> </xs:annotation> <xs:restriction base="xs:token"> <xs:pattern value="\c+" id="NMTOKEN.pattern"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/REC-xml#NT-Nmtoken"> pattern matches production 7 from the XML spec </xs:documentation> </xs:annotation> </xs:pattern> </xs:restriction> </xs:simpleType> <xs:simpleType name="NMTOKENS" id="NMTOKENS"> <xs:annotation> <xs:appinfo> <hfp:hasFacet name="length"/> <hfp:hasFacet name="minLength"/> <hfp:hasFacet name="maxLength"/> <hfp:hasFacet name="enumeration"/> <hfp:hasFacet name="whiteSpace"/> <hfp:hasFacet name="pattern"/> <hfp:hasProperty name="ordered" value="false"/> <hfp:hasProperty name="bounded" value="false"/> <hfp:hasProperty name="cardinality" value="countably infinite"/> <hfp:hasProperty name="numeric" value="false"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#NMTOKENS"/> </xs:annotation> <xs:restriction> <xs:simpleType> <xs:list itemType="xs:NMTOKEN"/> </xs:simpleType> <xs:minLength value="1" id="NMTOKENS.minLength"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="Name" id="Name"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#Name"/> </xs:annotation> <xs:restriction base="xs:token"> <xs:pattern value="\i\c*" id="Name.pattern"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/REC-xml#NT-Name"> pattern matches production 5 from the XML spec </xs:documentation> </xs:annotation> </xs:pattern> </xs:restriction> </xs:simpleType> <xs:simpleType name="NCName" id="NCName"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#NCName"/> </xs:annotation> <xs:restriction base="xs:Name"> <xs:pattern value="[\i-[:]][\c-[:]]*" id="NCName.pattern"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/REC-xml-names/#NT-NCName"> pattern matches production 4 from the Namespaces in XML spec </xs:documentation> </xs:annotation> </xs:pattern> </xs:restriction> </xs:simpleType> <xs:simpleType name="ID" id="ID"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#ID"/> </xs:annotation> <xs:restriction base="xs:NCName"/> </xs:simpleType> <xs:simpleType name="IDREF" id="IDREF"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#IDREF"/> </xs:annotation> <xs:restriction base="xs:NCName"/> </xs:simpleType> <xs:simpleType name="ENTITY" id="ENTITY"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#ENTITY"/> </xs:annotation> <xs:restriction base="xs:NCName"/> </xs:simpleType> <xs:simpleType name="integer" id="integer"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#integer"/> </xs:annotation> <xs:restriction base="xs:decimal"> <xs:fractionDigits fixed="true" value="0" id="integer.fractionDigits"/> <xs:pattern value="[\-+]?[0-9]+"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="nonPositiveInteger" id="nonPositiveInteger"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#nonPositiveInteger"/> </xs:annotation> <xs:restriction base="xs:integer"> <xs:maxInclusive value="0" id="nonPositiveInteger.maxInclusive"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="negativeInteger" id="negativeInteger"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#negativeInteger"/> </xs:annotation> <xs:restriction base="xs:nonPositiveInteger"> <xs:maxInclusive value="-1" id="negativeInteger.maxInclusive"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="long" id="long"> <xs:annotation> <xs:appinfo> <hfp:hasProperty name="bounded" value="true"/> <hfp:hasProperty name="cardinality" value="finite"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#long"/> </xs:annotation> <xs:restriction base="xs:integer"> <xs:minInclusive value="-9223372036854775808" id="long.minInclusive"/> <xs:maxInclusive value="9223372036854775807" id="long.maxInclusive"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="int" id="int"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#int"/> </xs:annotation> <xs:restriction base="xs:long"> <xs:minInclusive value="-2147483648" id="int.minInclusive"/> <xs:maxInclusive value="2147483647" id="int.maxInclusive"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="short" id="short"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#short"/> </xs:annotation> <xs:restriction base="xs:int"> <xs:minInclusive value="-32768" id="short.minInclusive"/> <xs:maxInclusive value="32767" id="short.maxInclusive"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="byte" id="byte"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#byte"/> </xs:annotation> <xs:restriction base="xs:short"> <xs:minInclusive value="-128" id="byte.minInclusive"/> <xs:maxInclusive value="127" id="byte.maxInclusive"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="nonNegativeInteger" id="nonNegativeInteger"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#nonNegativeInteger"/> </xs:annotation> <xs:restriction base="xs:integer"> <xs:minInclusive value="0" id="nonNegativeInteger.minInclusive"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="unsignedLong" id="unsignedLong"> <xs:annotation> <xs:appinfo> <hfp:hasProperty name="bounded" value="true"/> <hfp:hasProperty name="cardinality" value="finite"/> </xs:appinfo> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#unsignedLong"/> </xs:annotation> <xs:restriction base="xs:nonNegativeInteger"> <xs:maxInclusive value="18446744073709551615" id="unsignedLong.maxInclusive"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="unsignedInt" id="unsignedInt"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#unsignedInt"/> </xs:annotation> <xs:restriction base="xs:unsignedLong"> <xs:maxInclusive value="4294967295" id="unsignedInt.maxInclusive"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="unsignedShort" id="unsignedShort"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#unsignedShort"/> </xs:annotation> <xs:restriction base="xs:unsignedInt"> <xs:maxInclusive value="65535" id="unsignedShort.maxInclusive"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="unsignedByte" id="unsignedByte"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#unsignedByte"/> </xs:annotation> <xs:restriction base="xs:unsignedShort"> <xs:maxInclusive value="255" id="unsignedByte.maxInclusive"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="positiveInteger" id="positiveInteger"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#positiveInteger"/> </xs:annotation> <xs:restriction base="xs:nonNegativeInteger"> <xs:minInclusive value="1" id="positiveInteger.minInclusive"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="derivationControl"> <xs:annotation> <xs:documentation> A utility type, not for public use</xs:documentation> </xs:annotation> <xs:restriction base="xs:NMTOKEN"> <xs:enumeration value="substitution"/> <xs:enumeration value="extension"/> <xs:enumeration value="restriction"/> <xs:enumeration value="list"/> <xs:enumeration value="union"/> </xs:restriction> </xs:simpleType> <xs:group name="simpleDerivation"> <xs:choice> <xs:element ref="xs:restriction"/> <xs:element ref="xs:list"/> <xs:element ref="xs:union"/> </xs:choice> </xs:group> <xs:simpleType name="simpleDerivationSet"> <xs:annotation> <xs:documentation> #all or (possibly empty) subset of {restriction, union, list} </xs:documentation> <xs:documentation> A utility type, not for public use</xs:documentation> </xs:annotation> <xs:union> <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value="#all"/> </xs:restriction> </xs:simpleType> <xs:simpleType> <xs:list> <xs:simpleType> <xs:restriction base="xs:derivationControl"> <xs:enumeration value="list"/> <xs:enumeration value="union"/> <xs:enumeration value="restriction"/> </xs:restriction> </xs:simpleType> </xs:list> </xs:simpleType> </xs:union> </xs:simpleType> <xs:complexType name="simpleType" abstract="true"> <xs:complexContent> <xs:extension base="xs:annotated"> <xs:group ref="xs:simpleDerivation"/> <xs:attribute name="final" type="xs:simpleDerivationSet"/> <xs:attribute name="name" type="xs:NCName"> <xs:annotation> <xs:documentation> Can be restricted to required or forbidden </xs:documentation> </xs:annotation> </xs:attribute> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="topLevelSimpleType"> <xs:complexContent> <xs:restriction base="xs:simpleType"> <xs:sequence> <xs:element ref="xs:annotation" minOccurs="0"/> <xs:group ref="xs:simpleDerivation"/> </xs:sequence> <xs:attribute name="name" type="xs:NCName" use="required"> <xs:annotation> <xs:documentation> Required at the top level </xs:documentation> </xs:annotation> </xs:attribute> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:restriction> </xs:complexContent> </xs:complexType> <xs:complexType name="localSimpleType"> <xs:complexContent> <xs:restriction base="xs:simpleType"> <xs:sequence> <xs:element ref="xs:annotation" minOccurs="0"/> <xs:group ref="xs:simpleDerivation"/> </xs:sequence> <xs:attribute name="name" use="prohibited"> <xs:annotation> <xs:documentation> Forbidden when nested </xs:documentation> </xs:annotation> </xs:attribute> <xs:attribute name="final" use="prohibited"/> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:restriction> </xs:complexContent> </xs:complexType> <xs:element name="simpleType" type="xs:topLevelSimpleType" id="simpleType"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#element-simpleType"/> </xs:annotation> </xs:element> <xs:group name="facets"> <xs:annotation> <xs:documentation> We should use a substitution group for facets, but that's ruled out because it would allow users to add their own, which we're not ready for yet. </xs:documentation> </xs:annotation> <xs:choice> <xs:element ref="xs:minExclusive"/> <xs:element ref="xs:minInclusive"/> <xs:element ref="xs:maxExclusive"/> <xs:element ref="xs:maxInclusive"/> <xs:element ref="xs:totalDigits"/> <xs:element ref="xs:fractionDigits"/> <xs:element ref="xs:length"/> <xs:element ref="xs:minLength"/> <xs:element ref="xs:maxLength"/> <xs:element ref="xs:enumeration"/> <xs:element ref="xs:whiteSpace"/> <xs:element ref="xs:pattern"/> </xs:choice> </xs:group> <xs:group name="simpleRestrictionModel"> <xs:sequence> <xs:element name="simpleType" type="xs:localSimpleType" minOccurs="0"/> <xs:group ref="xs:facets" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:group> <xs:element name="restriction" id="restriction"> <xs:complexType> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#element-restriction"> base attribute and simpleType child are mutually exclusive, but one or other is required </xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="xs:annotated"> <xs:group ref="xs:simpleRestrictionModel"/> <xs:attribute name="base" type="xs:QName" use="optional"/> </xs:extension> </xs:complexContent> </xs:complexType> </xs:element> <xs:element name="list" id="list"> <xs:complexType> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#element-list"> itemType attribute and simpleType child are mutually exclusive, but one or other is required </xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="xs:annotated"> <xs:sequence> <xs:element name="simpleType" type="xs:localSimpleType" minOccurs="0"/> </xs:sequence> <xs:attribute name="itemType" type="xs:QName" use="optional"/> </xs:extension> </xs:complexContent> </xs:complexType> </xs:element> <xs:element name="union" id="union"> <xs:complexType> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#element-union"> memberTypes attribute must be non-empty or there must be at least one simpleType child </xs:documentation> </xs:annotation> <xs:complexContent> <xs:extension base="xs:annotated"> <xs:sequence> <xs:element name="simpleType" type="xs:localSimpleType" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="memberTypes" use="optional"> <xs:simpleType> <xs:list itemType="xs:QName"/> </xs:simpleType> </xs:attribute> </xs:extension> </xs:complexContent> </xs:complexType> </xs:element> <xs:complexType name="facet"> <xs:complexContent> <xs:extension base="xs:annotated"> <xs:attribute name="value" use="required"/> <xs:attribute name="fixed" type="xs:boolean" default="false" use="optional"/> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="noFixedFacet"> <xs:complexContent> <xs:restriction base="xs:facet"> <xs:sequence> <xs:element ref="xs:annotation" minOccurs="0"/> </xs:sequence> <xs:attribute name="fixed" use="prohibited"/> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:restriction> </xs:complexContent> </xs:complexType> <xs:element name="minExclusive" type="xs:facet" id="minExclusive"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#element-minExclusive"/> </xs:annotation> </xs:element> <xs:element name="minInclusive" type="xs:facet" id="minInclusive"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#element-minInclusive"/> </xs:annotation> </xs:element> <xs:element name="maxExclusive" type="xs:facet" id="maxExclusive"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#element-maxExclusive"/> </xs:annotation> </xs:element> <xs:element name="maxInclusive" type="xs:facet" id="maxInclusive"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#element-maxInclusive"/> </xs:annotation> </xs:element> <xs:complexType name="numFacet"> <xs:complexContent> <xs:restriction base="xs:facet"> <xs:sequence> <xs:element ref="xs:annotation" minOccurs="0"/> </xs:sequence> <xs:attribute name="value" type="xs:nonNegativeInteger" use="required"/> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:restriction> </xs:complexContent> </xs:complexType> <xs:element name="totalDigits" id="totalDigits"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#element-totalDigits"/> </xs:annotation> <xs:complexType> <xs:complexContent> <xs:restriction base="xs:numFacet"> <xs:sequence> <xs:element ref="xs:annotation" minOccurs="0"/> </xs:sequence> <xs:attribute name="value" type="xs:positiveInteger" use="required"/> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:restriction> </xs:complexContent> </xs:complexType> </xs:element> <xs:element name="fractionDigits" type="xs:numFacet" id="fractionDigits"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#element-fractionDigits"/> </xs:annotation> </xs:element> <xs:element name="length" type="xs:numFacet" id="length"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#element-length"/> </xs:annotation> </xs:element> <xs:element name="minLength" type="xs:numFacet" id="minLength"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#element-minLength"/> </xs:annotation> </xs:element> <xs:element name="maxLength" type="xs:numFacet" id="maxLength"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#element-maxLength"/> </xs:annotation> </xs:element> <xs:element name="enumeration" type="xs:noFixedFacet" id="enumeration"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#element-enumeration"/> </xs:annotation> </xs:element> <xs:element name="whiteSpace" id="whiteSpace"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#element-whiteSpace"/> </xs:annotation> <xs:complexType> <xs:complexContent> <xs:restriction base="xs:facet"> <xs:sequence> <xs:element ref="xs:annotation" minOccurs="0"/> </xs:sequence> <xs:attribute name="value" use="required"> <xs:simpleType> <xs:restriction base="xs:NMTOKEN"> <xs:enumeration value="preserve"/> <xs:enumeration value="replace"/> <xs:enumeration value="collapse"/> </xs:restriction> </xs:simpleType> </xs:attribute> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:restriction> </xs:complexContent> </xs:complexType> </xs:element> <xs:element name="pattern" id="pattern"> <xs:annotation> <xs:documentation source="http://www.w3.org/TR/xmlschema-2/#element-pattern"/> </xs:annotation> <xs:complexType> <xs:complexContent> <xs:restriction base="xs:noFixedFacet"> <xs:sequence> <xs:element ref="xs:annotation" minOccurs="0"/> </xs:sequence> <xs:attribute name="value" type="xs:string" use="required"/> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:restriction> </xs:complexContent> </xs:complexType> </xs:element></xs:schema>

B DTD for Datatype Definitions (non-normative)<!ENTITY % simpleType "%p;simpleType"><!ENTITY % restriction "%p;restriction"><!ENTITY % list "%p;list"><!ENTITY % union "%p;union"><!ENTITY % maxExclusive "%p;maxExclusive"><!ENTITY % minExclusive "%p;minExclusive"><!ENTITY % maxInclusive "%p;maxInclusive"><!ENTITY % minInclusive "%p;minInclusive"><!ENTITY % totalDigits "%p;totalDigits"><!ENTITY % fractionDigits "%p;fractionDigits"><!ENTITY % length "%p;length"><!ENTITY % minLength "%p;minLength"><!ENTITY % maxLength "%p;maxLength"><!ENTITY % enumeration "%p;enumeration"><!ENTITY % whiteSpace "%p;whiteSpace"><!ENTITY % pattern "%p;pattern"><!ENTITY % simpleTypeAttrs ""><!ENTITY % restrictionAttrs ""><!ENTITY % listAttrs ""><!ENTITY % unionAttrs ""><!ENTITY % maxExclusiveAttrs ""><!ENTITY % minExclusiveAttrs ""><!ENTITY % maxInclusiveAttrs ""><!ENTITY % minInclusiveAttrs ""><!ENTITY % totalDigitsAttrs ""><!ENTITY % fractionDigitsAttrs ""><!ENTITY % lengthAttrs ""><!ENTITY % minLengthAttrs ""><!ENTITY % maxLengthAttrs ""><!ENTITY % enumerationAttrs ""><!ENTITY % whiteSpaceAttrs ""><!ENTITY % patternAttrs ""><!ENTITY % URIref "CDATA"><!ENTITY % XPathExpr "CDATA"><!ENTITY % QName "NMTOKEN"><!ENTITY % QNames "NMTOKENS"><!ENTITY % NCName "NMTOKEN"><!ENTITY % nonNegativeInteger "NMTOKEN"><!ENTITY % boolean "(true|false)"><!ENTITY % simpleDerivationSet "CDATA"><!ENTITY % minBound "(%minInclusive; | %minExclusive;)"><!ENTITY % maxBound "(%maxInclusive; | %maxExclusive;)"><!ENTITY % bounds "%minBound; | %maxBound;"><!ENTITY % numeric "%totalDigits; | %fractionDigits;"><!ENTITY % ordered "%bounds; | %numeric;"><!ENTITY % unordered "%pattern; | %enumeration; | %whiteSpace; | %length; | %maxLength; | %minLength;"><!ENTITY % facet "%ordered; | %unordered;"><!ENTITY % facetAttr "value CDATA #REQUIRED id ID #IMPLIED"><!ENTITY % fixedAttr "fixed %boolean; #IMPLIED"><!ENTITY % facetModel "(%annotation;)?"><!ELEMENT %simpleType; ((%annotation;)?, (%restriction; | %list; | %union;))><!ATTLIST %simpleType; name %NCName; #IMPLIED final %simpleDerivationSet; #IMPLIED id ID #IMPLIED %simpleTypeAttrs;><!ELEMENT %restriction; ((%annotation;)?, (%restriction1; | ((%simpleType;)?,(%facet;)*)), (%attrDecls;))><!ATTLIST %restriction; base %QName; #IMPLIED id ID #IMPLIED %restrictionAttrs;><!ELEMENT %list; ((%annotation;)?,(%simpleType;)?)><!ATTLIST %list; itemType %QName; #IMPLIED id ID #IMPLIED %listAttrs;><!ELEMENT %union; ((%annotation;)?,(%simpleType;)*)><!ATTLIST %union; id ID #IMPLIED memberTypes %QNames; #IMPLIED %unionAttrs;><!ELEMENT %maxExclusive; %facetModel;><!ATTLIST %maxExclusive; %facetAttr; %fixedAttr; %maxExclusiveAttrs;><!ELEMENT %minExclusive; %facetModel;><!ATTLIST %minExclusive; %facetAttr; %fixedAttr; %minExclusiveAttrs;><!ELEMENT %maxInclusive; %facetModel;><!ATTLIST %maxInclusive; %facetAttr; %fixedAttr; %maxInclusiveAttrs;><!ELEMENT %minInclusive; %facetModel;><!ATTLIST %minInclusive; %facetAttr; %fixedAttr; %minInclusiveAttrs;><!ELEMENT %totalDigits; %facetModel;><!ATTLIST %totalDigits; %facetAttr; %fixedAttr; %totalDigitsAttrs;><!ELEMENT %fractionDigits; %facetModel;><!ATTLIST %fractionDigits; %facetAttr; %fixedAttr; %fractionDigitsAttrs;><!ELEMENT %length; %facetModel;><!ATTLIST %length; %facetAttr; %fixedAttr; %lengthAttrs;><!ELEMENT %minLength; %facetModel;><!ATTLIST %minLength; %facetAttr; %fixedAttr; %minLengthAttrs;><!ELEMENT %maxLength; %facetModel;><!ATTLIST %maxLength; %facetAttr; %fixedAttr; %maxLengthAttrs;><!ELEMENT %enumeration; %facetModel;><!ATTLIST %enumeration; %facetAttr; %enumerationAttrs;><!ELEMENT %whiteSpace; %facetModel;><!ATTLIST %whiteSpace; %facetAttr; %fixedAttr; %whiteSpaceAttrs;><!ELEMENT %pattern; %facetModel;><!ATTLIST %pattern; %facetAttr; %patternAttrs;>

C Datatypes and FacetsThe following table shows the values of the fundamental facets for each

Datatypeorderedboundedcardinalitynumericprimitive

string

false

countably infinite

false

boolean

false

finite

false

float

partial

true

finite

true

double

partial

true

finite

true

decimal

total

false

countably infinite

true

duration

partial

false

countably infinite

false

dateTime

partial

false

countably infinite

false

time

partial

false

countably infinite

false

date

partial

false

countably infinite

false

gYearMonth

partial

false

countably infinite

false

gYear

partial

false

countably infinite

false

gMonthDay

partial

false

countably infinite

false

gDay

partial

false

countably infinite

false

gMonth

partial

false

countably infinite

false

hexBinary

false

countably infinite

false

base64Binary

false

countably infinite

false

anyURI

false

countably infinite

false

QName

false

countably infinite

false

NOTATION

false

countably infinite

false

derived

normalizedString

false

countably infinite

false

token

false

countably infinite

false

language

false

countably infinite

false

IDREFS

false

countably infinite

false

ENTITIES

false

countably infinite

false

NMTOKEN

false

countably infinite

false

NMTOKENS

false

countably infinite

false

Name

false

countably infinite

false

NCName

false

countably infinite

false

countably infinite

false

IDREF

false

countably infinite

false

ENTITY

false

countably infinite

false

integer

total

false

countably infinite

true

nonPositiveInteger

total

false

countably infinite

true

negativeInteger

total

false

countably infinite

true

long

total

true

finite

true

int

total

true

finite

true

short

total

true

finite

true

byte

total

true

finite

true

nonNegativeInteger

total

false

countably infinite

true

unsignedLong

total

true

finite

true

unsignedInt

total

true

finite

true

unsignedShort

total

true

finite

true

unsignedByte

total

true

finite

true

positiveInteger

total

false

countably infinite

true

D ISO 8601 Date and Time FormatsD.1 ISO 8601 ConventionsThe

[ISO 8601] "specifies the representation of dates in the proleptic Gregorian calendar and times and representations of periods of time". The proleptic Gregorian calendar includes dates prior to 1582 (the year it came into use as an ecclesiastical calendar). It should be pointed out that the datatypes described in this specification do not cover all the types of data covered by [ISO 8601], nor do they support all the lexical representations for those types of data.

[ISO 8601] lexical formats are described using "pictures" in which characters are used in place of decimal digits. The allowed decimal digits are (#x30-#x39). For the primitive datatypes dateTime, time, date, gYearMonth, gMonthDay, gDay, gMonth and gYear. these characters have the following meanings:

C -- represents a digit used in the thousands and hundreds components, the "century" component, of the time element "year". Legal values are from 0 to 9. Y -- represents a digit used in the tens and units components of the time element "year". Legal values are from 0 to 9. M -- represents a digit used in the time element "month". The two digits in a MM format can have values from 1 to 12. D -- represents a digit used in the time element "day". The two digits in a DD format can have values from 1 to 28 if the month value equals 2, 1 to 29 if the month value equals 2 and the year is a leap year, 1 to 30 if the month value equals 4, 6, 9 or 11, and 1 to 31 if the month value equals 1, 3, 5, 7, 8, 10 or 12. h -- represents a digit used in the time element "hour". The two digits in a hh format can have values from 0 to 24. If the value of the hour element is 24 then the values of the minutes element and the seconds element must be 00 and 00. m -- represents a digit used in the time element "minute". The two digits in a mm format can have values from 0 to 59. s -- represents a digit used in the time element "second". The two digits in a ss format can have values from 0 to 60. In the formats described in this specification the whole number of seconds Strictly speaking, a value of 60 or more is not sensible unless the month and day could represent March 31, June 30, September 30, or December 31 in UTC. Because the leap second is added or subtracted as the last second of the day in UTC time, the long (or short) minute could occur at other times in local time. In cases where the leap second is used with an inappropriate month and day it, and any fractional seconds, should considered as added or subtracted from the following minute.

For all the information items indicated by the above characters, leading zeros are required where indicated.

In addition to the above, certain characters are used as designators and appear as themselves in lexical formats.

T -- is used as time designator to indicate the start of the representation of the time of day in dateTime. Z -- is used as time-zone designator, immediately (without a space) following a data element expressing the time of day in Coordinated Universal Time (UTC) in dateTime, time, date, gYearMonth, gMonthDay, gDay, gMonth, and gYear. In the lexical format for duration the following characters are also used as designators and appear as themselves in lexical formats:

P -- is used as the time duration designator, preceding a data element representing a given duration of time.Y -- follows the number of years in a time duration.M -- follows the number of months or minutes in a time duration.D -- follows the number of days in a time duration.H -- follows the number of hours in a time duration.S -- follows the number of seconds in a time duration.The values of the Year, Month, Day, Hour and Minutes components are not restricted but allow an arbitrary integer. Similarly, the value of the Seconds component allows an arbitrary decimal. Thus, the lexical format for duration and datatypes derived from it does not follow the alternative format of § 5.5.3.2.1 of [ISO 8601].

D.2 Truncated and Reduced Formats[ISO 8601] supports a variety of "truncated" formats in which some of the characters on the left of specific formats, for example, the century, can be omitted. Truncated formats are, in general, not permitted for the datatypes defined in this specification with three exceptions. The time datatype uses a truncated format for dateTime which represents an instant of time that recurs every day. Similarly, the gMonthDay and gDay datatypes use left-truncated formats for date. The datatype gMonth uses a right and left truncated format for date.

[ISO 8601] also supports a variety of "reduced" or right-truncated formats in which some of the characters to the right of specific formats, such as the time specification, can be omitted. Right truncated formats are also, in general, not permitted for the datatypes defined in this specification with the following exceptions: right-truncated representations of dateTime are used as lexical representations for date, gMonth, gYear.

D.3 Deviations from ISO 8601 Formats D.3.1 Sign Allowed

D.3.2 No Year Zero

D.3.3 More Than 9999 Years

D.3.4 Time zone permitted

D.3.1 Sign AllowedAn optional minus sign is allowed immediately preceding, without a space, the lexical representations for duration, dateTime, date, gYearMonth, gYear.

D.3.2 No Year ZeroThe year "0000" is an illegal year value.

D.3.3 More Than 9999 YearsTo accommodate year values greater than 9999, more than four digits are allowed in the year representations of dateTime, date, gYearMonth, and gYear. This follows [ISO 8601:2000 Second Edition].

D.3.4 Time zone permittedThe lexical representations for the datatypes date, gYearMonth, gMonthDay, gDay, gMonth and gYear permit an optional trailing time zone specificiation.

E Adding durations to dateTimesGiven a dateTime S and a duration D, this appendix specifies how to compute a dateTime E where E is the end of the time period with start S and duration D i.e. E = S + D. Such computations are used, for example, to determine whether a dateTime is within a specific time period. This appendix also addresses the addition of durations to the datatypes date, gYearMonth, gYear, gDay and gMonth, which can be viewed as a set of dateTimes. In such cases, the addition is made to the first or starting dateTime in the set.

This is a logical explanation of the process. Actual implementations are free to optimize as long as they produce the same results. The calculation uses the notation S[year] to represent the year field of S, S[month] to represent the month field, and so on. It also depends on the following functions:

fQuotient(a, b) = the greatest integer less than or equal to a/b fQuotient(-1,3) = -1fQuotient(0,3)...fQuotient(2,3) = 0fQuotient(3,3) = 1fQuotient(3.123,3) = 1modulo(a, b) = a - fQuotient(a,b)*b modulo(-1,3) = 2modulo(0,3)...modulo(2,3) = 0...2modulo(3,3) = 0modulo(3.123,3) = 0.123fQuotient(a, low, high) = fQuotient(a - low, high - low) fQuotient(0, 1, 13) = -1fQuotient(1, 1, 13) ... fQuotient(12, 1, 13) = 0fQuotient(13, 1, 13) = 1fQuotient(13.123, 1, 13) = 1modulo(a, low, high) = modulo(a - low, high - low) + low modulo(0, 1, 13) = 12modulo(1, 1, 13) ... modulo(12, 1, 13) = 1...12 modulo(13, 1, 13) = 1modulo(13.123, 1, 13) = 1.123maximumDayInMonthFor(yearValue, monthValue) = M := modulo(monthValue, 1, 13)Y := yearValue + fQuotient(monthValue, 1, 13)Return a value based on M and Y:

M = January, March, May, July, August, October, or December

M = April, June, September, or November

M = February AND (modulo(Y, 400) = 0 OR (modulo(Y, 100) != 0) AND modulo(Y, 4) = 0)

Otherwise

E.1 AlgorithmEssentially, this calculation is equivalent to separating D into <year,month> and <day,hour,minute,second> fields. The <year,month> is added to S. If the day is out of range, it is pinned to be within range. Thus April 31 turns into April 30. Then the <day,hour,minute,second> is added. This latter addition can cause the year and month to change.

Leap seconds are handled by the computation by treating them as overflows. Essentially, a value of 60 seconds in S is treated as if it were a duration of 60 seconds added to S (with a zero seconds field). All calculations thereafter use 60 seconds per minute.

Thus the addition of either PT1M or PT60S to any dateTime will always produce the same result. This is a special definition of addition which is designed to match common practice, and -- most importantly -- be stable over time.

A definition that attempted to take leap-seconds into account would need to be constantly updated, and could not predict the results of future implementation's additions. The decision to introduce a leap second in UTC is the responsibility of the [International Earth Rotation Service (IERS)]. They make periodic announcements as to when leap seconds are to be added, but this is not known more than a year in advance. For more information on leap seconds, see [U.S. Naval Observatory Time Service Department].

The following is the precise specification. These steps must be followed in the same order. If a field in D is not specified, it is treated as if it were zero. If a field in S is not specified, it is treated in the calculation as if it were the minimum allowed value in that field, however, after the calculation is concluded, the corresponding field in E is removed (set to unspecified).

Months (may be modified additionally below) temp := S[month] + D[month]E[month] := modulo(temp, 1, 13)carry := fQuotient(temp, 1, 13)Years (may be modified additionally below) E[year] := S[year] + D[year] + carryZone E[zone] := S[zone]Seconds temp := S[second] + D[second]E[second] := modulo(temp, 60)carry := fQuotient(temp, 60)Minutes temp := S[minute] + D[minute] + carryE[minute] := modulo(temp, 60)carry := fQuotient(temp, 60)Hours temp := S[hour] + D[hour] + carryE[hour] := modulo(temp, 24)carry := fQuotient(temp, 24)Days if S[day] > maximumDayInMonthFor(E[year], E[month]) tempDays := maximumDayInMonthFor(E[year], E[month])else if S[day] < 1 tempDays := 1else tempDays := S[day]E[day] := tempDays + D[day] + carrySTART LOOP IF E[day] < 1 E[day] := E[day] + maximumDayInMonthFor(E[year], E[month] - 1)carry := -1ELSE IF E[day] > maximumDayInMonthFor(E[year], E[month]) E[day] := E[day] - maximumDayInMonthFor(E[year], E[month])carry := 1ELSE EXIT LOOPtemp := E[month] + carryE[month] := modulo(temp, 1, 13)E[year] := E[year] + fQuotient(temp, 1, 13)GOTO START LOOPExamples:

dateTimedurationresult2000-01-12T12:13:14Z

P1Y3M5DT7H10M3.3S

2001-04-17T19:23:17.3Z

2000-01

-P3M

1999-10

2000-01-12

PT33H

2000-01-13

E.2 Commutativity and AssociativityTime durations are added by simply adding each of their fields, respectively, without overflow.

The order of addition of durations to instants is significant. For example, there are cases where:

((dateTime + duration1) + duration2) != ((dateTime + duration2) + duration1)

Example:

(2000-03-30 + P1D) + P1M = 2000-03-31 + P1M = 2000-04-30

(2000-03-30 + P1M) + P1D = 2000-04-30 + P1D = 2000-05-01

F Regular ExpressionsA set of strings L(R). When used to constrain a regular expression R asserts that only strings in L(R) are valid literals for values of that type.

Note: Unlike some popular regular expression languages (including those defined by Perl and standard Unix utilities), the regular expression language defined here implicitly anchors all regular expressions at the head and tail, as the most common use of regular expressions in A (#x41) and end with the character Z (#x5a) would be defined as follows: <simpleType name='myString'> <restriction base='string'> <pattern value='A.*Z'/> </restriction></simpleType>

In regular expression languages that are not implicitly anchored at the head and tail, it is customary to write the equivalent regular expression as: ^A.*Z$

where "^" anchors the pattern at the head and "$" anchors at the tail.

In those rare cases where an unanchored match is desired, including .* at the beginning and ending of the regular expression will achieve the desired results. For example, a datatype A (#x41) characters somewhere within the value could be defined as follows:

regular expression is composed from zero or more | characters.

Regular Expression

[1]

regExp

::=

branch ( '|' branch )*

For all S, and for all T, valid R are: Denoting the set of strings L(R) containing: (empty string)

the set containing just the empty string

all strings in L(S)

S|T

all strings in L(S) and all strings in L(T)

branch consists of zero or more

Branch

[2]

branch

::=

piece*

For all S, and for all T, valid R are: Denoting the set of strings L(R) containing: S

all strings in L(S)

all strings st with s in L(S) and t in L(T)

piece is an

Piece

[3]

piece

::=

atom quantifier?

For all S and non-negative integers n, m such that n <= m, valid R are: Denoting the set of strings L(R) containing: S

all strings in L(S)

the empty string, and all strings in L(S).

All strings in L(S?) and all strings st with s in L(S*) and t in L(S). ( all concatenations of zero or more strings from L(S) )

S+

All strings st with s in L(S) and t in L(S*). ( all concatenations of one or more strings from L(S) )

S{n,m}

All strings st with s in L(S) and t in L(S{n-1,m-1}). ( All sequences of at least n, and at most m, strings from L(S) )

S{n}

All strings in L(S{n,n}). ( All sequences of exactly n strings from L(S) )

S{n,}

All strings in L(S{n}S*) ( All sequences of at least n, strings from L(S) )

S{0,m}

All strings st with s in L(S?) and t in L(S{0,m-1}). ( All sequences of at most m, strings from L(S) )

S{0,0}

The set containing only the empty string

Note: The regular expression language in the Perl Programming Language [Perl] does not include a quantifier of the form S{,m}, since it is logically equivalent to S{0,m}. We have, therefore, left this logical possibility out of the regular expression language defined by this specification. quantifier is one of ?, *, +, {n,m} or {n,}, which have the meanings defined in the table above.

Quanitifer

[4]

quantifier

::=

[?*+] | ( '{' quantity '}' )

[5]

quantity

::=

quantRange | quantMin | QuantExact

[6]

quantRange

::=

QuantExact ',' QuantExact

[7]

quantMin

::=

QuantExact ','

[8]

QuantExact

::=

[0-9]+

atom is either a

Atom

[9]

atom

::=

Char | charClass | ( '(' regExp ')' )

For all c, C, and S, valid R are: Denoting the set of strings L(R) containing: c

the single string consisting only of c

all strings in L(C)

(S)

all strings in L(S)

metacharacter is either ., \, ?, *, +, {, } (, ), [ or ]. These characters have special meanings in

normal character is any XML character that is not a metacharacter. In

Normal Character

[10]

Char

::=

[^.\?*+()|#x5B#x5D]

Note that a

character class is an R that identifies a set of characters C(R). The set of strings L(R) denoted by a character class R contains one single-character string "c" for each character c in C(R).

Character Class

[11]

charClass

::=

charClassEsc | charClassExpr | WildcardEsc

A character class is either a

character class expression is a [ and ] characters. For all character groups G, [G] is a valid character class expression, identifying the set of characters C([G]) = C(G).

Character Class Expression

[12]

charClassExpr

::=

'[' charGroup ']'

character group is either a

Character Group

[13]

charGroup

::=

posCharGroup | negCharGroup | charClassSub

positive character group consists of one or more positive character group identifies the set of characters containing all of the characters in all of the sets identified by its constituent ranges or escapes.

Positive Character Group

[14]

posCharGroup

::=

( charRange | charClassEsc )+

For all R, all E, and all P, valid G are: Identifying the set of characters C(G) containing: R

all characters in C(R).

all characters in C(E).

all characters in C(R) and all characters in C(P).

all characters in C(E) and all characters in C(P).

negative character group is a ^ character. For all P, ^P is a valid negative character group, and C(^P) contains all XML characters that are not in C(P).

Negative Character Group

[15]

negCharGroup

::=

'^' posCharGroup

character class subtraction is a - character.

Character Class Subtraction

[16]

charClassSub

::=

( posCharGroup | negCharGroup ) '-' charClassExpr

For any G-C is a valid C(G) that are not also in C(C).

character range R identifies a set of characters C(R) containing all XML characters with UCS code points in a specified range.

Character Range

[17]

charRange

::=

seRange | XmlCharIncDash

[18]

seRange

::=

charOrEsc '-' charOrEsc

[20]

charOrEsc

::=

XmlChar | SingleCharEsc

[21]

XmlChar

::=

[^\#x2D#x5B#x5D]

[22]

XmlCharIncDash

::=

[^\#x5B#x5D]

A single XML character is a

The [, ], - and \ characters are not valid character ranges; The ^ character is only valid at the beginning of a The - character is a valid character range only at the beginning or end of a Note: The grammar for A s-e, identifying the set that contains all XML characters with UCS code points greater than or equal to the code point of s, but not greater than the code point of e.

s-e is a valid character range iff:

s is a s is not \ If s is the first character in a s is not ^ e is a e is not \ or [; and The code point of e is greater than or equal to the code point of s; Note: The code point of a F.1.1 Character Class Escapescharacter class escape is a short sequence of characters that identifies predefined character class. The valid character class escapes are the

Character Class Escape

[23]

charClassEsc

::=

( SingleCharEsc | MultiCharEsc | catEsc | complEsc )

single character escape identifies a set containing a only one character -- usually because that character is difficult or impossible to write directly into a

Single Character Escape

[24]

SingleCharEsc

::=

'\' [nrt\|.?*+(){}#x2D#x5B#x5D#x5E]

The valid Identifying the set of characters C(R) containing: \n

the newline character (#xA)

the return character (#xD)

the tab character (#x9)

\\|

{

}

(

)

[

]

X, can be identified with a category escape \p{X}. The complement of this set is specified with the category escape \P{X}. ([\P{X}] = [^\p{X}]).

Category Escape

[25]

catEsc

::=

'\p{' charProp '}'

[26]

complEsc

::=

'\P{' charProp '}'

[27]

charProp

::=

IsCategory | IsBlock

Note: [Unicode Database] is subject to future revision. For example, the mapping from code points to character properties might be updated. All The following table specifies the recognized values of the "General Category" property.

CategoryPropertyMeaningLetters

All Letters

uppercase

lowercase

titlecase

modifier

other

Marks

All Marks

nonspacing

spacing combining

enclosing

Numbers

All Numbers

decimal digit

letter

other

Punctuation

All Punctuation

connector

dash

open

initial quote (may behave like Ps or Pe depending on usage)

final quote (may behave like Ps or Pe depending on usage)

other

Separators

All Separators

space

line

paragraph

Symbols

All Symbols

math

currency

modifier

other

Other

All Others

control

format

private use

not assigned