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

The unconfirmed error reports are from readers.  They have not yet been 
approved or disproved by the author or editor and represent solely the
opinion of the reader.

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

This page was updated July 30, 2008.  

[9] Example 2-1;
The content of MyApp.xaml is incorrect, as it specifies a NavigationWindow object, rather than an 
Application object. (At the least, with the RTM version of the Windows SDK and .NET 3.0, this will not 
compile.)

The correct content should be something like the following:

<Application xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
StartupUri="Page1.xaml"
/>



{12} 7th paragraph (project file example);
The project file presented appears to be written so as to allow the compilation of the sample 
application outlined on the preceding pages (i.e., "MyApp.xaml" and "Page1.xaml"). However, the 
"TargetType" specification is a list of all possible target types, rather than being a single supported 
type (e.g., "winexe"), and the "WindowsUIAutomation" reference inclusion appears not to exist in the RTM 
Windows SDK/.NET 3.0.

A corrected version of this file (which works with the RTM Windows SDK) would be as follows:

<?xml version='1.0' encoding='utf-8'?>
<Project
xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup>
<AssemblyName>MyFirstApplication</AssemblyName>
<TargetType>winexe</TargetType>
<OutputPath>.\</OutputPath>
</PropertyGroup>

<Import Project="$(MSBuildBinPath)\Microsoft.CSharp.targets" />
<Import Project="$(MSBuildBinPath)\Microsoft.WinFX.targets" />

<ItemGroup>
<ApplicationDefinition Include="MyApp.xaml" />
<Page Include="Page1.xaml" />
</ItemGroup>

<ItemGroup>
<Reference Include="System">
<Private>false</Private>
</Reference>
<Reference Include="System.Xml">
<Private>false</Private>
</Reference>
<Reference Include="System.Data">
<Private>false</Private>
</Reference>
<Reference Include="WindowsBase">
<Private>false</Private>
</Reference>
<Reference Include="PresentationCore">
<Private>false</Private>
</Reference>
<Reference Include="PresentationFramework">
<Private>false</Private>
</Reference>
<Reference Include="UIAutomationProvider">
<Private>false</Private>
</Reference>
</ItemGroup>

</Project>

(65) Bottom of page (Example 4-3);
Example 4-3 is titled "A document containing both SVG and XLinks" when it actually contains both rdf and 
dc elements.


(72) Section 5.4,1st paragraph;
Section 5.4 starts with -

An XML parser is required to handle the UTF-16 and UTF-8 encodings or Unicode (about which more follows).

Should be 'of', not 'or',

An XML parser is required to handle the UTF-16 and UTF-8 encodings of Unicode (about which more follows).


{163}  in the code listing;
The name of the attribute of the homepage-element on page 163 is 'xlink:href' 
but in the picture on page 164 it is 'xref:href'.


<622>in the 5th, 6th, 7th, and 8th row set of characters;
Under the hex code 620 there is a 'Y' character. This is not an arabic character. It should be no charater at all (or just n/a).
Under the hex code 628 there is a 'Y' character. It should be the arabic charater &#1576;
Under the hex code 630 there is a 'Y' character. It should be the arabic charater &#1584;
Under the hex code 638 there is a 'Y' character. It should be the arabic charater &#1592;