From: David Schwartz <davids@webmaster.com>
To: <jamie@shareable.org>
Cc: <cfriesen@nortelnetworks.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Monta Vista software license terms
Date: Wed, 12 Feb 2003 18:41:53 -0800 [thread overview]
Message-ID: <20030213024154.AAA23702@shell.webmaster.com@whenever> (raw)
In-Reply-To: <20030213022127.GB13897@bjl1.jlokier.co.uk>
On Thu, 13 Feb 2003 02:21:27 +0000, Jamie Lokier wrote:
>David Schwartz wrote:
>> 1) I have all the rights to the difference between the original
>>work
>>and the derived work. (Since I made the derived work, I must.)
>The logic of derivation does not work like that.
>You don't have all the rights to the difference.
>It is not a case of B = C - A. People do not own individual lines
>or
>bytes of the source code. (Sometimes they do, but often they
>don't).
>The "difference" between the original work and the derived work is
>_itself_ a derived work, because you can't possibly *create* a diff
>without deriving from the original work.
I don't think you understand what I mean by "difference". It's not a
precise mathematical term and it doesn't refer to 'diff' output. It
means the rights to the derived work apart from the rights to the
original work.
>In the act of you creating the diff you must have worked from the
>original GPL'd work, so the diff is derived from that, as well as
>from
>your original work. When you write "diff -ur orig-kernel my-kernel
>>file", the output from that command is a derived work of the
>orig-kernel directory.
Certainly, but that's not what I'm talking about.
>This is true even if you didn't copy any context lines from the
>original tree.
>
>That means your difference is covered by the GPL, even though you
>wrote the changes.
Of course the original work is covered by the GPL and of course the
derived work as a whole is covered by the GPL to the extent that the
original work is covered by the GPL.
>(If you did manage to write the same diff working from other
>sources,
>or if the diff only makes "fair use" of the original, that would be
>different. But any large, complex diff such as a patch to the Linux
>VM simply cannot be written without starting from the original Linux
>VM
>code. It is a question of how well the glove fits the hand, as it
>were).
When I say 'difference', I don't mean the output of a 'diff'. I mean
the literal subtraction. I mean the derived work less the original
work. Or, to put it another way, the rights to the output of the
additional creative effort added by the person who made the derived
work.
>(If the difference was just whole files using a well defined
>interface, such as a device driver or filesystem, your point seems
>quite applicable though.)
Suppose you write a play and then I write an adaptation of that play
in the form of a screenplay for a motion picture. To produce a motion
picture based upon my screenplay, you would need certain specific
rights to your play and certain specific rights to my adaptations. By
"difference" I mean the rights to the adaptations themselves. I do
agree that it is nonsensical to have, say, distribution rights to the
adaptations without rights to the original.
In other words, to have distribution rights to the derived work, you
must have distribution rights to the original. You must also have
distribution rights to the "difference". This is a notional legal
thing, there does not have to exist such a "difference" as an actual
object.
Consider if I translate a book you wrote. To distribute the
translation, you need the right to distribute the original work, the
right to make the translation, and other rights to the "difference",
that is, the right to distribute the translation apart for the right
to distribute the original work.
I think you're hung up on my use of terminology. If you don't like
the word "difference" substitute "derived work apart from the
original work".
For example, if I translate your book into another language, the
thing you need to get from me to distribute the translation is what I
call the "right to distribute the difference", but of course there is
no actual "difference". Call it the "right to distribute the
translation apart from the right to distribute the original work" or
the "right to distribute the additional creative work added in the
derivation process".
It's a complex and technical legal issue, but I'm not doing anything
unusual with it. See, for example, section 103 which states:
"The copyright in a compilation or derivative work extends only to
the material contributed by the author of such work, as distinguished
from the preexisting material employed in the work, and does not
imply any exclusive right in the preexisting material."
DS
next prev parent reply other threads:[~2003-02-13 2:32 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 11:58 Monta Vista software license terms Nilmoni Deb
2003-02-05 17:04 ` Disconnect
2003-02-05 17:25 ` Christoph Hellwig
2003-02-05 17:10 ` Robert Love
2003-02-05 17:18 ` Nilmoni Deb
2003-02-05 17:23 ` Robert Love
2003-02-05 17:36 ` andrea.glorioso
2003-02-05 17:57 ` Nicolas Pitre
2003-02-05 18:13 ` andrea.glorioso
2003-02-05 18:15 ` Christoph Hellwig
2003-02-05 18:24 ` Steven Dake
2003-02-05 18:28 ` Christoph Hellwig
2003-02-05 19:41 ` Alan Cox
2003-02-05 18:47 ` Christoph Hellwig
2003-02-05 18:52 ` Steven Dake
2003-02-05 18:31 ` Nicolas Pitre
2003-02-05 18:34 ` Christoph Hellwig
2003-02-05 18:41 ` Nicolas Pitre
2003-02-05 18:42 ` Christoph Hellwig
2003-02-05 19:00 ` Nicolas Pitre
2003-02-05 18:51 ` Ben Greear
2003-02-05 18:54 ` Dana Lacoste
2003-02-05 18:56 ` Christoph Hellwig
2003-02-05 19:25 ` Hugo Mills
2003-02-06 8:08 ` Andre Hedrick
2003-02-05 18:44 ` Nilmoni Deb
2003-02-05 17:16 ` Daniel Jacobowitz
2003-02-05 17:38 ` andrea.glorioso
2003-02-05 17:54 ` Christoph Hellwig
2003-02-05 18:04 ` andrea.glorioso
2003-02-06 1:11 ` jeff millar
2003-02-06 2:19 ` James Buchanan
2003-02-06 9:12 ` Andre Hedrick
2003-02-06 14:37 ` Alan Cox
2003-02-06 18:41 ` Valdis.Kletnieks
2003-02-06 19:14 ` Charles Cazabon
2003-02-06 20:36 ` Andre Hedrick
2003-02-10 7:18 ` Oliver Xymoron
2003-02-10 7:24 ` Christoph Hellwig
2003-02-10 13:24 ` Alan Cox
2003-02-10 17:42 ` Oliver Xymoron
2003-02-10 21:33 ` David Schwartz
2003-02-11 7:42 ` Horst von Brand
2003-02-11 19:39 ` David Schwartz
2003-02-11 20:42 ` Horst von Brand
2003-02-11 22:11 ` David Schwartz
2003-02-12 8:00 ` Horst von Brand
2003-02-12 13:26 ` Mark Hounschell
2003-02-12 15:32 ` Chris Friesen
2003-02-12 20:18 ` David Schwartz
2003-02-13 2:21 ` Jamie Lokier
2003-02-13 2:41 ` David Schwartz [this message]
2003-02-13 3:01 ` Jamie Lokier
2003-02-12 3:25 ` Derek Fawcus
2003-02-12 4:13 ` David Schwartz
2003-02-05 18:47 ` Nilmoni Deb
2003-02-05 17:17 ` Christoph Hellwig
2003-02-05 18:17 ` Nicolas Pitre
2003-02-05 18:20 ` Christoph Hellwig
2003-02-05 18:33 ` Nicolas Pitre
2003-02-05 18:40 ` Russell King
2003-02-06 11:31 ` Alex Bennee
2003-02-05 17:28 ` Chris Friesen
2003-02-05 17:31 ` Russell King
2003-02-05 19:15 ` Alan Cox
2003-02-05 19:02 ` Nilmoni Deb
2003-02-05 19:12 ` Daniel Jacobowitz
2003-02-05 21:11 ` Nilmoni Deb
2003-02-06 23:06 ` Bill Davidsen
2003-02-06 23:59 ` Nilmoni Deb
2003-02-09 14:52 ` Bill Davidsen
2003-02-09 16:50 ` Nilmoni Deb
-- strict thread matches above, loose matches on Subject: below --
2003-02-06 19:11 Dan Kegel
2003-02-06 20:38 ` Andre Hedrick
2003-02-07 17:28 ` Dan Kegel
2003-02-11 22:27 Larry McVoy
[not found] <20030212201840.AAA15967%shell.webmaster.com@whenever>
2003-02-12 20:46 ` Valdis.Kletnieks
2003-02-12 21:30 ` David Schwartz
2003-02-12 21:41 ` Derek Fawcus
[not found] <20030212213022.AAA17490%shell.webmaster.com@whenever>
2003-02-12 21:43 ` Valdis.Kletnieks
2003-02-12 22:31 ` David Schwartz
2003-02-12 23:04 ` Daniel Forrest
2003-02-12 23:28 ` David Schwartz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030213024154.AAA23702@shell.webmaster.com@whenever \
--to=davids@webmaster.com \
--cc=cfriesen@nortelnetworks.com \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox