www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Barnett" <j...@bea.com>
Subject RE: Licensing concern...
Date Wed, 27 Feb 2008 15:16:47 GMT
If the licensor is indeed the owner of the copyright in the
commercial-licensed/AGPLv3-licensed database engine, it is not bound by
terms applicable to its licensees.  When it chooses to offer bridge
component code designed to work with its other AGPLv3-encumbered code,
it is not subject to the any copyleft requirements (if any apply to the
given packaging or distribution model) of the AGPLv3.

Licensees of the ALv2-licensed bridge component who elect to download
the AGPLv3-encumbered version of the database engine should carefully
analyze whether their intended use of the latter is compatible with the
conditions of the AGPLv3, but that is not an issue created by the
ALv2-licensed bridge component. 

Regards,

Jim  

-----Original Message-----
From: Niclas Hedhman [mailto:niclas@hedhman.org] 
Sent: Tuesday, February 26, 2008 7:09 PM
To: legal-discuss@apache.org
Subject: Licensing concern...


Gang,

I have a situation where a commercial company provides a kind of 
high-performance database engine, which has its own API. It is available
both 
in a commercial-style license and AGPLv3.

Now, the same company is offering a bridge component that implements 
our "Persistence" SPI being backed by the above database. The company is

offering this bridge under Apache License v2.

The idea is that the component is contributed, and the user downloads
the 
AGPLv3 version directly from their site.

Now, I just want to make sure that the Copyright owner can "violate" the

AGPLv3 by not making the bridge component AGPLv3 as well, and has the
legal 
right to license it under ALv2. Is that correct?


Cheers
-- 
Niclas Hedhman, Software Developer

I  live here; http://tinyurl.com/2qq9er
I  work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug

---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only.  Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF.  See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Notice:  This email message, together with any attachments, may contain information  of  BEA
Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,
 copyrighted  and/or legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient, and have received
this message in error, please immediately return this by email and then delete it.

---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only.  Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF.  See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Mime
View raw message