Lawrence Lessig has a terrific weblog, well worth visiting regularly (available here), and on today's post he announces something really interesting: he is going to update his five-year old Code and Other Laws of Cyberspace, but he is going to do so in a novel manner. There will be a Wiki -- all right, I'm not really hip enough to have known what a "wiki" is; you can find out the same way I did at this site -- at which (or is it "on which"?) anyone can write comments or whole new sections of the book. Professor Lessig will then take all those contributions during the Summer and work them up into the second edition of Code, which Basic Books will then publish in the Fall. "The Wiki will stay live forever (under a Creative Commons license)." Professor Lessig has also donated his advance from Basic and any royalties that he might realize from sales of Code V.2 to Creative Commons.
I had a fascinating discussion this morning with my friend and former student Charlie Petit about Creative Commons and what it means. (You can find the Creative Commons website here, and Charlie's website here, with lots of nice material on copyright and IP generally. Charlie specializes in legal representation for authors.) My admittedly limited understanding of Creative Commons was that it was a means of placing all or parts of one's copyright interests into the public domain. Alternatively, perhaps, it is a means of renouncing one's copyright interests or of declaring one's intention not to enforce one's copyright interests. (I notice that the Becker-Posner Blog, which I have recommended before, has a Creative Commons license in the sidebar.) Charlie tells me that it is not quite as easy to renounce one's copyright interest as the Creative Commons license would seem to indicate. I want to learn more about this; my instinct is to renounce, if I can and as if anyone might care, any copyright interest in these musings, but I would, nonetheless, be mildly upset -- and I stress "mildly" -- if I were to discover that someone had copied something here and posted it without attribution. I'll continue to investigate this and will report back on what I've discovered.
TSU