[sword-devel] Finding out copyright programatically

Chris Burrell chris at burrell.me.uk
Mon Jan 7 11:26:13 MST 2013


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" <thulester at gmail.com> wrote:

> 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 <dmsmith at crosswire.org> wrote:
>
>> 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 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.
>>
>> 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.
>>
>> In Him,
>> DM
>>
>> On Jan 7, 2013, at 12:31 PM, Andrew Thule <thulester at gmail.com> wrote:
>>
>> 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 module
>> through Xiphos from Crossway? Presumably not? Or do the Xiphos owners need
>> to seek permission from Crossway? Possibly?"
>>
>> This is also a good example.
>>
>> 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.
>>
>> 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.
>>
>> ~A
>>
>>
>>
>>
>> On Sun, Jan 6, 2013 at 5:59 PM, DM Smith <dmsmith at crosswire.org> wrote:
>>
>>> 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.
>>>
>>> As Peter mentioned there are (at least) two questions that need to be
>>> answered:
>>> Redistributable? Are there modules that cannot be distributed at all.
>>> Commercial? Are there modules that preclude the use in a commercial
>>> context. (E.g. Ad driven).
>>>
>>> Note, when STEP is a desktop application or a web application, these
>>> might have different meanings.
>>>
>>> Here are details of how to dig it out today:
>>>
>>> o.c.j.book.sword.ConfigEntryType.DISTRIBUTION_LICENSE
>>> defines the list of acceptable values.
>>>
>>> You can access this via o.c.j.book.BookMetadata.getProperty as in:
>>>
>>>
>>> o.c.j.b.BookMetadata.getProperty(o.c.j.b.sword.ConfigEntryType.DISTRIBUTION_LICENSE.getName())
>>>
>>> You can then compare it to expected values as in "Copyrighted;
>>> Permission to distribute granted to CrossWire"
>>>
>>> Hope this helps.
>>>
>>> In Him,
>>>         DM
>>>
>>> On Jan 6, 2013, at 12:05 PM, Chris Burrell <chris at burrell.me.uk> wrote:
>>>
>>> > Hi
>>> >
>>> > 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.
>>> >
>>> > 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.
>>> >
>>> > 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)
>>> >
>>> > 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.
>>> >
>>> > If, we think, this is consistent enough, I'd be happy to implement a
>>> simple getter on the BookMetadata object in JSword.
>>> >
>>> > 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
>>> > Chris
>>> >
>>> > _______________________________________________
>>> > sword-devel mailing list: sword-devel at crosswire.org
>>> > http://www.crosswire.org/mailman/listinfo/sword-devel
>>> > Instructions to unsubscribe/change your settings at above page
>>>
>>>
>>> _______________________________________________
>>> sword-devel mailing list: sword-devel at crosswire.org
>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>> Instructions to unsubscribe/change your settings at above page
>>>
>>
>> _______________________________________________
>> sword-devel mailing list: sword-devel at crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>>
>>
>>
>> _______________________________________________
>> sword-devel mailing list: sword-devel at crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>>
>
>
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20130107/90f50e63/attachment.html>


More information about the sword-devel mailing list