Glossary of "XML Schema Part 2: Datatypes"

Term entries in the "XML Schema Part 2: Datatypes" glossary

W3C Glossaries

Showing results 1 - 19 of 19

atomic

From XML Schema Part 2: Datatypes (2001-05-02)

A   datatype definition (or the simple ur-type definition).

basic readability:

From XML Schema Part 2: Datatypes (2001-05-02)

Textual, rather than binary, literals are used. This makes hand editing, debugging, and similar activities possible.

collapse

From XML Schema Part 2: Datatypes (2001-05-02)

After the processing implied by replace, contiguous sequences of #x20's are collapsed to a single #x20, and leading and trailing #x20's are removed.

constraint onstraint

From XML Schema Part 2: Datatypes (2001-05-02)

Constraints on the schema components themselves, i.e. conditions components satisfy to be components at all. Largely to be found in .

ease of parsing and serializing:

From XML Schema Part 2: Datatypes (2001-05-02)

Where possible, literals correspond to those found in common programming languages and libraries.

error

From XML Schema Part 2: Datatypes (2001-05-02)

A violation of the rules of this specification; results are undefined. Conforming software detect and report an error and recover from it.

for compatibility

From XML Schema Part 2: Datatypes (2001-05-02)

A feature of this specification included solely to ensure that schemas which use this feature remain compatible with

interoperability:

From XML Schema Part 2: Datatypes (2001-05-02)

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.

list

From XML Schema Part 2: Datatypes (2001-05-02)

An or simple type definition.

match

From XML Schema Part 2: Datatypes (2001-05-02)

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

may

From XML Schema Part 2: Datatypes (2001-05-02)

Conforming documents and processors are permitted to but need not behave as described.

must

From XML Schema Part 2: Datatypes (2001-05-02)

Conforming documents and processors are required to behave as described; otherwise they are in error.

otherwise

From XML Schema Part 2: Datatypes (2001-05-02)

a set with members drawn from the set above, each being present or absent depending on whether the string contains an equivalently named space-delimited substring.Although the finalDefault  attribute of schema may include values other than restriction, list or union, those values are ignored in the determination of

preserve

From XML Schema Part 2: Datatypes (2001-05-02)

No normalization is done, the value is not changed (this is the behavior required by for element content)

replace

From XML Schema Part 2: Datatypes (2001-05-02)

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

schema representation constraint

From XML Schema Part 2: Datatypes (2001-05-02)

Constraints on the representation of schema components in XML. Some but not all of these are expressed in and .

the empty string

From XML Schema Part 2: Datatypes (2001-05-02)

the empty set;

union

From XML Schema Part 2: Datatypes (2001-05-02)

A non-empty sequence of simple type definitions.

validation rule

From XML Schema Part 2: Datatypes (2001-05-02)

Constraints expressed by schema components which information items satisfy to be schema-valid. Largely to be found in .

View another glossary