<< 1 >>
Rating: 
Summary: Spacefiller without any real focus
Review: I was looking for a clean and concise approach to XML. Instead I got the impression that this book was just an excuse for the author to squeeze in as much minutia on SGML as he thought he could get away with. It does give good background on XML along with a mind numbing amount of hype. Look elsewhere for a good introduction to using XML.
Rating: 
Summary: I'm not impressed.
Review: I was looking for a clean and concise approach to XML. Instead I got the impression that this book was just an excuse for the author to squeeze in as much minutia on SGML as he thought he could get away with. It does give good background on XML along with a mind numbing amount of hype. Look elsewhere for a good introduction to using XML.
Rating:
Summary: Buy a newer book.
Review: This is an actual excerpt from page 544: "Similarly, an output specification language may be associated with a recurring negotiation problem (or class of negotiation problems) as a way of describing that only agreements allowed by this language may be considered valid output for any specific problem instance belonging to the recurring negotiation problem." This was a bad book when it was published almost 6 years ago. Now it is bad and out of date.
Rating:
Summary: Buy a newer book.
Review: This is an actual excerpt from page 544: "Similarly, an output specification language may be associated with a recurring negotiation problem (or class of negotiation problems) as a way of describing that only agreements allowed by this language may be considered valid output for any specific problem instance belonging to the recurring negotiation problem." This was a bad book when it was published almost 6 years ago. Now it is bad and out of date.
Rating: 
Summary: Spacefiller without any real focus
Review: This is obviously a book where the authors commited themselves to writing a certain number of pages and then, half-way into the work they realized that didn't have enought material to cover it. The totally useless 100-page poorly-commented pre-release Java source code for a DOM-implementation in chapter 10 is a particularily good example of this. Another horrible chapter is chapter 11, which contains an explataion of user interface interaction that is so overly abstract but still so extremely stupid that I've used that particular chapter as an example of how a really useless book should be written. Also, early in the book the author explains that the book is amed towards rpogrammers. It's interesting to see that they hardly ever back their examples up with and source code at all. In short. Don't buy this book.
<< 1 >>
| 
