Moses-support Digest, Vol 139, Issue 15

Send Moses-support mailing list submissions to
moses-support@mit.edu

To subscribe or unsubscribe via the World Wide Web, visit
http://mailman.mit.edu/mailman/listinfo/moses-support
or, via email, send a message with subject or body 'help' to
moses-support-request@mit.edu

You can reach the person managing the list at
moses-support-owner@mit.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Moses-support digest..."


Today's Topics:

1. Re: Dual Licensing or relicensing Moses (Tom Hoar)


----------------------------------------------------------------------

Message: 1
Date: Tue, 29 May 2018 22:27:44 +0700
From: Tom Hoar <tahoar@slate.rocks>
Subject: Re: [Moses-support] Dual Licensing or relicensing Moses
To: moses-support@mit.edu
Message-ID: <bab7c4c2-ed43-bcb2-6b10-f288ecd25a12@slate.rocks>
Content-Type: text/plain; charset="utf-8"

Hi Liling,

I'm not sure what you mean by "dual licensing or re-license." Software
is published under one license, which may or may not be compatible with
other licenses. The Moses trunk is licensed under LGPL2.1, except those
modules specifically republished under their respective licenses. My
copy of tokenizer.perl script shows it's LGPL2.1. Under those terms, any
changes to its code, if published, must be published under LGPL2.1 or
newer. It looks to me like you've done that.

You might have problems including a Python version of tokenizer.perl in
NLTK because NLTK is licensed under the incompatible Apache License
Version 2.0, at least according to this site,
https://www.quora.com/What-are-the-major-differences-between-GNU-LGPL-v3-and-v2-1.

The source code's copyright IPR is the property of the University of
Edinburgh. It's polite to track down the authors/contributors, but it's
not necessary. The University's legal/intellectual property department
is the authority and best source of information about licensing.

Tom


On 5/29/2018 9:53 PM, moses-support-request@mit.edu wrote:
> Date: Tue, 29 May 2018 09:53:03 -0500
> From: Lane Schwartz<dowobeha@gmail.com>
> Subject: Re: [Moses-support] Dual Licensing or relicensing Moses
> To: liling tan<alvations@gmail.com>
> Cc: moses-support<moses-support@mit.edu>
>
> Matt,
>
> Did you ever track down the people who contributed to the tokenizer? It
> seems like we should be able to dual license that script. It would be very
> nice to be able to include the Moses tokenizer and detokenizer as part of
> NLTK.
>
> Lane
>
>
> On Fri, Apr 20, 2018 at 12:38 AM, liling tan<alvations@gmail.com> wrote:
>
>> Dear Moses Devs and Community,
>>
>> Sorry for the delayed response.
>>
>> We've repackaged the MosesTokenizer Python code as a library and made it
>> pip-able.
>> https://github.com/alvations/sacremoses
>>
>> I hope that's okay with the Moses community and the license compliance is
>> good with this now.
>>
>> Regards,
>> Liling
>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20180529/95032e50/attachment-0001.html

------------------------------

_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support


End of Moses-support Digest, Vol 139, Issue 15
**********************************************

Tweet