We have a discussion going on internally about inheritance. Some people believe
that when you subclass/inherit/derive a new class, you are creating a
derivative work in the copyright sense, especially when you override existing
methods. Others believe that inheritance is delegation of
Michael Beck wrote:
Some people believe that when you subclass a new class,
you are creating a derivative work in the copyright sense,
especially when you override existing methods.
The scary scenario is that somebody will inherit a
class, make some modifications to it, and then claim
Julian Hall scripsit:
Having quickly scanned the archives of the license discussion mailing
list I can't find much reference from when I submitted version 1.0, but
I did note that there was some concern about the license requiring the
committee to be an incorporated body.
IANAL TINLA YADA
On Sat, 13 Oct 2001, Julian Hall wrote:
Following comments I received on version 1.0 of the DSPL, I have
prepared a revision for submission for approval.
Here are my comments:
Section 3, use of the software, seems to be fairly irrelevant.
Surely simply saying use of the software is not
On Saturday 13 October 2001 03:54 am, Michael Beck wrote:
We have a discussion going on internally about inheritance. Some people
believe that when you subclass/inherit/derive a new class, you are creating
a derivative work in the copyright sense, especially when you override
existing
David Johnson scripsit:
A derivative work must contain at least portions of the original work.
I know what you mean, but that's poorly worded. Translations, for example,
don't contain any literal portion of the original, but are paradigm cases
of derivative works.
Dependency alone does not
6 matches
Mail list logo
