Errata

Errata listed on various pages has not been updated for the source code.

I ran both of these examples in Opera and Mozilla 1.0, and neither worked. The first
example had an error related to &InvisibleTimes. The second did not display the
image created.

The paragraph perplexes me. I am brand new to XML. The line, "This is an example of
a contextual error that a well-formedness checker would not report."

--It wouldn't report that a bulleted list was inside a paragraph?

It goes on to mention another error that says, "This is a syntactic error that a
well-formedness checker would find, too."

--As if (too), meant as in the first example which WOULD NOT. You see what I mean?

According to the XML spec, it is not possible to have both keywords PUBLIC *and*
SYSTEM in the declaration of an external id. It should be PUBLIC here only. see rule

The following example in "Elements : The Building Blocks of XML" of the
Chapter 2 : Markup and Core Concepts, shows the use of empty element tag.

<outer>an element can be empty: <nuttin//></outer>

The explaination pertaining to the empty tag (in the same page) on the last
paragraph as follows :

.... (5), and the element ends with a slash (/) and a closing angle bracket.

The example shows two slashes to close the tag, whereas the explaination for
the tag shows only 1 slash being used.

XLink ... These special attributes names are described here: ... xml:link
... xml:attribute..."
These statements are not true. XLink standard does not have those two
attribute names.

namespace and that it should be validated against that namespace's DTD."
This is a misleading statement because XML Namespaces and DTDs are
completely independent. I would refer you to "Namespaces and DTDs" section
of XML in a Nutshell (pp. 69-71).

information about the namespace, such as who owns it and what version you're
using."
This is a misleading statement because the purpose of using URL is that
"URLs are guaranteed to be unique because they are based on domain names,
which are registered to prevent conflicts." (XML by Example, p. 77) Also,
"They are very flexible because you can create an infinite number of
namespaces from a simple root." and "It is easy to set up a Web site, if the
need arises to provide information on the namespaces." (XML by Example, p.
81).

In the last sentence:
"Elements and attributes in the default namespace don't need the namespace
prefix, ..."

should read:

"Elements in the default namespace don't need the namespace prefix, ..."

reason:
------
The sentence "Elements and attributes in the default namespaces don't
need the namespace prefix, ..." is ambiguous and misleading. The default
namespace only applies to element names. The default namespace does not
apply to attribute names. So a prefix is required to refer to attributes
names that are in an XML namespace. But sometimes, attributes do not need
a prefix and the XML instance document is still valid. It is because the
un-prefix attributes assumed to be part of the same namespace as the element
that carries them (but not because the un-prefix attributes assumed to be
part of the default namespace).

the use of"&mypic;"is not allowed here.
References to non-parsed entitities are only allowed as values of attributes of type ENTITY

The first example is not correct; the absolute URL of the given relative URL
would be
"http://www.oreilly.com/catalog/9780596000462/www.oreilly.com/catalog/learnxml/de
sc.html".

If it was the author's intention to show a relative URL that included all
but the URL's scheme, the relative URL must have a double-slash at the front
("//www.oreilly.com/catalog/9780596000462/desc.html").

the third example starts at the path:

http://www.oreilly.com/catalog/9780596000462/index.html

Since the target document is not considered part of the relative path, the example

../../

should move up two parent levels from then original to become simply

http://www.oreilly.com/

Or, it could be fixed by using only a single climb

../

in the sentence

(the keyword SYSTEM, followed by a system path or URL in quotes)

omit everything until "by". by rule [75] of the XML spec, the keyword SYSTEM must not
appear after the keyword PUBLIC has been used.

Page 85 says "descendant()" walk in depth first order. The left diagram is
not depth first (the right is).

The nodes should be relabled:
OLD CORRECTED
1 3
2 1
3 2

xhtml 1 strict doesn't allow inline elements, like <a /> on their own.
img tags require the 'alt' attribute, also in xhtml.

I got the examples files from this site.

I fixed some errors mentionned by other readers in file ex0401.xml.
And then, I tried to open it with my favorite browser (Netscape 7.1). But to my
dismay it didn't format it as specified in stylesheet ex0402.css.

The processing instruction referencing the stylesheet is missing in the XML file.
Therefore, the beginning of file ex0401.xml should be:

<?xml version="1.0"?>.
<?xml-stylesheet type="text/css" href = "ex0402.css"?>

there is no "ALL" content-model, just an "ANY".

so please replace "ALL" by "ANY"

it should read

<!ATTLIST recor id ID #REQUIRED>

and

<!ATTLIST related word IDREF #REQUIRED>

Should not the references to entities in the following

<doc>
<graphic sources="bob"/>
<graphic cources="judy"/>
</doc>

be preceded by the ampersand and terminated by the semicolon:

<doc>
<graphic sources="&bob;"/>
<graphic cources="&judy;"/>
</doc>

Firstly... shouldn't line 2
<!DOCUMENT doc [
should be
<!DOCTYPE doc [

name, the first one seen by the XML processor is used and the rest are
ignored."
This statement is false. It would be true if "element" is replaced by
"entity". Also, ignore the subsequent example of <!ELEMENT plyhedron...
because it is incorrect.

the line of code:

<![%use-disclaimer;[[

should be:

<![%use-disclaimer;[

For the same reason as confirmed errow on page 206
(insert after <blockquote> "Find out which episode")
child:* matches <comment> too.

However, for educational reasons you should change
page 204 second code block somewhere in the middle

replace:

<comment>
Find out which episode
</comment>

with:

<!-- Find out which episode -->

Then neither page 206 nor the here reported page 209 would be wrong
and the example even better!

The line of the example <xsl:template match="@type"> doesn't refernce
"friend"?

Item3 says that stuff/cruft patterns take precedence over stuff/* patterns. However,
when I try this with eXcelon Stylus Studio and also with XALAN-J 2.2.0 and XERCES
1.4.4 directly, both give stuff/* higher precedence.
e.g. the following XSL outputs "WRONG? WRONG? WRONG?"
[[[ P.S. try changing the priority on items/* template to -1 ]]]

TEST.XML...
<?xml version="1.0"?>
<items xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="test.xsd">
<product><name>foo</name></product>
<shirt><name>tanktop</name><size>10</size></shirt>
<product xsi:type="ShirtType"><name>T</name><size>12</size> </product>
</items>

TEST.XSD...
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="items">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="product" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>

<xsd:element name="product" type="ProductType"/>
<xsd:complexType name="ProductType">
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>

<xsd:element name="shirt" type="ShirtType" substitutionGroup="product"/>
<xsd:complexType name="ShirtType">
<xsd:complexContent>
<xsd:extension base="ProductType">
<xsd:sequence>
<xsd:element name="size" type="xsd:integer"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:schema>

TEST.XSL...
<?xml version='1.0'?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="items/product">
RIGHT:[<xsl:value-of select="name"/>]
</xsl:template>
<xsl:template match="items/*">WRONG? </xsl:template>
</xsl:stylesheet>

"The test attribute of <xsl:while>"

should read

"The test attribute of <xsl:when>"

Correction on 301 needs to also have

my %space_after_start;

inserted into code. A good place is after Line 56.