25 of 27 people found the following review helpful
- Published on Amazon.com
Format: Kindle Edition
People who rate the book 5 stars clearly didn't try to understand what they were learning. Had they tried, they wouldn't have been able to understand for the simple reason that this book is full of errors and typos.
I confirm the review by C. Wilson : the book is full of errors and typos. I've wasted quite a few hours. I've decided to give up trying to learn from this book since I can't trust the content anymore.
I've been an Amazon customer since 1999 and I've never felt the need to write a review. But this 4.5 stars out of 5 stars, as of April 20th 2013, clearly upsets me because it's totally unfair to give such a high rating to a book with so many mistakes. And it's a 5th edition on top of that! Unbelievable!
That's why it's my first review on Amazon after 14 years as a loyal customer.
I wrote to the author, Joe Fawcett, on March 19th 2013 and here was his answer :
First email :
"Thanks for reading the book. I will try to answer your two queries but won't be able to do so until I am home tomorrow.
In future I suggest you submit them to the official forum at [...]
The main reason for this is to get the correct person responding, for instance I don't think I wrote the chapter referred to in your second email."
Second email :
"I have checked and indeed I didn't write this chapter. If you post your questions to the forum I mentioned earlier I will make sure the relevant author tries to help.
I've spent some time to write to him and it should be up to me to spend even more time to create an account and post on a forum? I mean it's his book. He is the author or at least one of them. He should be self-conscious and take the matter seriously even though he didn't write this particular chapter.
Later, I've found many more mistakes and I finally understood that it was not me who wasn't understanding but the book which had too many errors, typos, and missing explanations.
Did anyone at least proofread the book? They will say yes but how do you then explain so many issues?
I give 1 star because once you can not trust the book anymore (for me it was at the end of chapter 5, chapter about XML Schema), there is no point to keep reading anymore.
I really wish I could have my time and money back. I am not a student, I needed to understand XML Schema for work. My estimate is that this book costed us from $200 to $1000 USD.
Time is money. Don't waste yours. Follow my advice : don't buy this book.
12 of 13 people found the following review helpful
- Published on Amazon.com
I know many people may be forced to use this book for a college XML course, if so I do feel bad for you. The book and the try-it-out examples are fraught with errors, poor grammar, and missing files. In my class, we have found over two dozen errors in the text and we are only through chapter 6. I feel like I spend more time trying to figure out what the book is trying to say than I do with actually learning XML. I think with a lot of proof reading and testing, this book could truly be an excellent BEGINNING Xml book but in its current state, it is very hard for a beginner like myself to sort through the mess.
I would steer clear of this book if you can and hopefully the authors will come out with a sixth edition sooner rather than later with corrected material.
16 of 22 people found the following review helpful
Let's Compare Options
- Published on Amazon.com
Nearly 900 pages for $23 bucks? These folks live in the real world of budgets! The promo material on this text says that XML is for "document handling." Well, that's correct in some senses, but XML is far more important than that-- it's a little more than a Xerox machine with a network chip. It actually is about information management and standards. If you're an educator, you've likely run into Bill Clinton's (infamous?) SCORM standards, which in a nutshell, tell e-learning folks about the XML files they need to generate to follow certain rules. If you get into it deeply, you'll see the rules are about assuming folks are dishonest, and making sure it's Jimmy taking that online exam, not Joanie.
If you know a little HTML, that's all you really need to get started here. The authors step us through with a very nice pace, building on each section without assuming we're already HTML or CSS experts. Remember, XML is a document storage, transmission and management STANDARD, NOT a "display" language where you can add some tags and "go bold." In fact, XML has to depend on other languages to do everything else around it's standard-- and doesn't even have "native" tags. If you're turning your website into a database or search driven document behemoth, you'll likely be investing in LINQ, SQL and PDF conversions from and to XML to make your system work.
There are a couple other books out there on XML, but they are outdated. This 5th Edition has ALL the latest "plug ins" surrounding XML, and without them you'd really be out of date! SEO folks will love this, because it takes the usual "Google secret Numerical Analysis" formulas and raises them a step up to sleek compliance details that will optimize how the spiders see your pages. Like the donkey, if you don't whack the spider on the head with compliance and best info practices first, who cares how great the metas are if it doesn't look at them?
Who else? ANYONE whose life is data management intensive. I'm CTO at a worldwide Body of Knowledge DBMS firm (iabok dot org) and our daily routine includes HUGE documents, and is all about Taxonomy and data management, storage and retrieval. So, here's a list: Publishers, Lawyers, Educators, SEO folk, Web Designers, Archivists, Librarians, ISPs, Internet semantics folk, Search folk, Router and Network folk, Global CFO's required to report in XBRL/XML to SEC by 2013... etc.
Ontology in philosophy is about whether things are real or not, in DBMS it's about filters-- what we accept and reject, and why. XML was created assuming that someday information would become so massive, we'd need a special language just to direct traffic. Someday is here. People creating the best data driven web services don't use XML because they "have to" to comply with standards that the spiders like, they do so because it is a ROCKING language that handles huge chunks of info very efficiently when you surround it with it's favorite tools. XML also is the "heart" of many other X languages (like the aforementioned XBRL), which use it's attributes to populate their namespace ISO's, schemas and even rule details.
This book will meet your needs even if you only "have" to use XML due to a standard, but will also be really helpful and enjoyable if you also are trying to get or stay up to date on best practices not only for the "right" way to do things, but also the most enjoyable, efficient and effective. Out in IT land those two rarely go together, but in XML land, with texts like this to show us the links, they do.
Written clearly enough for self study, but would also make a great text for a course. Would you skim, read, study or refer to this? With a lot of HTML knowledge-- skim and refer, as a beginner, read and study, then skim and refer as you grow. Yep, definitely works for more than one narrow audience.
1 of 1 people found the following review helpful
- Published on Amazon.com
Using for class, book is well written and easy to understand. TONS of examples. Would like a little more insight into xml parsing software, but otherwise it's been pretty helpful in understanding the material. Our course syllabus only has us going through about 5 or 6 chapters though.