No comments about Service-Oriented Integration Report: Using Web Services and XML to Integrate Systems.

No comments about E-Business and XML: Where Metadata Makes Money Presentation.

No comments about XML in Financial Services Report: The Whats, Whys, Whos and Hows.

No comments about ZapNote: Corel ZapNote: Advancing XML Content Creation.

No comments about XML: Filling a Data-Description Gap, Part I.(Technology Information): An article from: Journal of Database Management.

No comments about ZapNote: Forum Systems ZapNote: Advanced XML Network Appliance.

No comments about XML: Filling a Data-Description Gap, Part II.(Technology Information): An article from: Journal of Database Management.

5 comments about Designing XML Internet Applications.

1. It's a pretty decent indication of the potential of the XML document/messaging structure, but lacks significant insight into designing any type of formal business application.

   Most of the book relies heavly on perl scripts for message processing. I wish some attention was directed at VB/ASP or CGI for message processing.

   With few XML books on the market, I would recommend this book, as it provides a good insight of the potential of XML.




2. 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.




3. 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.




4. 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.




5. 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.

No comments about Tech Ed 2001: centrado en XML.(evento de la industria de aplicaciones; México)(TT: Tech Ed 2001: setting eyes on XML.)(TA: software industry exhibit; Mexico)(Artículo ... Breve): An article from: E Semanal.

2 comments about DocBook XML Publishing (With CD-ROM) (Linux).

1. For a complete beginner, this book is OK, otherwise I think people are going to find it light on the details. Of course, it's the details that are hard to discover and get right.

   Also, space was devoted to topics that are not really germane, like CVS, Emacs and vi. Of course one has to edit DocBook files, but devoting 3 chapters (out of 12 total) seems like padding.




2. Save your money and spend your time on the Linux Documentation Project web site.
   This book does not contain a single useful detail on how to install and configure the software used to render documents, so make sure you're using a distribution of Linux which includes the tools. Windows users are out of luck.
   None of the Chapter 5 example links work on the CD-ROM. The examples in the book and on the CD-ROM are not very complete or useful. The book and CD seem slapped together without organization or quality control. I'm sorry I bought it.