Errata

Please report any errors or comments to the author. All feedback is welcome.

~~Strikethrough~~ indicates deleted text and underline indicates inserted text.

Chapter 2

Table 2-2, page 23, lists 47 built-in types, but two paragraphs earlier it says there are 49 built-in simple types. This is because, for simplicity, the table leaves out the special types xs:anySimpleType and xs:anyAtomicType. The special types are described in Section 11.1.1.

Section 6.5, page 106, second bullet point was confusing in that it implied that "Mr." was the default value in the schema. Instead, it was intended to mean that the element could be missing from the instance because the application should consider it the default. ~~"It is the default, so it is not specified: The customer's title should default to "Mr."~~"It is considered the default, so it is not specified: The processing application should assume that the customer's title is "Mr." if it is not present.

Section 8.3, page 135, second paragraph says "Every new simple type restricts the value space of its base type in some way." However, this is not true if the new simple type is a list or union type. You could also have a new atomic simple type that has the same value space as the base type, if it does not use any facets.

Section 8.3.4.1, page 141, first paragraph says ""Keep in mind that any types that may be derived from your type must be more restrictive.". However, it is possible for the new type to be equally restrictive if no facets are specified.

Section 8.4.2, page 143, second paragraph. "Either of or both of these facets may be applied."

Section 9.2.2, page 165, refers to the wildcard (period) as a character when it would be more correct to refer to it as a metacharacter.

Table 11-14, Safari Books Online only, the table is visually truncated. The half-visible line in the final column of the final row reads "value is 0)".
Section 11.4.1, page 221: "The lexical representation of date is YYYY-MM-DD where YYYY represents the year,..."
Table 11-21, electronic versions only, the subheading for "Invalid Values" is missing. It should appear before example 99, as that and the subsequent examples are invalid values.
Table 11-36, electronic versions only, the subheading for "Invalid Values" is missing. It should appear before example contains a space, as that and the subsequent example are invalid values.
Section 11.6.4, page 251, "Version 1.1 expands the definition of anyURI to include ~~IRfIs~~IRIs".

Table 12-6, page 277, says that maxOccurs on an all element can be 0 or 1. Conversely, the prose right after the table states that maxOccurs must be 1. Both of these should say that in version 1.0, maxOccurs on an all element must be 1. In version 1.1, it can be 0 or 1.

Table 13-7, page 318, unnecessarily lists pattern twice under the content model.
Example 13-35, page 340, shows the number element in the base type as having type xs:integer, but in the restriction it has type xs:string. This is not a correct restriction; the type in the restriction should be the same as, or a derivation of, the type in the base type. The intent was for it to be xs:integer in both places.

Section 14.1.1.3, page 359, says "The fields are matched in the same order, and they must have related types." To clarify, "related types" means that the types must either be the same type or one must be derived from the other.

Section 15.3.2.4, page 398, "However, it is possible for a complex type definition to reference two or more attribute groups, each of which may contains an attribute wildcard."

Section 17.6, page 432, "It is not valid in XPath 2.0 to compare an integer to a string, at least not ~~with~~without converting one value to the other's type."

Some of the book examples downloadable from this Web site were accidentally truncated, although they appeared correctly in the book. They were examples 13-9, 13-36, 14-15, 14-16, 19-15, 19-24, 20-1, 20-2, 20-3, 20-5, 21-8, 21-10 and 21-25. These have now been corrected.

Last updated August 19, 2024.