Alan Cox on Patent Law and GPLv3

tykev writes "Linux kernel guru Alan Cox talks about kernel features, cooperation with hardware vendors, and software patents. From the interview: 'I don't think [Microsoft's patent threats] are the biggest danger. As Microsoft has been finding out recently it is the patent trolls, and organisations with buried patents in interesting areas that are the biggest threat in the USA. The real answer to that problem, however, is to pull the USA back into line with the majority of the world which simply does not recognize patents on software but respects them as literary works subject to copyright law.'"

Comments

Re:One extreme to the next

[cpt kangarooski]

The problem becomes, how many ways can you write a single piece of code? At present, you are fairly limited by the languages available as to what you can and cannot do. This means that you could get several pieces of code doing the same task that look nearly identical. Now is this going to be copyright infringement? Variable names could even come out looking very similar if both programs were coded using the same naming convention. There is a huge problem with treating a software copyright like an "art" copyright.

Actually, it's not. Copyright pertains to the expression portion of software, but not the underlying ideas, functionality, etc. Ultimately, maintaining this distinction takes priority over copyrightability. For example, where there is only one or only a limited way of expressing a given idea, the idea and expression are considered to have merged, and there cannot be a copyright, lest it effectively protect the uncopyrightable idea. This is known as the merger docrine.

There's also the scenes a faire doctrine, which makes uncopyrightable things like stock story elements. For example, in horror movies, someone originated the routine bit where the mood is set when you see a wolf howling, silhouetted against the moon. But it's unprotectable since it's a common, stock element. The doctrine is used in the software field, both for elements which would be common across much software, as well as for portions of the code which are dictated by external considerations such as efficiency or platform compatability, and so lack some originality.

Finally, there's the fact that copyright infringement has nothing to do with identicality, but rather has to do with originality. That is, it isn't unlawful for Alice's program to be identical to Bob's program, so long as Alice didn't copy her program from Bob. For many works, independent creation -- when it happens -- can still be tricky to show. But for closed source software, it would be tricky for the alleged infringer to have seen the source. The accused would want to have kept some records to help vindicate themselves, and if they did have some kind of access (e.g. Alice used to work for Bob's company and could reasonably have snuck a copy out), they'd have a pretty strong case. Reverse engineering can qualify as access -- e.g. if you decompile the binary -- but again, the underlying functionality isn't protected by copyright, only the way in which it is expressed can be, subject to the limits discussed above. That's why cleanroom reverse engineering is a good strategy to follow.

You might also want to look at the abstraction-filtration-comparison test in the Altai case to see how courts will often compare two pieces of software to see if there has been infringement.

Re:One extreme to the next

[cpt kangarooski]

No it's not. The presence of citations in a quote doesn't affect whether it is infringing or not. Rather, it is good practice for purposes of avoiding plagarism (which isn't illegal). Citing others' work, when it is used, is good academic and professional practice. Nothing to do with the law, though.