K T wrote:
I expect at some point there will be no talk of apps going MIA because of an update and the review process will become similar to app reviews. In any case, and at this time, I think it's risky to not bother with the caveat, and just emptor away - it's up to the individual, tho, of course.
I sure hope that, going forward, updates to a book won't cause the currently selling copy to go AWOL. Apple's message to Jim seems to indicate as much. But, given the reports around here, I'm not going to casually push an update to my book until well after we've established that doing so isn't going to endanger my currently selling version…
And again, the best way to aviod such risk is to simply not go down that road, double down on reviewing and proofing up front, rather than shipping something less than perfect. We all know the saying "Why is there always time to do something twice but never enough time to do it right in the first place." Resist the urge to see your book in the store long enough to make sure it's something you want your name on.
Getting it right as much as possible the first time is definitely preferable, I agree. But there are reasons for wanting to update a book other than just mistakes. I had to replace an entire chapter in my paper book for the third printing due to a change in an international standard, for example. Especially for technical books, such updates are often inevitable. I see this as a big advantage of electronic books: cheap and easy to update.
Once Apple add a notification mechanism similar to what is available for apps, it'll even be easy for customers to find out when a book has been updated.
Michi.