Tom, Moses is licensed under LGPL. But if the contributors agree, there's no reason that the tokenizer script can't also be simultaneously licensed under Apache.
Most open source projects only have a single license, but there are certainly cases where code is distributed under more than one license. Lane On Tue, May 29, 2018 at 10:27 AM, Tom Hoar <[email protected]> wrote: > 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, [email protected] wrote: > > Date: Tue, 29 May 2018 09:53:03 -0500 > From: Lane Schwartz <[email protected]> <[email protected]> > Subject: Re: [Moses-support] Dual Licensing or relicensing Moses > To: liling tan <[email protected]> <[email protected]> > Cc: moses-support <[email protected]> <[email protected]> > > 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 <[email protected]> > <[email protected]> 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 > > > > > _______________________________________________ > Moses-support mailing list > [email protected] > http://mailman.mit.edu/mailman/listinfo/moses-support > > -- When a place gets crowded enough to require ID's, social collapse is not far away. It is time to go elsewhere. The best thing about space travel is that it made it possible to go elsewhere. -- R.A. Heinlein, "Time Enough For Love"
_______________________________________________ Moses-support mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/moses-support
