GPL survives antitrust challenge - again
Posted Nov 15, 2006 16:45 UTC (Wed) by
jstAusr (guest, #27224)
In reply to:
GPL survives antitrust challenge - again by bojan
Parent article:
GPL survives antitrust challenge - again
>> In fact the GNU GPL doesn't say that royalties can't be asked for
>Well, you are now contradicting yourself. You claimed previously the charging royalties isn't premitted. Unless you're playing some word game here along the lines of "you can ask, but it isn't permitted".
The first time I was responding to your question, I assumed you were referring to a standard royalty contract or claim. In the case you are quoting from above I was thinking outside the box, however, I quoted the GNU GPL in order that you would be able to see the facts.
I must make a complaint here, I have noticed that in at least a few instances you have quoted while disregarding relevant information. I am not asking you to quote everything, but try to respond to the complete idea. Such as, in this case you seem to be ignoring the word "redistribution" in the GNU GPL license, that means that the distributor cannot place a requirement of collection of royalties on a down stream distributor. It does not place the restriction on the "distribution" itself. That is consistent with the rest of the GNU GPL, the distributor must give the same freedoms that were received. Now, I will agree that a normal royalty contract would not work under the GNU GPL. However that does not stop a distributor from saying "Hey, if you want to give me royalties that is fine, as long as you don't require that anyone give you royalties."
The important parts in this comment are:
1. The word redistribution in the GNU GPL snippet that is referenced here and quoted in a prior comment.
2. The fact that there is no "allows requirement of "no charge"" in the GNU GPL. (The keyword there being "requirement".)
And in general you are making an assumption that "no charge" in the court order means "royalties", that is your assumption not an established fact.
(
Log in to post comments)