please, no philosophy

Ted’s latest (and his patience with me is wearing, so perhaps sadly, his last), makes a passionate argument against my source code escrow idea, based on the nature of software and the creativity that builds it. I realize I must have somewhere inspired this debate about “nature.” I renounce it. No more talk about nature, or the philosophy of creativity. My argument is simple (maybe simplistic, maybe naive) pragmatism.

Ted had asked me why software should be treated differently from other “copyright property.” My simple response was that giving software 95 years of protection was to give the public nothing of value in return. Ted seems to agree with that: Some modification of the existing system is in order. That is all that motivates my argument. But Ted still doesn’t find that argument persuasive.

Yet his response reminds me of my years studying philosophy. He argues that there is a “means of production” that goes into every creative work. For the Godfather, for example, it “was the mind of Mario Puzo.” For software, it is the source code. And obviously, as the government should not demand Mario Puzo make his mind public in exchange for the copyright(s) supporting the Godfather, so too should the government not demand of the software author that he make his mind (the source code) public in exchange for a copyright on code.

That’s a useful point for making a distinction, but it is not an argument against escrowed code. Obviously, every creative activity includes lots of stuff that went into the creation that is not properly thought to be part of the product. Dave pointed to this point earlier: In writing a novel, there’s tons of creativity that is opaque in the final product. We don’t know, and can’t see, what the author had for breakfast, what arguments she had with her spouse, who he flirted with before writing chapter 10, what threat the publisher made that made her end at chapter 15. All this is hidden in the final product, and hence all creativity is, in this sense, “opaque.”

True enough. But I approach this from a pragmatic perspective, not a philosopher’s perspective. I pick out source code as the sort of thing that the world would benefit from having revealed because, as Seth Schoen reminded me and as the GPL defines it, source code is “the preferred form of a work for making modifications to it.” So if a copyright system wanted to encourage others to build on earlier code, providing the source code is at least one very good way to enable that creativity.

Of course, it is not the only way to enable others to build on earlier code. Providing clear APIs, etc., would enable a bunch of building. Just not as much. And reverse engineering object code would enable a bunch of building. Just not as cheaply. My point is just that we should design the system to support the “preferred form … for making modifications.”

Unless there’s a great reason not to, and this is what I’ve not seen yet. I find Ted’s claim that “I do not want to live in a society which compels me to register the contents of my brain with the federal government” colorful, but not persuasive. Poets know their poetry by heart. Does anyone think that poets are being forced to “resister the contents of [their] brain[s]” with the government when the copyright law requires a deposit of their work? This is source code, Ted. No doubt it is the product of lots of sweat and blood. But let’s not get carried away.

Siva Vaidhyanathan wrote me that my distinction may make sense today, but how long will it survive. As convergence means that all content is increasingly software, will the source code for that have to be deposited as well?

The answer to that depends, of course, on whether the source code for that too is “the preferred form of a work for making modifications to it.” Maybe, and if so, then yes. But let’s see first.

(Nick Coghlan also wrote to me that it is a mistake to call the “source code” the product; the source code, he nicely points out, is the “design – we just happen to have tools for automatically turning the design into a usable product.” Nicely put.)

Ted’s map of the different ways in which one might depend upon the right to copy is an excellent and helpful clarification of this debate. In light of that, I take it the crux of any real disagreement between Ted and me is precisely this question about modification. There is a long history of depositing copyrighted works with the government as a condition, or requirement, of copyright. Authors of books had to do it; movie studios (for a time) too with movies. These deposits were in part to enable the works to be copied once the copyright expired. The only thing my proposal adds to this tradition is the ability not just to copy, but to modify and build on the earlier work. That ability is enabled more easily with the source code than without it.

So why not enable it if we can? After an author earns the return promised by the copyright system, why not make the creative work available in the form others could most easily build upon? What reason (beyond mind-control rhetoric) is there for providing only handicapped access to the creative work?

(Compare: The Second Circuit Court of Appeals in the Corley case said that the fair use right didn’t include the right to access content in the technically more convenient manner. Thus, there was no violation of fair use if the only way to cut a snippet from a DVD was to film the snippet from the display on your TV. That position is consistent with Ted’s: the law need not give you the best, or easiest, means of modifying a copyrighted work. But in both cases, I don’t understand why. Why not push towards the easiest method for building on the work of others, once the copyright itself has been respected?)

