| |||||||||||||
WordPress, themes, and derivative worksWordPress, themes, and derivative worksPosted Jul 28, 2010 22:08 UTC (Wed) by anselm (subscriber, #2796)In reply to: WordPress, themes, and derivative works by dwheeler Parent article: WordPress, themes, and derivative works
According to copyright law, only the copyright holder of a library (proprietary or free) is entitled to distribute the library code, so in the »proprietary case« the application author must pay the copyright holder a run-time fee to be allowed to pass a copy of the library along with their application. In this case, the question of whether the application is a »derivative work« of the library or not is immaterial, since the fee serves to compensate the (library) copyright holder for letting someone else (the application author) do something which would otherwise be the copyright holder's prerogative, namely making and distributing copies of the proprietary library. The derivative-work issue only becomes a problem with the GPL, where there is already blanket permission in the license to pass copies of a library along with an application (albeit with strings attached concerning licensing and publication of source code, etc.). The question here is what combining an application with a GPLed library does to the licensing options for that application, not how the library copyright owner is to be compensated for the use of their actual code, which is what the run-time fees are about. I am not a lawyer in any way, shape, or form but would venture to guess that the legal theory covering this (such as there exists) is completely different from that dealing with run-time fees for libraries.
(Log in to post comments)
WordPress, themes, and derivative works Posted Jul 29, 2010 22:53 UTC (Thu) by giraffedata (subscriber, #1954) [Link] You're saying the derivative work issue is specific to GPL because without GPL the application author couldn't distribute his application without the permission of the library author anyway, because the application is no good without the library and he would need the permission of the library author to distribute the library.But who says the recipient doesn't get the library from someone else? The library author gives Mary a copy of his library, then the application author gives Mary a copy of the application. It seems to me the derivative work issue is no more an issue with GPL-licensed stuff than with any other licensed stuff. I agree with nye that people should keep clear in their minds what is copyright law and what is GPL. (Hint - if it stops you from doing something, it's not GPL. GPL only adds to what you can do). That prevents them from imagining that the author can control more than he really can.
WordPress, themes, and derivative works Posted Jul 30, 2010 1:50 UTC (Fri) by vonbrand (subscriber, #4458) [Link] It seems to me the derivative work issue is no more an issue with GPL-licensed stuff than with any other licensed stuff. True, but in the case of propietary stuff you pay for the permission to redistribute the library (and perhaps also for the right to create a derivative work to be distributed with it). In the GPL case the only point that matters is the second one, which is very much irrelevant in the propietary case.
WordPress, themes, and derivative works Posted Jul 30, 2010 7:12 UTC (Fri) by anselm (subscriber, #2796) [Link] You're saying the derivative work issue is specific to GPL because without GPL the application author couldn't distribute his application without the permission of the library author anyway, because the application is no good without the library and he would need the permission of the library author to distribute the library. No, I don't. I said that according to copyright law only the copyright holder gets to distribute their code, and that vendors of proprietary libraries may charge run-time fees in order to allow others to do it too. Application authors tend to take advantage of that sort of arrangement for the convenience of the users of their code. Whether that makes the application a "derived work" of the library is a non-issue in this case; the library is presumably sold in order to be incorporated in applications, and end users typically don't get to redistribute the code in question to yet other people. With a GPLed library, permission to distribute is already part of the library's license, and the authors of the GPL are jumping through hoops to try to enforce specific licensing conditions on the distribution of code that uses that library, which is an entirely different ball-game from the proprietary case.
WordPress, themes, and derivative works Posted Jul 30, 2010 10:03 UTC (Fri) by marcH (subscriber, #57642) [Link]
> But who says the recipient doesn't get the library from someone else? The library author gives Mary a copy of his library, then the application author gives Mary a copy of the application.
That's circumvention, it's forbidden by the DMCA.
WordPress, themes, and derivative works Posted Jul 30, 2010 15:41 UTC (Fri) by mpr22 (subscriber, #60784) [Link] Is it circumvention of an "effective technical measure"?
|
|||||||||||||