Definitive XML Schema
Priscilla Walmsley (pwalmsley@datypic.com)
ISBN: 0132886723
2nd edition, , Prentice Hall PTR.
Errata
Please report any errors or comments to the author. All feedback is welcome.
Strikethrough indicates deleted text and underline indicates inserted text.
Chapter 6
- 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.
Chapter 8
- Section 8.4.2, page 143, second paragraph. "Either
ofor both of these facets may be applied."
Chapter 11
- 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)".
- Table 11-21, page 225, example
-0045
. Comment should read: "45 B.C. in XSD 1.0, and 46 B.C. in XSD 1.1." This chapter should also note that the interpretation of negative years changed from 1.0 to 1.1, and now the value 0000 represents 1 BCE, value -0001 represents 2 BCE, etc. - 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
IRfIsIRIs".
Chapter 13
- Example 13-35, page 340, shows the
number
element in the base type as having typexs:integer
, but in the restriction it has typexs: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 bexs:integer
in both places.
Chapter 14
- Section 14.1.1.3, page 359, "It is not valid in XPath 2.0 to compare an integer to a string, at least not
withwithout converting one value to the other's type."
Chapter 19
- Section 19.8, electronic versions only, "elementspecific" should be hyphenated.
Downloadable examples
- 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 October 21, 2019.