Datypic Logo
Definitive XML Schema

Definitive XML Schema

Priscilla Walmsley (pwalmsley@datypic.com)

2nd edition (September 2012)

Prentice Hall PTR; ISBN: 0132886723


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

Strikethrough indicates deleted text and underline indicates inserted text.

Chapter 3

  • p. 50, last paragraph. "This is because none of the attributes in the XML Schema Namespace isare declared globally."

Chapter 6

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

  • p. 143, second paragraph. "Either of or both of these facets may be applied."

Chapter 11

  • p. 225, last example on page. 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.

Chapter 13

  • p. 340. Example 13-35 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.

Last updated April 26, 2015