Lessig’s latest post, please, no philosophy, explains why he thinks source code escrow is important. Here’s a reformulation of the argument:

1. Copyright law restricted copies, but in return required that the government hold onto a copy and let others make copies when that copyright expired.

2. Now copyright law restricts modifications too. In return, it should require that the government let others make copies when the copyright expires.

3. With books, it’s not so difficult to make modifications from the printed copy. But with software, it’s nearly impossible: you’ll probably end up rewriting much of the source code to get things to work right.

[3a. Some have suggested this is analogous to making writers give their brains to the public. This is wrong: writers already distribute their work in a form that’s easy to modify—a form that’s rarely different from what the writer used themselves.

3b. A better analogy is that of an architect’s plans: you can “reverse-engineer” a building (take pictures, walk around, maybe punch some holes in the walls) but if you want to modify it and make a derivative building, you’ll probably end up recreating the plans and adding your modifications.]

4. To best let others make modifications of software, the government must ensure that the source code is made available when the copyright is up. The best way to do this is with source code escrow.

posted November 07, 2002 09:26 AM (Politics) #


2003 Redesign: [viewed best in gill sans]
Announcing Decisions
i’ve got the jitterbug
Quality Software
Official Argument Transcripts
The Case for Source Code Escrow
File Cabinet Lib
today’s featured superhero: Dean Kamen
today is my birthday
book connections: death and life, future of ideas, elements of typography
Trusted Clothing / Trusted Computing: A Parable

Aaron Swartz (me@aaronsw.com)