Posted in ideas | Comments Off on please, no philosophy

GNU again

ESR has a wonderful analysis of the latest Halloween document from (some mole in) Msft. Eric rightly emphasizes substantial good news. Yet though this may be just my nature, I think there is more here to be worried about than the good news suggests. Bottom line: Regardless of our OSS/FSF loyalties, we need to work hard to de-FUDify GPL.

My worry about this comes from two recent experiences—one reading the extraordinarily misguided missive from New Democrat Adam Smith, calling on the government to stop funding research producing GPLd code; the other watching a Japanese audience react to an argument ably made by Msft’s General Counsel, Brad Smith, about GPL.

Congressman Smith’s argument, as I have argued elsewhere, is radical and wrong. But it is amazing (given how radical and wrong it is) that it still survived his staffs’ check. Corporate Smith’s argument is familiar and also wrong, but it has the appeal of centrism that corporate types and government’s like.

Our strategy here should be Msft’s: We need to “embrace and extend” Msft’s message. As Brad Smith persuasively argued, the world needs a broad “ecosystem” of software. True enough, and we should agree, because the more the world agrees that a healthy “ecosystem” is needed, the harder it will be to argue that one species in that healthy ecosystem (GPL) needs to be extinguished. GPLd code may not make sense for all projects, but we need to push the idea that that market has shown that it makes plenty of sense for many projects, including many commercial projects. The choice within this ecosystem is not between commercial and noncommercial. The real choice is between business models that benefit Msft, and those that do not.

And more importantly in the short term, we need to get the Democrats to address Congressman Smith’s mistake. He went too far. They need to correct him. In their correction, the Democrats have a chance to say something useful and principled about the importance of choice in the software market. It is one good thing about being out of power: You can afford to speak the truth.

There is obviously a well-funded campaign underway to make the world believe GPL is not safe or effective. Whether you call the operating system Torvalds helped build GNU/Linux or just Linux, it is critical that we support those fighting to defend the GPL. Eric’s optimism reflects the good news about the spread of Open Source and Free Software. But this feels a bit about like the crowing around DR-DOS. The war here has just begun. The course we must “stay” must include the defense of a core part of the Free and Open Source software ecosystem: GPL.

Posted in bad law | Comments Off on GNU again

the next really important issue

Alot of us have been talking up the importance of spectrum policy, and about the extraordinary opportunity that free spectrum (or unlicensed spectrum) creates for the next great internet revolution. Sarah Lai Stirland has a great piece framing the debate. I think Michael Powell might get this. If he does the right thing, it could be the most important governmental decision affecting the internet in 40 years.

Posted in ideas | 7 Comments

focusing for Shelton

Ted Shelton ends his reply with a nice question: why should the protection for software “be different from copyright property in the first place.” That is the issue on which the only real disagreement lies (the other disagreements are illusory, caused I trust by my own lack of clarity).

Here’s what motivates my thought that copyright gives too much protection to software just now: Think about patents for drugs. There is an active generic market for drugs. Why? Because the patents expire long before the usefulness of the drug does. That means the generics get to free ride off of the invention of the drug companies. But that free riding is a Good Thing. If the patent term is long enough, it has had its effect: it has incented [not really a word but it should be] a new discovery; but after giving the inventor his due (as defined by the term of the patent), the public gets access to the invention “without restraint.” (Story, J.).

Patents for drugs thus strike a balance: the inventor gets a portion of the total value of the patent, and the public gets a portion. And because the public gets the portion equally (meaning there can be competition in the production of the drugs), prices for drugs fall significantly, and competition is enhanced.

My sense is that at 95 years, copyrights for software produce no similar balance. Sure: they produce value to the public to the extent that they induce the creation of new software. And sure: people can reverse engineer software to figure out how it ticks. But both of those “bargains” for the public are much less than the bargain that a drug patent gives the public. (A drug patent too creates a new drug (that may save lives, or reduce pain), AND AS WELL after a period of time, a useable and valuable invention becomes the public. And a drug patent too creates an invention that other people could reverse engineer, but it AS WELL includes instructions (the patent) for how to practice the invention.)

