I picked up this book, and several others, because I was interested in catching up on some of the emerging protocols. From the table of contents, it looked like it presented a broad overview on a variety of topics, as well as the in-depth discussion of RDF. Frankly, though, it is one of the worst books I've read in years.
There are two problems: the content, and the author. The writing and editing is poor and sloppy. The text is disjointed to the point that I often had to flip back after moving to the next page, to make sure that I hadn't skipped one. At some points, it refers back to examples that don't exist, and at others, it refers to figures that just don't match up. The larger structure is as sloppy and disjointed as the text. It's not even useful as a reference, because no single section contains all the information needed to understand the format.
The book reads like what it is: an attempt to fill 320 pages with the information that could have been (and should have been) written in a 20 page white paper ...
His editorial comments are full of contradictions and misstatements that read more like Usenet flames than thoughtful commentary. He liberally trashes SOAP, AI, and CORBA, while ignoring or glossing over any shortcomings in RDF. My favorite contradiction: KQML is a failure because it uses a lisp-based syntax, which is *hard for humans to read*. Meanwhile, elsewhere in the book, he states that humans shouldn't write out their own RDF, and should always use a remote syntax checker, because it's just too easy to make a mistake. Looking at his half-page examples of even the simplest schemas, filled with angle brackets, quotes, and syntactic oddities, makes me long for the simplicity of a lisp-based syntax, even if I have to put up with a prefix notation.
The book is a waste of time and money. One could get more information, in a better format, and with less irritation, just by going to the w3c web site.
