On Tue, 16 October 2001, "Michael Beck" wrote:
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> The issue is that
> when I release something under OpenSource, I want to make sure that it will be
> "used as is", and if there is any derivative work, it will benefit the
> community, i.e. it will be published.
The OSD does not force publication on the user.
The OSD requires that software authors ALLOW users to modify/distribute.
you've already muddied the waters by turning the OSD on its head.
> The user, by using the library, agrees to
> the governing license, and thus should be obligated to publish all
> changes/modifications. Creating a wrapper, or using the class in a composite
> class would be considered as "use" and not as "derivative work". I would also
> see overriding abstract methods as "use", because the author, by defining them
> abstract, left the implementation to the user. But making any other
> changes/adaptation to "library classes", direct via code changes or indirect via
> inheritance, should be considered as derivative work and published back to the
> community.
you are attempting to excercise a right that Copyright Law does not grant you.
you are using words that have double meanings that are separate and distinct
in their two fields, i.e. "derived"
copyright law : "Derived work"
a translation into another language
adaptation into a screenplay
a sequel to a book,
the CONTENT of teh original is in the DERIVED work
in a different form. yada yada
software engineering: "Derived class"
A work, separate in CONTENT from it's base class ,
but overlapping in USE and FUNCTION.
"derived" as in "derived class" is not the same as "derived" as in "derived work".
copyright does not cover the USE or FUNCTION of a work.
patent law might, I'm not sure, but copyright does not.
The USE of a work is granted wholly to the user.
the Author is not granted any rights to control USE by copyright law.
Basically, you want to control how people USE your package,
whether they copy or modify any of your CONTENT or not.
It's outside the realm of copyright law,
and it's outside the spirit of open source.
Greg
--
license-discuss archive is at http://crynwr.com/cgi-bin/ezmlm-cgi?3