So too is the “bargain” of a software copyright less than the bargain of a copyright for something other than software. For when (or I guess I should say if) an ordinary copyright expires, the text it produced can be copied and actually used. That’s because texts, on their surface, carry all the code necessary to make them run within one natural language. Software is different. When the copyright for Windows 95 expires in 2090, there will be no machine that can run it. It will have zero value then. And indeed, all software written in 1995 will have zero value then, if all that is “free” then is object code. (Sure, there may be emulators that emulate computers of the last century, and they may well be able to run Windows 95, but we don’t need an emulator of the 18th century to read Ben Franklin’s essays. Everything’s a difference of degree, and some differences of degree (like this one) become differences of kind.)

Software copyright thus gives the public less than patents, and less than nonsoftware copyright. That was the motivation for my proposal: software should be “different from copyright property” because the public is not getting the same sort of bargain with software that it is getting with nonsoftware copyright, or with (some) patents.

Thus I proposed two modifications: First, shorten radically the term of protection. I said 10 years, but I’ve no magic in that number. Could be shorter. Could be longer (slightly). The point is the term should be short enough that there is something valuable at the end of the bargain that others can build upon. Second, make sure there’s a translatable text at the end of the bargain so that there’s something others actually could build upon. Thus the escrowed source code. Two changes designed to create more of a bargain in the context of software, so the public could benefit from more public domain code, and others could more easily build upon formerly copyrighted software.

Now one could well say, “but it’s my property. I deserve it for ever. No reason you should force me to give it to the public after 10, or 95 years. I created it. I get it forever.” But then you would have to say the same thing about drug patents. And you would also have to amend the constitution. For again (and this is why I insist it is just confusing to use the word “property” here):not all “property” is alike (even if all “property” gives what Ted calls “ownership”). While the constitution says that if the state takes your property, it must give you “just compensation” (Amendment 5), the same constitution says that if the state gives you (what we call) intellectual property, it MUST take it after a “limited time” without compensation. So you may well be against limited times, and the bargain with the public implicit in that. But my argument is grounded in the view that the monopolies (“exclusive Rights” is the constitutional text) the government grants in the name “promot[ing] Progress” should be balanced in the way patents are, and copyrights used to be.

Two other nits on Ted’s response.

(1) We’ve converged on a description of the kinds of protection the law might grant software under the proposal I’ve outlined: (1) the modified form of copyright (shorter terms, escrowed source), (2) if not (1), then some protection against simple mechanical copying of object code, (3) if not (1) or (2), then trade-secret. This structure says: the state gives you more protection the more you give the public after a limited time. Whatever the details, that’s got to be the form.

(2) We’re nowhere close to an agreement about the mystical difference between atoms and bits, but I don’t think it matters to the argument above at all. I will just note this: Ted makes lots of the idea of the government holding the source, and then giving it away after the term expires. But there is nothing new or special in this. Until Hollywood got a nice exemption from this, the government required, e.g., deposits of films that were copyrighted for the sole purpose of assuring that after the copyright expired, there would be a source for others to come and copy. Obviously, the cost of copying is greater, but here’s the point about economics that we are just not connecting about: so long as all competitors face the same cost, why does it matter that the cost is $1 or $100. The product will be sold at the marginal cost. This is what the competitive system is all about. Or put differently: would the complaint go away if the government charged everyone wanting a copy $100? Or put differently again: I understand there is a difference between atoms and bits: the question I am asking, and not yet seeing an answer, is why does it matter to the economics. Some inventions are easy to copy after the patent expires (the Cotton Gin); some inventions are hard (drugs). Some copyrighted work is easy to copy after the copyright expires (a novel); some copyrighted work is hard to copy (a 1930 film). But whether easy or hard, the economics is the same.

Posted in ideas | Comments Off on focusing for Shelton

GNU democrats

This letter by Adam Smith on behalf of the “New Democrat Network” asking Cybersecurity Czar Richard Clarke to avoid GPLd software deserves a response. Here’s a short one by me. And if you agree, then you should respond here.

The essence of Congressman Smith’s argument is that the government should not fund basic research that results in GPLd code because it “prevent[s] companies from adopting, improving commercializing and deriving profits from the software.” GPL does this by demanding that any modifications of GPLd code that are distributed must be distributed with the source and that makes it impossible for companies to establish “commercial IP rights in any subsequent code.”

