<div>Hi,</div>
<div> </div>
<div>I think there is a basic misunderstanding about how the GPL works with Sword and Jsword. This is how I see the problem...</div>
<div> </div>
<div>Sword or JSword (which contains 3 or 4 files under the GPL) are both under the GPL v2.</div>
<div>Any frontend to these is a derivative work, and thus that program *as a whole* must be able to be licensed under the GPL. However, the actual frontend code can be licensed under a less strict license by the copyright holder for that code. Provided that the license is compatible with the GPL, it will all work legally - the combination being under the GPL. That section of code which they have released under a more permissive license (e.g. LGPL or BSD) can then be used elsewhere in different programs.</div>
<div> </div>
<div>
<div>This is clearly stated here:</div>
<div><a href="http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLModuleLicense">http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLModuleLicense</a></div>
<div> </div>
<div>Public domain, however, is not a license - it is releasing all claims to copyright on the code. This means anyone can do whatever they like with it.</div>
<div> </div></div>
<div>So let's say with Alkitab - if it was released under the LGPL, I could take out parts of it which don't use JSword (or modify them so they don't) and use them with other LGPL software. This would be quite okay. As it is, it is public domain, so I could (though of course I won't :) take out the bits which rely on JSword, and release it as a commercial program. </div>
<div><br>God Bless,<br>Ben<br>-------------------------------------------------------------------------------------------<br>The Lord is not slow to fulfill his promise as some count slowness,<br>but is patient toward you, not wishing that any should perish,<br>
but that all should reach repentance.<br>2 Peter 3:9 (ESV) <br> </div>
<div><span class="gmail_quote">On 6/5/08, <b class="gmail_sendername">Jonathan Morgan</b> <<a href="mailto:jonmmorgan@gmail.com">jonmmorgan@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Thu, Jun 5, 2008 at 12:25 AM, Peter von Kaehne <<a href="mailto:refdoc@gmx.net">refdoc@gmx.net</a>> wrote:<br>
> Jonathan Morgan wrote:<br>>>> 6) Licensing - not my area of knowledge - but do you think it is correct<br>>>> to link a public domain programme to a GPL library? Or is Java with its<br>>>> multiple separate jars designed in a fashion that this is not a matter<br>
>>> of concern?<br>>><br>>> Two points on this:<br>>> 1. Public domain software is fairly obviously GPL compatible (see<br>>> <a href="http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses">http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses</a><br>
>> for a list of GPL compatible licenses).<br>><br>> Incorporating PD into GPL yes, but GPL into PD appears to me<br>> counterintuitive as the GPL requirements will trump. Certainly BSD into<br>> GPL is a one-way street (remember that fight last year about wireless<br>
> code from OpenBSD in Linux?)<br><br>It is a one way street if anyone chooses to modify the GPL'ed version,<br>but they could just as easily be modifying the public domain version.<br>If they release their changes under public domain then it remains<br>
public domain (though one questions whether it will actually be useful<br>without the GPL'ed library).<br><br>Jon<br><br>_______________________________________________<br>jsword-devel mailing list<br><a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br></blockquote></div><br><br clear="all">