Table of contents

[Home] [W3C Specs]

1.1 Purpose

1.2 Requirements

1.4 Terminology

1.5 Constraints and Contributions

2.1 Datatype

2.2 Value space

2.3 Lexical space

2.3.1 Canonical Lexical Representation

2.4.1 Fundamental facets

2.4.2 Constraining or Non-fundamental facets

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

3 Built-in datatypes

3.1 Namespace considerations

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.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

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.7 NCName

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.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

4 Datatype components

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

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.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

Appendices

A Schema for Datatype Definitions (normative)

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

D.3.1 Sign Allowed

D.3.2 No Year Zero

D.3.3 More Than 9999 Years

E Adding durations to dateTimes

E.1 Algorithm

E.2 Commutativity and Associativity

F Regular Expressions

F.1 Character Classes

F.1.1 Character Class Escapes

G Glossary (non-normative)

H.1 Normative

H.2 Non-normative

I Acknowledgements (non-normative)

1.4 Terminology

Terminology

The 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:

for compatibility: A feature of this specification included solely to ensure that schemas which use this feature remain compatible with [XML]
may: Conforming documents and processors are permitted to but need not behave as described.
match: (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.
must: Conforming documents and processors are required to behave as described; otherwise they are in error.
error: A violation of the rules of this specification; results are undefined. Conforming software may detect and report an error and may recover from it.

[Next Chapter] [Home]