By John E. Simpson
First Edition
July 2002
Pages: 208
ISBN 10: 0-596-00291-2 |
ISBN 13: 9780596002916
![]()
![]()
![]()
![]()
(Average of 2 Customer Reviews)
Referring to specific information inside an XML document is a little like finding a needle in a haystack. XPath and XPointer are two closely related languages that play a key role in XML processing by allowing developers to find these needles and manipulate embedded information. By the time you've finished XPath and XPointer, you'll know how to construct a full XPointer (one that uses an XPath location path to address document content) and completely understand both the XPath and XPointer features it uses.
Full Description
Cover | Table of Contents | Colophon
Featured customer reviews
XPath and XPointer Review, June 05 2003
I believe the book is quite good.
I believe that the context node should have been better defined.
I believe that chapter 3 should have had more examples.
Nonetheless, I have been very happy with this book. When I had a technical
question about the content, I wrote to O'Reilly and they had the author send me an answer and a satisfactory explanation. I am happy.
XPath and XPointer Review, September 15 2002
This book is mixed. I bought it really for an independent, more in-depth treatment of XPath. Chapters 3, 4, and 5 are really good in that regard.
However, there are two BIG negatives to the book. First, THE EXAMPLES ARE NOT ON-LINE EVEN THOUGH THE PREFACE SUGGESTS THEY ARE. This is RIDICULOUS since particularly Chapter 5 is written as though you were interactively working the example. Chapters 3 and 4 are also best read interactively like this.
Second, the purpose of some of the other chapters is unclear or they could be better redacted with the reader who is not part of the small XPath cognoscenti in mind. Chapter one's treatment of the historical components of XPath seems a little like ancient history to me, and I am not sure what it adds.
Chapter two is a little disjoint. The style is deductive. For instance, the reader is told several papges in that he or she might have deduced that XPath supports 4 types. Well, why not just say that up front. It was also unclear why anyone would want to use a string in XPath the way it was explained here. Of course, you want to use strings in comparison operators all the time.
XLink and XPointer are still relatively immature. I might have suggested de-emphasizing them. Focusing chapters on non-XSLT applications that use XPATH might have been better. O'Reilly has really missed the boat in this regard. A lot of new interfaces are being built that allow XPath access to document trees. One of the most interesting of these is the Java Standard Tag Library. However, Bergsten's JavaServer Pages 2nd Edition barely touches the topic, perhaps because XPath belongs elsewhere. However, it is also not in the XPath book.
Wake-up! Expand the parts of this book that are good, and put examples on-line. Make it a book that hands-on people can really use.







