<div dir="ltr">Yes, this is exactly what I was thinking and has more complexity than I had originally thought of - very helpful.<div><br></div><div style>I guess the next question, is whether your four categories are comprehensive? We would perhaps want to include another bit to indicate that there are special non-parseable conditions, so as to indicate to a developer that he'll have to work out what it means for him. I'm thinking for example of texts that someone makes available on condition that they are not displayed/used alongside other texts from different publishers, or other kind of special permissions.</div>
<div style><br></div><div style>What do you mean by "rights for distribution of an unchanged module"? Do you mean that someone accessing the module through a front-end, in this case a web server, would not be included in the licence? i.e. because the web server has made modifications to the way the data is displayed?</div>
<div style><br></div><div style>I guess the one thing that I'm not quite clear on yet which affects the above discussion, is what where the distribution licence ends and where a license to use the distributed module in Sword frontends starts/ends. 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 style><br></div><div style>Just trying to get my head around the Copyright and licensing law which I find rather complicated.</div><div style>Chris</div><div style><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On 6 January 2013 21:39, Peter von Kaehne <span dir="ltr"><<a href="mailto:refdoc@gmx.net" target="_blank">refdoc@gmx.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
> Von: Chris Burrell <<a href="mailto:chris@burrell.me.uk">chris@burrell.me.uk</a>><br>
<div class="im"><br>
> Can I suggest adding something in the module configuration and/or<br>
> sword/jsword backends that could indicate what kind of copyright we're<br>
> dealing with: PUBLIC_DOMAIN, COPYRIGHT, OTHER, etc.<br>
<br>
</div>As such this is simply a call to see some conf entry, is it not?<br>
<br>
The only caveat would be that the conf entry might not be present and something sensible (i.e. something which stops you using a module inadvertently) needs to be returned.<br>
<br>
The next question is interpretation of the result - rights for distribution of a unchanged module e.g. would prevent using it in a webserver. Rights to create derivates non-commercially would preclude having e.g. ads on the screen.<br>
<br>
Maybe one of the best solutions (not sure if this is feasible) would be to return a bit encoded byte value which summarises<br>
<br>
Copyright - yes/no<br>
Distributable as unchanged module yes/no<br>
Distributable as derivate yes/no<br>
Commercial yes/no<br>
<br>
For a church website without ads, only the third value would be relevant. For someone who wants to create CDs with modules to give away or sale, 2 and 4 would be relevant.<br>
<br>
Does this cover what you were thinking of?<br>
<span class="HOEnZb"><font color="#888888"><br>
Peter<br>
<br>
<br>
<br>
</font></span></blockquote></div><br></div>