XPath and XPointer
by John E. Simpson

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 March 5, 2004.


UNCONFIRMED  errors and comments from readers: 

(ix)  5th sub item under Italics convention;
"This" misspelled as "Theis"


[53]  4th through 7th paragraphs;
The parentheses in the example are wrong, if the 'Operator precedence...' paragraph
is to be believed.  If 'and' is of higher importance (precedence) than 'or', then:

  a = b or c = d and x = y

will be evaluated as though they were coded:

  a = b or (c = d and x = y)


{60}  example at end of page;
missing [ after book:book in the DTD of the example


{67}  first xslt example;
<xsl:for-each select="book:section/*[1]">

should be:

<xsl:for-each select="//book:section/*[1]">


[170]  The xpointer example in the 2nd paragraph of the range-to(locset) heading;
The xpointer in the example is inconsistent with the explanation in the text. The
explanation only makes sense if the xpointer is:
xpointer(//account/range-to(amount))


(181)  5th paragraph ;
The explanation of the date:day-in-week(string?) prototype is a copy of the preceding
prototype for date:day-of-week-in-month(string?). It should be something like "If the
string argument is present, it returns a number identifying which weekday is present
for the date in that ISO 8601 string. If a date represents the second Friday in a
month and the first day of the week is Sunday, the value is 6. If the argument is not
present, it returns the value for the current date."