<div dir="ltr"><div>Peter, </div><div> </div><div>The licenses found at the ISV site, and the ESV site do not specifically grant to you license to distribute their Copyrighted work. Those licensing don't mention CrossWire at all.</div>
<div> </div><div>I agree, that if I am bound by those licenses I have no right to distribute anything, but neither does CrossWire. Not only, but Crosswire has no right to chastise me for distributing them and is hipocritical if it does so.</div>
<div> </div><div>However, I'm giving Crosswire benefit of the doubt, that it has license to do what it is doing, and I was operating under those assumptions, in which case my actions should be gauged against what Crosswire has been licensed to do, not another license that grants neither of us permission to distribute anything.</div>
<div> </div><div>If I was mistaken to place my faith that Crosswire had actually obtained license to distribute copyrighted text (above and beyond the general license which prohibits that), oh dear (I'm not the only one with a problem then)!</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jan 7, 2013 at 2:27 PM, 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: Andrew Thule <<a href="mailto:thulester@gmail.com">thulester@gmail.com</a>><br>
<div class="im">> It may be the case that the ISV foundations license to Crosswire is not as<br>
> restritive as Peter and Chris claimed and my action of sharing a compile<br>
> module on a separate server didn't in fact breach anything. Only by<br>
> inspecting Crosswire's license obligations can this be determined though.<br>
<br>
</div>Now, imagine the ISV license to CrossWire did indeed say<br>
<br>
"You can obtain a random 'updated' text from somewhere else and publish it too, including other parts of the Bible than those we supplied you with. Any of the subscribers of your mailing list may do the same"<br>
<br>
And we forgot to share that info....<br>
<br>
Oh, ouch!<br>
<br>
So when Random Dude publishes a module made up from random additional bits and publishes it on a random server under the name of ISV all kinds of people jumped down his throat and told him that he had no licence to do so and he might end up in trouble because he does something which is against the law, he might have had a defense but it was not accessible to him in that we did not publish along with our module the sentence:<br>
<br>
"You can obtain a random 'updated' text from somewhere else and publish it too, including other parts of the Bible than those we supplied you with. Any of the subscribers of your mailing list may do the same" "<br>
<br>
Oh, ouch!<br>
<br>
Now what exactly would Random Dude's best approach be? Given that he thinks he might just have more permissions that the default legal stance, as he suspects that CrossWire nefariously does not share all permissions they have.<br>
<br>
He might have asked from CrossWire before he published a random text with random additions on a random server.<br>
<br>
CrossWire might have told him "Oh, ouch! "We have indeed more permissions, and we need to update our module DistributionLicense".<br>
<br>
Or CrossWire might have told him - likely - "No, our license text is as it stands in the conf file".<br>
<br>
He might have asked from ISV.<br>
<br>
ISV might have told him "Go, do as you like".<br>
<br>
Or ISV might have told him - "No, we do not want you to publish a random text on a random server".<br>
<br>
Or ISV might have told him - "Here is a better text, use this one, and please add following license text to it"<br>
<br>
Oh, ouch!<br>
<br>
So, we have established Random Dude could have saved himself a lot of trouble by asking before he did something which on the face of it looked like A Bad Idea.<br>
<br>
But Random Dude did not ask before<br>
<br>
Now, as it stands, Random Dude feels aggrieved as he did something which looks like it was A Bad Idea. In his heart of hearts he feels it was a A Good Idea nevertheless, only all kinds of people tell him it was not.<br>
<br>
What pray, may Random Dude do now?<br>
<br>
He can take his random module from his random server and check again, does he have more rights than the law permits him as default?<br>
<br>
Maybe. Maybe not.<br>
<br>
CrossWire, assures him that he has not as far as they are concerned.<br>
<br>
So, what is left? He can go and ask ISV.<br>
<br>
Dear ISV,<br>
<br>
I have obtained from a random place a random document which looks pretty similar to your text. In fact it looks a lot better than what CrossWire has on its server. May I please pass it on via my server as something which looks like a CrossWire module? Or, alternatively could you even give me a better text than my random document?<br>
<br>
Love, hugs and kisses<br>
Random Dude<br>
<br>
It might work. Or it might not.<br>
<br>
Nevertheless.<br>
<br>
Bible publishers (unless they are of the more evil kind) do not behave music publishers and chances are Random Dude's actions, however ill advised they might have been, will not end up in court. So, not all is lost, Random Dude has learned that asking prior to doing things which on the face of it look like A Bad Thing, is always A Good Idea.<br>
<br>
Or maybe he has not learned and continues to blame everyone but himself.<br>
<br>
To be continued...<br>
<div class="HOEnZb"><div class="h5"><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>