Errata

Learning XML

Errata for Learning XML

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted By Date submitted Date corrected
Printed
Page 13
In the fifth paragraph (second paragraph under "Keep It Simple")

"... there will more and cheaper programs available ..."

should read:

"... there will be more and cheaper programs available ..."

 Anonymous   
Printed
Page 14
1st paragraph

The latest XML specification (in XML) is at <http://www.w3.org/TR/REC-xml>.
The URL has been changed to reflect this.

 Anonymous    Jun 01, 2001
Printed
Page 27
In the second paragraph

"... but you many be curious to know ..."

should read:

"... but you may be curious to know ..."

 Anonymous   
Printed
Page 28
last line of 3rd paragraph

Insert "with " before "style". Remove whitespace before period.

 Anonymous   
Printed
Page 43
2nd paragraph

The last sentence used to read:

"This is followed by a colon, then a namespace prefix (2),
an equals sign, and finally a URL in quotes (3)."

"namespace prefix" has been changed to "local name" to be consistent
with the description of Figure 2-10 on page 42.

 Anonymous    Jun 01, 2001
Printed
Page 48
penultimate paragraph, 3rd sentence

"The problem is how enter..."

should read:

"The problem is how to enter..."

 Anonymous   
Printed
Page 50
IN PRINT: Figure 2-15

"&chap1---..."

SHOULD BE:
"&chap1;---..."

 Anonymous   
Printed
Page 86
last line of Table 3-1

The "locates" column for psibling() used to read:

"A node from among the siblings of the current node."

It now reads:

"A node from among the preceding siblings of the current node."

 Anonymous    Jun 01, 2001
Printed
Page 93
6

The "Ascott Incident" example now reads:

We aren't constrained to the limits of the search string. The offset
is allowed to run off the edge and zoom through the remaining text in
the node. Searching in the text "The Ascott Venture" with the locator
string(1, "Ascott", 8, 7) finds the string "Venture".

 Anonymous    Jun 01, 2001
Printed
Page 94
2nd paragraph

An example got deleted somehow. Take out the last paragraph and
example in the section and say:

For example in a DocBook document with a <sect1> with id="s1", you can
create a range from the start of the first <para> to the start of the
second para <para> with the span:

id(s1).span(descendant(1,para),descendant(2,para))

 Anonymous   
Printed
Page 123
7

In the last sentence:

...gets the color blue, not red.

now reads:

...gets the color red, not blue.

 Anonymous    Jun 01, 2001
Printed
Page 142
1st line

This line now reads "The selector .section can match ..."

 Anonymous    Jun 01, 2001
Printed
Page 156
last line of item IDREF

The example used to read:

<!ATTLIST related word ref IDREF #REQUIRED>

It now reads:

<!ATTLIST related-word ref IDREF #REQUIRED>

 Anonymous    Jun 01, 2001
Printed
Page 160
2/3 down the page

<!ENTITY judy "pictures/judy.jpeg" NDATA png>

Since the graphic file is a Portable Network Graphic (png) the filename
has been changed to "pictures/judy.png."

 Anonymous    Jun 01, 2001
Printed
Page 160
and [161], there were three examples starting with

<!DOCUMENT

They have been changed to read:

<!DOCTYPE

 Anonymous    Jun 01, 2001
Printed
Page 168
Example 5-2: The Checkbook DTD

The line:

#REQUIRED>

has been changed to:

#REQUIRED
number #CDATA #IMPLIED>

 Anonymous    Jun 01, 2001
Printed
Page 190
middle of page

The <occupant> entry for Filbert Fleegle was missing the </occupant> close.

Just before the last </occupants> in the example, a line
with "</occupant>" alone has been added.

 Anonymous    Jun 01, 2001
Printed
Page 197
In the code at the top of the page

"peanut-butter"

has been changed to:

"peanut butter"

to match Figure 6-1.

 Anonymous    Jun 01, 2001
Printed
Page 200
second line of the stylesheet, at the bottom of the page

The trailing slash has been removed from the uri that's the value of the
xmlns attribute .

 Anonymous    Jun 01, 2001
Printed
Page 206
Example 6-3,

Just after the first <blockquote>, the following should be inserted:

Find out which episode.

This is again because the XML of 6-1 uses the element <comment>, whose text
would be output by a default XSL rule, rather than a true XML comment.

 Anonymous   
Printed
Page 209
Table 6-3, at child::*

Change the text in the table cell to read:

This matches three nodes: the elements <comment>, <body>, and
<source>. Again, we can leave out the axis specifier and write it as
*.

 Anonymous    Jun 01, 2001
Printed
Page 213
line 3

The line:

<xsl:template match="@type">

now reads:

<xsl:template match="@friend">

 Anonymous    Jun 01, 2001
Printed
Page 214
about a dozen lines down

<xsl:template match="category[type='humor']">

now reads:

<xsl:template match="category[@type='humor']">

 Anonymous    Jun 01, 2001
Printed
Page 215
3rd sentence, 1st para. of "Default Rules" section

"...assume an implict <xsl:match-templates> element"

now reads:

"...assume an implicit <xsl:apply-templates> element"

 Anonymous    Jun 01, 2001
Printed
Page 225
Third line from bottom

The line:

"the input would look like this:"

now reads:

"the output would look like this:"

since the immediately preceding text shows the input document.

 Anonymous    Jun 01, 2001
Printed
Page 226
second code block

In:

<xsl:template match="quote">
<blockquote xsl:use-attribute-sets="common-atts">
<value-of select="."/>
...

The third line has been changed to:

<xsl:value-of select="."/>

 Anonymous    Jun 01, 2001
Printed
Page 252
last line on page

<xsl:number value-of=

has been changed to:

<xsl:number value=

The same error occurs on page 253 seven times.

 Anonymous    Jun 01, 2001
Printed
Page 301
see description

Example 8-2 ("dbfix")
The sub &space_after_start() (used twice) is undefined.

Here's the missing text. You can put it at the end of the example:

# space_after_start
# -----------------
# Add newlines after tag if it's in the list
#
sub space_after_start {
my( $name ) = @_;
my $buf = "";
if( defined( $space_after_start{ $name } )) {
my $spaces = $space_after_start{ $name };
for ( my $i=0; $i<$spaces; $i++ ) {
$buf .= "
";
}
}
return $buf;
}

 Anonymous