<< 1 >>
Rating: 
Summary: Irritating
Review: 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.
Rating:
Summary: A bad book
Review: In spite of the bad reviews on this site,I decided to buy this book partly because this may be the only book on the sementic web in the market,and I did not want to wait till others were published. Unfortunately,I too cannot recommend this book to anyone.Here are
my reasons: 1)Both the title of the book as well as the title of the series(Professional Developer's Guide Series)are highly misleading.No developer will learn anything practical from this book.There are no examples or any other practical instructions whatsoever.The most "difficult" examples I could find were the analysis of statements like "Hjelm is the author of a book". 2)What this book is is a theoretical and acedemic discussion of artificial intelligence(AI),XML,RDF,and intelligent agents(IA).But here too there is a catch.You wont understand much unless you already know these fields.I have some background in these fields but I found the presentation so monotonous and boring that I too learned nothing new. 3)This book could have been a classic if properly written.Time may be ripe for artificial intelligence to enter the mainstream of computer world via the gateway of XML.Therefore,the unification of AI,XML,RDF,and IA is a highly fascinating project for the future.And a classic is desperately needed on this theme.But Hjelm's book is not that classic.
Rating: 
Summary: Okay but confused
Review: This book is okay but needs work. It has neither good examples of RDF or programming with RDF. A better background to RDF, more examples, and better explanations are required.
Rating:
Summary: Okay but confused
Review: This book is okay but needs work. It has neither good examples of RDF or programming with RDF. A better background to RDF, more examples, and better explanations are required.
Rating: 
Summary: Good first book
Review: This is a very good book for RDF. Get this book, if you want to learn RDF. The RDF specs from W3c aren't very easy to read. So, if you care about RDF, semantic web, get this book.
Rating:
Summary: ;-( Mess
Review: This is one of the worst book that I have ever read. It makes a simple thing perplexed. I really don't know what the author wants to say and why he repeats the same unrelated and simple things over and over again. It is always off the point. The examples are just toys for laymen.
Rating:
Summary: thanks professor ...
Review: This is the first book I've read on the topic after a few days getting a feel for RDF through web resources (W3C et al). I'm a nocive for sure, but have experience with XML/XSD and I'm an accomplished programmer / developer. This isn't a "Developer's Guide".
Though the author shows mastery of the topic and makes excellent points that have helped me in design issues, the general text is hard to read and hard to folow. This may speak more to my (lower than average?) reading skills but frankly I'm not sure. If I were well versed in RDF this may be a good book for opening academic discussions, but it's a bad read for beginners (and I'd consider myself a rather advanced beginner).
<< 1 >>
| 