The trick in this argument is to make it sound as if it is “companies” versus GPL, or the “private sector” versus RMS. But of course there is no such division. There are, no doubt, some companies that because of their business model, cannot adopt GPLd code. Microsoft is one. But there are plenty of other “companies” who have no trouble dealing with GPLd code—IBM is one. The difference is therefore not between “companies” and the GPL. The difference is between companies willing to pay the price of GPLd code and those not willing to pay the price of GPLd code. Giving up proprietary control is the price GPLd code demands, just as all-the-money-in-the-world is the price Microsoft would demand for similar access to its OS source. Some can pay that price; some cannot.

So if Smith is being principled, then properly stated, Smith’s principle comes down to this: That the government should not fund any research that results in code that some companies could not, consistent with their business model, adopt.

If that is his principle, then it follows that the government can’t fund projects that result in proprietary code (since there are some entities (say, the Free Software Foundation) that can’t, consistent with their business model, accept that code), or more radically, it means that the government can’t fund research that results in patents (since there are some business models that can’t pay the price of a patent). The only research the government could support, on this theory, is research that produces work in the public domain.

That is an interesting but radical principle. The government funds all sorts of research that results in patents, and in proprietary code. So the real question for Congressman Smith is this: Does he believe the government can’t support proprietary or patented work if he believes it can’t support GPLd work? Is he advancing a principle, or just FUD about GPL.

If this is not a principle, then why he is speaking for the New Democrat Network. I understand why the congressman from Microsoftland pushes legislation to protect Microsoft. But it is wrong to link that pork with the NDN.

Posted in bad law | 4 Comments

still missing the point?

I’m trying to think about other things, but when my Dad won’t stop sending me articles about the case, it gets hard. Today he sent me this piece by Professor Marci Hamilton which concludes that “Mickey has the better of the argument.” But I wonder whether Mickey would have the better argument if the real arguments that we make are considered.

Jeffrey Rosen in the New Republic is the only commentator I’ve seen (though I’ve been trying to ignore this, my father notwithstanding) who has actually framed what makes this an interestingly hard case. The question is not what the Copyright Clause means in the abstract. The question is what the Copyright Clause means, given the Court’s method for reading enumerated powers. Given the Court’s insistence on the limits on Congress’s power in the context of the Commerce Power, our argument is that the same principles should produce limits on Congress’s power in the context of the Copyright Clause. Again, Rosen frames the question perfectly well: Why would you read the express limits of the Copyright Clause (“limited times”) to produce no meaningful limit on Congress’s power, but read the implied limits in the Copyright and Commerce Clause to impose real limits on Congress’s power?

It is also odd to find in Hamilton’s piece the following statement: “indeed, there is so little history relating to the Copyright Clause that any argument from original intent is doomed from lack of information.” That claim does a great disservice to scholars such as Ray Patterson who has written extensively about what the framers thought. So too does it ignore the extensive history by Tyler Ochoa, Mark Rose, and Edward Walterscheid in their historians’ brief. Indeed, it does a disservice to Hamilton’s own work, for we had relied upon her writing in our opening brief to conclude, as she wrote, that the Copyright Clause is thus not so much “pro-author but rather anti-publisher.” At least in her writing, she seemed quite confident about what the framers meant, and, imho, with good cause.

Hamilton may in the end be right. She is an extraordinarily talented lawyer and legal scholar whose work has taught me a great deal. It may well be that though everyone seems to concede that CTEA is bad policy, the constitution must permit it. But if that’s the answer, then I confess I’ve missed something in my understanding of modern American constitutional law. Taking this Court at its word, and even praising them a bit for their commitment to constitutional fidelity (as I have), “limited times” ought to have a meaningful limit.

Posted in eldred.cc | Comments Off on still missing the point?

“fair use” (or proof that Aaron has been captured by the government)

Aaron makes the nice point that there should be an analog to “fair use” in the context of patent law. This is actually a point explored by a number of legal scholars, most extensively by Maureen A. O’Rourke in a 2000 paper that does not seem to be online. But he grounds his claim on the “the conflict between these two have, in copyright at least, traditionally been resolved by the concept of ‘fair use.'”

