You would then have a financially stable organization backing the pages, have democratic input into the hosting process, and probably less censorship than a private company would apply for those that care about that sort of thing (since private companies need literally no reason to do so whereas a public enterprise would need a court order or some such).

It is right that the author of a creative work get protection for having conceived that work and reduced it to tangible form. Developers do this all the time with their code. So too do many, many others. Many today disagree with this because they grew up in a digital age where copyright was seen as simply an unnecessary impediment to the otherwise limitless and basically cost-free capacity we all have to reproduce digital products in our modern world and hence an impediment to the social good that would come from widespread sharing of such products for free. Yet, as much as people believe that information ought to be free, it is a fact that simply letting any casual passer-by copy and distribute any creative work with impunity would certainly work to rob those who may have spent countless hours developing such works of the commercial value of their efforts. I will grant that this is a social policy judgment on which the law could come down on either side. I stand with the idea of copyright protection.

Even granting the correctness of copyright as a body of law that protects certain property interests, there are still many abuses in the way it is implemented and enforced. Copyright terms have been extended to the point of absurdity, and certainly well beyond what is needed to give the original author an opportunity to gain the fruits of his or her labor. Enforcement statutes are heavy-handed and potentially abusive, especially as they apply to relatively minor acts of infringement by end-users. And the list goes on.

The point is that many people are fed up with copyright law as currently implemented and, when there is widespread discontent in society over the effects of a law, the time is ripe for a change.

I believe this is where copyright law is today.

The Bono law may have slipped through Congress with nary a dissent in its day but this will not happen again, whatever the lobbying power of Disney and others. And the same is true for the scope of copyright law as it applies to APIs.

Ours is a world of digital interoperability. People see and like its benefits. Society benefits hugely from it. Those who are creatively working to change the world - developers - loath having artificial barriers that block those benefits and that may subject them to potential legal liabilities to boot. Therefore, the idea that an API is copyrightable is loathsome to them. And it is becoming increasingly so to the society as a whole.

The copyright law around APIs had developed in fits and starts throughout the 1980s and 1990s, primarily in the Ninth Circuit where Silicon Valley is located. When Oracle sued Google in this case, that law was basically a mess. Yet Judge Alsup, the judge assigned to this case, did a brilliant synthesis in coming up with a coherent and logically defensible legal justification for why APIs in the abstract should not be protected by copyright. He did this by going back to the purpose of copyright, by examining in detail what it is that APIs do, and by applying the law in light of its original purpose. The result was simple and compelling (though the judicial skill it took to get there was pretty amazing).

Legal decisions are binding or not depending on the authority of the court making them and on whether a particular dispute in under the authority of one court or another when it is heard.

The decision by Judge Alsup is that of a trial judge and hence not legally binding as precedent on any other judge. It could be hugely persuasive or influential but no court is bound to follow it in a subsequent case.

The Federal Circuit decision that reversed Judge Alsup and held APIs to be copyrightable is not that of a trial judge and has much more precedential effect. Yet it too has limited authority. The Federal Circuit Court does not even have copyright as its area of jurisdiction. It is a specialty court set up to hear patent appeals. The only reason it heard this case was because the original set of claims brought by Oracle included patent claims and this became a technical ground by which the Federal Circuit Court gained jurisdiction to hear the appeal. But there are many other Federal Circuit courts in the U.S. and the effect of the Federal Circuit Court decision concerning copyrights is not binding on them. There is also the U.S. Supreme Court. It has the final authority and its decisions are binding on all lower federal courts as concerns copyright law.

The point is that the battle over this issue is not over. It is true that the Federal Circuit decision was a large setback for those who believe APIs should not be subject to copyright. Yet there remains that whole issue of social resistance and that is huge. It will undoubtedly take some time but the law can and does change in ways that tend to reflect what people actually think and want, at least in important areas. No one has a stake in seeing that Oracle be awarded $9 billion in damages just because it bought Sun Microsystems and found an opportunity through its lawyers to make a big money grab against Google. But a lot of people have a stake in keeping software interoperability open and free and many, many people in society benefit from this. Nor is this simply an issue of unsophisticated people fighting the shark lawyers and the big corporations. Many prominent organizations such as EFF are in the mix and are strongly advocating for the needed changes. Thus, this fight over APIs will continue and I believe the law will eventually change for the better.

In this immediate case, I believe the jury likely applied common sense in concluding unanimously that, notwithstanding Oracle's technical arguments, the use here was in fact benign given the ultimate purposes of copyright law. I leave the technical analysis to others but, to me, this seems to be a microcosm of the pattern I describe above: when something repels, and you have a legitimate chance to reject it, you do. Here, the idea of fair use gave the jury a big, fat opening and the jury took it.