<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">The CrossWire (SWORD/JSword based) "desktop" applications may download and use any module provided by CrossWire. There is no need for these applications to know or care what the license is. All modules are fair game.<div><br></div><div>Applications that serve the web, such as SwordWEB and are not hosted on the CrossWire server can only serve those modules to which they are legally entitled to. It doesn't matter what the details of the license agreement are with CrossWire, those organizations must obtain their own license agreements.</div><div><br></div><div>The need that STEP has for checking is that it can be used to serve the WEB or be a desktop application. In the one case it cares; in the other, it doesn't. So far we have left it to the user of the application to do the right thing.</div><div><br></div><div>In Him,</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>DM</div><div><br><div><div>On Jan 7, 2013, at 12:31 PM, Andrew Thule <<a href="mailto:thulester@gmail.com">thulester@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div>I think this is a fanstastic idea, the idea of progamatically being able to detect Status of a module programatically! Very good suggestion.</div><div> </div><div>On this example:</div><div> </div><div>
"Say, a Xiphos user gets a module distributed by CrossWire, such as the ESV. Does the Xiphos user then need to seek permission to use the module through Xiphos from Crossway? Presumably not? Or do the Xiphos owners need to seek permission from Crossway? Possibly?" </div>
<div> </div><div>This is also a good example.</div><div> </div><div>Crossway as the Copyright Owner has granted CrossWire license to distribute the text as a Sword modules, so the terms of this license (permission) that govern how this works should be covered in a license agreemnt (that defines things like 'Distribute', the scope of what CrossWire means (develoepers or certain individuals) etc.</div>
<div> </div><div>So 'license to use' the ESV module has been set by the copyright owner, but CrossWire should be able to clarify what that means programatically as the licensee but also display the terms of the license (publicy) since (presumably) it has already been worked out with Crossway and both parties understand what it means.</div>
<div> </div><div>~A</div><div> </div><div> </div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jan 6, 2013 at 5:59 PM, DM Smith <span dir="ltr"><<a href="mailto:dmsmith@crosswire.org" target="_blank">dmsmith@crosswire.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Yes. o.c.j.book.BookMetaData is the proper place for this. There are many of ways you can do it. There are several patterns in the class already. I'll leave the choice up to you.<br>
<br>
As Peter mentioned there are (at least) two questions that need to be answered:<br>
Redistributable? Are there modules that cannot be distributed at all.<br>
Commercial? Are there modules that preclude the use in a commercial context. (E.g. Ad driven).<br>
<br>
Note, when STEP is a desktop application or a web application, these might have different meanings.<br>
<br>
Here are details of how to dig it out today:<br>
<br>
o.c.j.book.sword.ConfigEntryType.DISTRIBUTION_LICENSE<br>
defines the list of acceptable values.<br>
<br>
You can access this via o.c.j.book.BookMetadata.getProperty as in:<br>
<br>
o.c.j.b.BookMetadata.getProperty(o.c.j.b.sword.ConfigEntryType.DISTRIBUTION_LICENSE.getName())<br>
<br>
You can then compare it to expected values as in "Copyrighted; Permission to distribute granted to CrossWire"<br>
<br>
Hope this helps.<br>
<br>
In Him,<br>
DM<br>
<div class="HOEnZb"><div class="h5"><br>
On Jan 6, 2013, at 12:05 PM, Chris Burrell <<a href="mailto:chris@burrell.me.uk">chris@burrell.me.uk</a>> wrote:<br>
<br>
> Hi<br>
><br>
> Can I suggest adding something in the module configuration and/or sword/jsword backends that could indicate what kind of copyright we're dealing with: PUBLIC_DOMAIN, COPYRIGHT, OTHER, etc.<br>
><br>
> I personally would find that useful if I want to make available public domain resources in some fashion to others, and thereby not include some of the copyrighted material.<br>
><br>
> For example, if I'm going to allow people to include hooks into STEP to obtain and display the Scriptures on their websites, I'd want to make sure I can sift through the texts that I make available and the ones that I don't (see my separate thread about CMSses)<br>
><br>
> I guess this could be as trivial as looking for "Public domain" or "Copyright" in the field in the configuration, but in the numerous emails from the last few days, someone said something along the lines that we were trying to be consistent but aren't always.<br>
><br>
> If, we think, this is consistent enough, I'd be happy to implement a simple getter on the BookMetadata object in JSword.<br>
><br>
> If we don't think this is valuable and the .conf files aren't consistent, I'll simply maintain an "opt-in" list for those resources that are public domain + those I've obtained permissions from<br>
> Chris<br>
><br>
</div></div><div class="HOEnZb"><div class="h5">> _______________________________________________<br>
> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
> Instructions to unsubscribe/change your settings at above page<br>
<br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</div></div></blockquote></div><br></div>
_______________________________________________<br>sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br><a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>Instructions to unsubscribe/change your settings at above page</blockquote></div><br></div></body></html>