XML in a Nutshell, 3rd Edition
by Elliotte Rusty Harold, W. Scott Means

This errata page lists errors corrected in the most recent printing.

If you have technical questions or error reports, you can send them to
booktech@oreilly.com.  Please specify the printing date of your copy.

This page was updated July 10, 2007
  
Here's a key to the markup:
	[page-number]: serious technical mistake
	{page-number}: minor technical mistake
	<page-number>: important language/formatting problem
	(page-number): language change or minor formatting problem
	?page-number?: reader question or request for clarification


(29)  2nd bulleted point;
"How many of instances..."
should read:
"How many instances..."


{40}  last code on page;
<!ELEMENT name (last_name
               | (first_name, ( ( middle_name+, last_name) | (last_name?) )
               ) >

missing a closing ")"
should be:

<!ELEMENT name (last_name
                | (first_name, ( (middle_name+, last_name) | (last_name?) ))
                ) >


{46} 2nd paragraph of IDREF section;
"Every project has a project_id ID type attribute"  
should be:
"Every project has an ID type attribute named id"

also, towards the bottom of the page:

<!ATTLIST project project_id ID #REQUIRED>
should be:
<!ATTLIST project id ID #REQUIRED>


[47]  End of IDREFS section;

<!ATTLIST employee social_security_number ID     #REQUIRED
                    fsteam                   IDREFS #REQUIRED>
<!ATTLIST project  project_id             ID     #REQUIRED>

to

<!ATTLIST employee social_security_number ID     #REQUIRED>
<!ATTLIST project  project_id             ID     #REQUIRED
                    team                   IDREFS #REQUIRED>



{63}: The first paragraph of "Namespace Syntax" is really imprecise,
or perhaps overly precise. Replace it with the following:

     Namespaces distinguish between elements with different meanings but
the same name by assigning each element a URI. Generally, all the
elements from one XML application are assigned to one URI, and all the
elements from a different XML application are assigned to a different
URI. These URIs are called namespace names. Elements with the same name
but different URIs are different kinds of elements. Elements with the
same name and the same URI are the same kind of element. Most of the
time a single XML application has a single namespace URI for all its
elements, though a few applications use multiple namespaces to subdivide
different parts of the application. For instance, XSL uses different
namespaces for XSL Transformations (XSLT) and XSL Formatting Objects
(XSL-FO).


(95)  Subsection titled "The body of the work in the 'body' element";
The last sentence reads:

Each div1 element has a header child...

'header' should be 'head' according to Example 6-1.



[164]  Figure 9-1:

     * text/xsl should be application/xml
     * xref:href="http://www.turing.org.uk" should be
           xlink:href="http://www.turing.org.uk"




(193) In the last paragraph on the page;
"purchase_details.html" 
should be:
 "purchase_details.txt"



(266): In Example 16-4, remove the extra http:// from the namespace
URIs for xmlns:xsi and xmlns:xsd. That is, change

<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://http://www.w3.org/2001/XMLSchema">

to

<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">



(266): In Example 16-5, change xmlns:env to xmlns:SOAP-ENV and add a
namespace declaration for the xsd and xsi prefixes. That is, change

<SOAP-ENV:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">

to

<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">


{281}  after 1st paragraph;
In the sample command line

  % java dom.Writer -V -S addressdoc.xml

both option letters must be given in lower case to enable schema validation:

  % java dom.Writer -v -s addressdoc.xml

The given uppercase option letters DISABLE the schema validation, which is exactly what is not wanted here.



{286}: The first code fragment on the page should declare the xs
prefix, not the xsi prefix. That is change

<xs:schema xmlns:xsi="http://www.w3.org/2001/XMLSchema"
          targetNamespace="http://namespaces.oreilly.com/xmlnut/address">

to

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
          targetNamespace="http://namespaces.oreilly.com/xmlnut/address">



{287}: The second code fragment on the page should declare the xs
prefix, not the xsi prefix. That is change

<xs:schema xmlns:xsi="http://www.w3.org/2001/XMLSchema"
   targetNamespace="http://namespaces.oreilly.com/xmlnut/address"
   xmlns:addr="http://namespaces.oreilly.com/xmlnut/address">

to

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
   targetNamespace="http://namespaces.oreilly.com/xmlnut/address"
   xmlns:addr="http://namespaces.oreilly.com/xmlnut/address">



{289}: Example 17-7 should declare the xs prefix, not the xsi prefix.
That is change

<xs:schema xmlns:xsi="http://www.w3.org/2001/XMLSchema"
   targetNamespace="http://namespaces.oreilly.com/xmlnut/address"
   xmlns:addr="http://namespaces.oreilly.com/xmlnut/address"
   elementFormDefault="qualified">

to

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
   targetNamespace="http://namespaces.oreilly.com/xmlnut/address"
   xmlns:addr="http://namespaces.oreilly.com/xmlnut/address"
   elementFormDefault="qualified">


{297}: Example 17-9 should declare the xs prefix, not the xsi prefix.
That is change

<xs:schema xmlns:xsi="http://www.w3.org/2001/XMLSchema">
to
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">


{301}: Example 17-12 should declare the xs prefix, not the xsi prefix.
That is change the first line from

<xs:schema xmlns:xsi="http://www.w3.org/2001/XMLSchema"
to
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"



{302}: Both code fragments on this page should declare the xs prefix,
not the xsi prefix. That is change the first lines from

<xs:schema xmlns:xsi="http://www.w3.org/2001/XMLSchema"
to
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"



{458}: Change the description of the // abbreviated step to the following:


All descendants of the context node and the context node itself unless
// occurs at the beginning of the expression, in which case this refers
to all descendants of the root node and the root node itself. Never used
in isolation. Must be followed by a location step.