Not true, or better, that’s government speak. “Fair use” is one mediating device between the First Amendment and copyright. The Court has never held, and it would make not sense to hold, it is the only mediating device. It is a central part of our First Amendment claim in Eldred that there are other mediating devices between the First Amendment and copyright — i.e., duration. And that just as the government concedes that if “fair use” were changed by Congress, or if Congress decided to copyright ideas as well as expressioin, then “undoubtedly” ordinary First Amendment analysis would apply, so too if Congress changes the duration of existing copyrights, ordinary First Amendment analysis should apply. This was the argument of the author of the notion (adopted by the Supreme Court in Harper) that there is a “definitional balance” between the First Amendment and copyright–Nimmer–as he concluded that retrospective changes of copyright violated the First Amendment and the Copyright Clause.

Posted in eldred.cc | 1 Comment

the father of opposition to extensions of copyright

Dennis Karjala has been fighting copyright term extensions just about as long as anyone. His wonderful page has some of the best material from the beginning of this battle through the case in the Supreme Court. Check out the letter from artist Daryl Hanson about the effects of CTEA on his ability to create.

Posted in eldred.cc | Comments Off on the father of opposition to extensions of copyright

nice point nicely made

Aaron points to a wonderful page by John Mark Ockerbloom at the University of Pennsylvania listing books that are in the public domain elsewhere but not, because of the Copyright Term Extension Act, in the United States. Check out the books you are not allowed to download. Makes me proud to be an alum.

Posted in eldred.cc | 3 Comments

is there any vice in free code?

Dave bravely (given the excitement about Mitch’s latest contribution) defend’s Don Park‘s concern that the Open Source Applications Foundation will fuel an “erosion in the sense of value for software.” That is an important and valid concern, but it needs to be kept in context.

The more I try to understand the resistance of good-souled sorts to open source or free software, the more it reminds me of the resistance by good-souled sorts to limits on copyright in, e.g., music. Sure, there are institutions you would anti-trust that oppose free software (msft), just as there are institutions that should be anti-trusted that oppose limits on copyright in music (riaa). But the puzzle is to understand the valid and serious concerns of those whose motives one should trust — Dave Winer, e.g., in software; Jenny Toomey’s Future of Music Coalition, e.g., in music.

Park’s statement helps, but it helps by isolating a legitimate, yet distinguishable, concern.

I don’t see how anyone could on principle oppose having the source code for a program available. Dave insists it’s not necessary, but that’s a very different point. It’s also not necessary to have the formula for a certain chemical compound (because one could always reverse engineer it) (I know squat about chemistry, so that might be complete bs), but just because it is not necessary does not mean it would not help. All things being equal, having the source code helps for many purposes. (“Many,” not all; helps, not “necessary”). So opposition to having source code out there must be grounded on the view that source code also hurts, and that its harm outweighs any benefit.

So how might it hurt?

Well, one way it might hurt is by making it harder for companies to behave strategically against their competitors. That was the charge against msft: that it used its power over its code to play games that illegally harmed its competitors. That power was enabled in part by closed source code. That’s not to say one couldn’t reverse engineer the code — Ed Felten did it. But the ability to reverse engineer is different from the access to the source.

I take it no one opposing free software would offer that as a justification, and certainly, Dave-type opposition is not grounded in that reason.

That leads to a second reason to oppose open or free software — that it would destroy or change the software-writing business. This seems to be Park’s concern: If everyone expects code to be free, then the ability of certain sorts to get paid for writing code is threatened. Not all coders, but some. The people who would get paid for writing software would be the people who sold devices (e.g., Apple); the ability of independent sorts to write and sell software would in turn then be weakened.

Notice the parallel argument existed in the early days of the debate about copyright and the net. (Barlow‘s amazing article is still a powerful read on this.) In that debate, some suggested the answer was for musicians to sell t-shirts, or spend more time on tour. Understandably, that response didn’t make musicians very happy.

But I think the key in both contexts is first to isolate the point, and recognize what drives it. If there were a way to assure coders — especially independent coders — got paid even though the source of their code was open, then it would be hard to oppose open code. And while it might seem odd to imagine how that is possible, we should recognize that our economy already has about a billion ways in which it secures payment to creators without locking up the creativity. Some of those would be bad (moving music back to the patronage system, for example); but not all of these would be bad. And if we could devise a way for coders to get paid, including coders independent of companies like IBM, while allowing the source code to be free, then this legitimate concern of good-souled skeptics could be met.

Professor Terry Fisher is devising such a technique in the context of music. Pester him to publish, because it is truly brilliant. Equivalent geniuses should be crafting a similarly brilliant solution for code.

Posted in free culture | Comments Off on is there any vice in free code?