Here we'll explore the nexus of legal rulings, Capitol Hill
policy-making, technical standards development, and technological
innovation that creates -- and will recreate -- the networked world as we
know it. Among the topics we'll touch on: intellectual property
conflicts, technical architecture and innovation, the evolution of
copyright, private vs. public interests in Net policy-making, lobbying
and the law, and more.
Disclaimer: the opinions expressed in this weblog are those of the authors and not of their respective institutions.
Unfortunately, as Duane describes in great detail in her blog entry, life happened. Duane spends a lot of her posting apologizing to readers and sharing a bit of her perspective on the experiment. The big take-away here is that this is not all that unusual. Books are big projects and a tremendous amount can happen between the time a book is conceived and its eventual completion or - more often - abandonment. This happens a tremendous amount of the time in the conventional-funding publishing industry (last Dangerous Visions, anyone?) so it should be no surprise that it happened in a book funded by micropayments.
The challenge here is how to deal when something like this happens and that is completely uncharted territory. My hat is off to Ms. Duane not just for attempting a project of this highly experimental nature, but for how she is handling its conclusion. As I wrote earlier this week, I am still deeply committed to the idea that artists need to get paid for making art, but we clearly need to figure out how to handle what the software industry calls "error and failure cases" as well as successes. When I teach my Intro to HCI course one of the assignments for the students is always to go online and find an NTSB or similar accident report and learn how the physical world deals with failure cases - lessons the virtual world is still painfully slow to learn.