I think this is a fanstastic idea, the idea of progamatically being able to
detect Status of a module programatically! Very good suggestion.
On this example:
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
Peter, I've not received your email yet, but look forward to it.
Let me address your concern. I have no intention of distributing modules
exclusively licensed to Crosswire. I think I currently am, however (as I
previously said to Chris) I invent you to contact me with concerns and
request.
I
DM, I agree that not having thought through mirror management procedurally
(policy and best backpractice) is reason enough to hold off on such a
venture, but those problems are typically trivial to solve given effective
communication.
Since technology is subordinat to intent, what needs to be
Is there a URL that oultines what this patch does? I agree this is going
to be very useful change, but confess - I don't yet understand what this
patch is doing .
(Also, thanks indeed Greg for your efforts)
~A
On Sun, Jan 6, 2013 at 2:29 PM, Troy A. Griffitts scr...@crosswire.orgwrote:
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.
Applications that serve the web, such as SwordWEB and are not hosted on the
Mirror management is a moot issue if the software doesn't support mirrors. I
have no plans to add such to JSword, unless it is added to SWORD first. I
highly doubt that it will be added to SWORD until a problem with resiliency
creates a real need. Even then, I'm not sure that that will be used
On Sun, Jan 6, 2013 at 11:12 AM, DM Smith dmsm...@crosswire.org wrote:
No, we cannot publish the terms of licensing agreements. Think about it.
These are confidential, privileged contracts between organizations.
Umm, with software Licenses, Acceptable Use Policies, Copyright
Restrictions and
On Jan 7, 2013, at 12:58 PM, Andrew Thule thules...@gmail.com wrote:
The wording of your request is inviting a go pound sand response. Please be
careful in how you word things.
DM, I will be careful how I word things because such advice is always prudent
advice.
That said, I
My experience with mirrors is that mirrors are done at the level of the
Operating Systems. Tools like 'rsync', 'lsync', 'chron' etc manage the
integrity and distribution of these things.
That said, I think what you're saying is that you believe the Sword client
needs some additional support to
Sorry, I misunderstood. I see what you're saying now.
On Mon, Jan 7, 2013 at 1:03 PM, DM Smith dmsm...@crosswire.org wrote:
On Jan 7, 2013, at 12:58 PM, Andrew Thule thules...@gmail.com wrote:
The wording of your request is inviting a go pound sand response.
Please be careful in how
Except that the suggestion to support 'License Awareness' programatically I
take to mean 'Sword Library, and the Sword Library need not be narrowly
defined to suggest only Bible Programs can make use of the Library.
~A
On Mon, Jan 7, 2013 at 12:47 PM, DM Smith dmsm...@crosswire.org wrote:
The
On Mon, Jan 7, 2013 at 11:58 AM, Andrew Thule thules...@gmail.com wrote:
On Sun, Jan 6, 2013 at 11:12 AM, DM Smith dmsm...@crosswire.org wrote:
No, we cannot publish the terms of licensing agreements. Think about it.
These are confidential, privileged contracts between organizations.
Umm,
DM, all of which you said is reasonable; no issues from me. My point was
in the efforts to assist with module develoment, I apparently crossed some
line. I offered to send an OSIS update, and made a testing version of it
available. The debate started (as you note) because of my making a testing
I think we've got the answers across multiple threads. DM answers your
question in my thread. others in other threads.
1. All modules are fair game for sword front ends to use and display.
2. Modifying modules and/or redistributing is not allowed for modules
marked as Copyrighted permission
Coming back to my original point.
Is there appetite for such support in the sword modules?
Peter sends to suggest 'Maybe'. DM seems to suggest 'No'.
I'm happy to make my enhancements in the STEP code if nobody wants this.
Chris
Chris
On 7 Jan 2013 18:10, Andrew Thule thules...@gmail.com
On Mon, Jan 7, 2013 at 12:19 PM, Andrew Thule thules...@gmail.com wrote:
What I did have a hard time with was being publicly held accountable to
license restrictions reasonably unknown to me (and apparently secret), while
having the issue made personal. It isn't reasonable to assume I knew
Umm, Greg, you realise that under Copyright Law Crosswire has no right
to Copy right text
either (at least not without license) or to void its own license agreement?
If Crosswire is licensed to distribute Copyright text for which it is not
the owner:
The Copyright Owner must establish the terms
Von: Chris Burrell ch...@burrell.me.uk
Is there appetite for such support in the sword modules?
I do think there is value in this for supporting a Web API. You could host any
number of modules with many different licenses and many different API users
could have a reasonably automatic way
Greg, its not clear you understand copyright law.
Copyright Law is generic .. it applies generally. If you read American,
Canadian, or European copyright law you won't find anything mentionion
CrossWire, ISV, ESV specifically. That means it lays down principles.
Therefore, copyright law with
On Jan 7, 2013, at 12:58 PM, Andrew Thule thules...@gmail.com wrote:
On Sun, Jan 6, 2013 at 11:12 AM, DM Smith dmsm...@crosswire.org wrote:
No, we cannot publish the terms of licensing agreements. Think about it.
These are confidential, privileged contracts between organizations.
Von: Andrew Thule thules...@gmail.com
Sorry, but Crosswire has an obligation (under Copyright law) as
distributor
to share with its users the terms of each Copyright owner's license.
It does.
As per module conf entry re DistributionLicense. It tells you everything you
must know.
If you
I guess I need more information on mirrors.
Let's say that there are to mirrors X and Y. For what ever reason, X has A, B,
C, D and Y has A, D, E. Software is configured to use Y. When it goes to get a
list of files, what does it get? If it requests B, what does it get? Same
questions for
Chris this list in an of itself is not sufficient (legally) to establish
these principles. It is the Copyright owners who make this determination,
not Crosswire list members.
Each Copyright owner is entitled to impose unique restrictions on the use
of their texts. CrossWire is bound on a module
On Mon, Jan 7, 2013 at 12:43 PM, Andrew Thule thules...@gmail.com wrote:
Greg, its not clear you understand copyright law.
Copyright Law is generic .. it applies generally. If you read American,
Canadian, or European copyright law you won't find anything mentionion
CrossWire, ISV, ESV
Ok. In your example you have two levels of mirrors, root and banch.
If we assume all mirrors are synced (exactly the same), the client (if it
supports more than a preferred mirror) will check its mirrors in the order
they are specified.
So in your case, Y will check A. D. and E. in that order
Von: Andrew Thule thules...@gmail.com
It may be the case that the ISV foundations license to Crosswire is not as
restritive as Peter and Chris claimed and my action of sharing a compile
module on a separate server didn't in fact breach anything. Only by
inspecting Crosswire's license
On Mon, Jan 7, 2013 at 1:44 PM, DM Smith dmsm...@crosswire.org wrote:
Each copyright owner has several fields in the conf that they can fill out
with that information. Most use the About field. A few use some other
fields. Consult the module's conf for the information that you want. If it
is
Greg, respectfully you're still missing the point.
Because a work is Copyright, doesn't grant Crosswire the right to inform me
of anything, since CrossWire is not the CopyRight owner.
It is only if the Copyright Owner grants Crosswire rights (and
restrictions) though the use of a license to use
Peter,
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.
I agree, that if I am bound by those licenses I have no right to distribute
anything, but neither does
On Jan 7, 2013, at 1:19 PM, Andrew Thule thules...@gmail.com wrote:
DM, all of which you said is reasonable; no issues from me. My point was in
the efforts to assist with module develoment, I apparently crossed some line.
I offered to send an OSIS update, and made a testing version of it
On Jan 7, 2013, at 2:04 PM, Andrew Thule thules...@gmail.com wrote:
Ok. In your example you have two levels of mirrors, root and banch.
If we assume all mirrors are synced (exactly the same), the client (if it
supports more than a preferred mirror) will check its mirrors in the order
Andrew and others,
This thread is counterproductive-- and has been for quite some time.
It is now closed.
I was CC:ed on the email Peter sent you (Andrew) privately which
outlines explicitly how he was able to obtain multiple modules from your
mirror which indeed have:
Hi,
Sorry for sending this to the wrong list, but this list is more active than
osis-users list , My previous post in osis-users list didn't got attention and
i got just 2 replies and no one replied after my last reply .
The problem still exists and I've made many many trials, trying to get it
On Mon, Jan 7, 2013 at 1:37 PM, Andrew Thule thules...@gmail.com wrote:
Greg, respectfully you're still missing the point.
Because a work is Copyright, doesn't grant Crosswire the right to inform me
of anything, since CrossWire is not the CopyRight owner.
Correct. Nor does it mean CrossWire
DM,
Let's not reopen the DSS issue, thought it is the same issue. Crosswire is
not the Copyright Owner of a single DSS translations. So as long as
Crosswire is playing no official role in their digitization or
distribution, CrossWire has absolutely nothing to say on the matter.
That said, I
On Jan 7, 2013, at 3:09 PM, Andrew Thule thules...@gmail.com wrote:
Let's not reopen the DSS issue
Agreed.
I think that it was the foundation for the tone of responses you received. I
think it was the elephant in the room. I thought you'd like to know that.
In Him,
DM
I concur with DM, the Sword/JSword/UIs would have to change. I've had that
issue with having modules in both the normal repo and the (old?) beta
repository. The frontends give a false impression as to which module came
from which repository.
On 7 January 2013 19:50, DM Smith
The previous directive to close these discussions extends to this
thread, as well. The same conditions apply for action:
CrossWire considers the DSS materials you post on your website to be
under copyright and not legal for you to distribute. Our policy is to
not allow illegal content to be
If you think about Linux distributions, you see a number of approaches:
1 Software makes the mirror selection
2 User makes Mirror selection.
Given the clients cited above, only if the Software chooses the mirror are
coding changes necessary. The Software developer must also make decisions
about
Sent from my phone, hence this email may be short...
On 08/01/2013, at 8:51, Andrew Thule thules...@gmail.com wrote:
As long as Crosswire has policies in place govererning official mirrors there
should no no worries mirrors are out of sync, in which case preferred mirror
selection can be
Troy,
CrossWire is itself distributing Copyright Material, unwilling to provide
evidence it posses License to do this. Therefore since you're accusing me
of this same thing, the same standard applies. Although I don't impose
ultimatums on CrossWire though you are with me, feel free to validate
Agreed. That's another way of stating it: until Crosswire decides on the
issue, there's no sense in developers discussing it..
~A
On Monday, January 7, 2013, Nic Carter wrote:
Sent from my phone, hence this email may be short...
On 08/01/2013, at 8:51, Andrew Thule thules...@gmail.com
I have finally found time to start looking at adding sword module support
to Wide Margin (http:\\widemargin.org) again.
And I have a question about copyright and licencing.
Currently Wide Margin uses a sqlite database to store it's bible text. The
database is full text indexed which provides the
Von: Daniel Hughes tramps...@gmail.com
Am I allowed to pull the text out of the sword module once it is installed
(using the sword libs) and put it in my local sqlite database.
Not a lawyer, so my advice might be of limited value. Many of our modules are
public domain and essentially you
44 matches
Mail list logo
