3 ms·
Unfortunately the FSF's idea of what a derivative work is largely something they made up with no basis in statutory law and which has never been tested in court
by butlerm 5y ago
Unfortunately the FSF's idea of what a derivative work is largely something they made up with no basis in statutory law and which has never been tested in court. It basically consists of wishful thinking on their part.
In the US, a derivative work has a legal definition in Title 17 of the United States Code, and anything that is purportedly a derivative work that doesn't clearly fall under the legal definition or established common law on the subject is of little matter. Lawyers love to engage in wishful thinking on behalf of their clients and rarely get anywhere because they are not neutral arbiters but rather advocates for a one sided position of one kind or another.
In this case FSF associated lawyers appear to be completely out of touch with reality, but are incredibly influential in persuading others to be equally out of touch. And what more could you ask of an advocate for your position than that? A reality distortion field for hire.
- seba_dos1 5y agoIf you persuade enough people to be "out of touch with reality", they're not out of touch with reality anymore, because it's the reality that got changed.
- butlerm 5y agoThat may be true, but in this case the relevant parties to be persuaded are federal appellate judges before it can fairly be said that reality has changed on the ground. How likely they are to be persuaded by a position that has no apparent basis in the statutory text is a real question. As far as I can tell, no one making these rather unusual claims has even tried to outline such an argument. Why should anyone be persuaded by a legal position that has internal logic that has never been explicated anywhere? If lawyer A writes to lawyer B claiming that B's client is creating a derivative work but cannot explain why, lawyer B is more than justified in laughing them to scorn. Even if B did create a derivative work according to some unknown and unheard of legal argument acceptable to the courts, fair use could apply anyway. But one can hardly begin to look at the fair use factors if lawyer A could not even identify how a legally cognizable derivative work is being created in the first place.
- hnfong 5y ago> has never been tested in court This used to be true, but arguably the GPL has been tested in court in the infamous Oracle v Google case. (Java is licensed under the GPL among other licenses) It looks like the Supreme Court said "sure... whatever, Fair Use, I guess". Are APIs copyrightable in general? God knows. But at least you have a case from a top court deciding that in some cases you can actually copy all the APIs in a GPL'ed Java library. Totally agree with FSF making stuff up though. The reality distortion field they have is pretty legit. I don't think people even realized how the Java case could have impacted the interpretation of GPL and that it was actually a high profile allegation of GPL violation. Oh well shrug
- butlerm 5y agoThe claims that have never been tested in court here aren't part of the license, but rather commentary as to what constitutes a derivative work under copyright law. If true, they would affect the legality of a number of practices that apparently do not require distributing or modifying licensed components or accepting the license at all. If loading and running a program with dynamically linked modules with incompatible licenses creates a legally prohibited derivative work in memory, that is a reasonable claim that the author copyright holders of some of the code could pursue the users in question about. That is not what is controversial though. The controversial claim is that by merely making a module that is link or use compatible with another module a legally prohibited derivative work has been created. Not by incorporating inline code, or copying the structure, sequence, or organization of another module, but merely by making something that is compatible in the abstract. Where is the legal basis for this claim? It is apparently nowhere, little more than wishful thinking.
- hnfong 5y ago> commentary as to what constitutes a derivative work under copyright law That's part of my point actually. The question of API copyrightability in the Java case has a lot to do with whether copying APIs/ABIs in the code (whether from headers or binary symbol tables) is copyright infringement. That said, it's unfortunately true that the conclusion is far from clear. (Sidenote -- given that the Supreme Court dodged the question, does it mean that the Court of Appeals decisions still hold? [I'm not familiar with the US legal system])