I like the idea of having synonyms - it will help when we compare SPDX documents to determine that two licenses are really the same.
I have a few questions and suggestions: - Would the range be any SPDX expression? - I would suggest a different term - maybe equivalent licenses. Synonyms imply two names for the same subject or object. I think this is more of a relationship between a license and an expression. - It would be great to have this be machine paresable so that the tooling could understand it. For this to work, we would need to introduce another term in the standard to hold the information. I would propose this would be a release 2.1 candidate feature. - Before the new term is implemented, we could record this information in the notes for a given license. - If we wanted to state that 2 SPDX 2.0 licenses are really the same, we could add other web pages for this licenses that refer to the correct SPDX license (e.g. http://spdx.org/licenses/preview/StandardML-NJ). Gary > -----Original Message----- > From: [email protected] [mailto:spdx-legal- > [email protected]] On Behalf Of dmg > Sent: Thursday, January 8, 2015 10:47 AM > To: J Lovejoy > Cc: SPDX-legal > Subject: Re: Call this Thursday!! > > The idea is that each license has a name. > > Then some licenses might have synonyms. > > The old GPLv2 WITH Bison Exception is now known as the GPL-2 WITH > Bison Exception. The old name was GPL-2.0-with-bison-exception which is > deprecated. > > What I am suggesting is that the name: > > GPL-2.0-with-bison-exception = GPL-2 WITH Bison Exception > > this way the old name is not deprecated, it is just a synonym of the > GPL-2 WITH Bison Exception. So people can continue to use GPL-2.0-with- > bison-exception > > synonyms could also have an approval process the same as licenses. > > On Tue, Jan 6, 2015 at 9:14 PM, J Lovejoy <[email protected]> > wrote: > > Hi all and Happy New Year!! > > > > We will have our first call of 2015 this Thursday, same Bat-time, > same > > Bat-channel. That is, 11am Mtn Time / 1pm Eastern Time at the > > following > > dial-in: > > +1-857-216-2871 > > User PIN: 38633 > > > > I just sent out an invite for this week only. Will get a recurring > > invite out soon. > > > > On the agenda will be: > > > > 1) quick update on Collab Summit > > > > 2) SPDX License List 2.0 - release candidate update!! > > > > 3) compound licenses (see various discussion on email list re: > Python, > > OpenSSL, etc. raised by Sam Ellis) > > > > Cheers, > > Jilayne & Paul > > SPDX Legal Team co-leads > > > > > > > > > > _______________________________________________ > > Spdx-legal mailing list > > [email protected] > > https://lists.spdx.org/mailman/listinfo/spdx-legal > > > > > > -- > --dmg > > --- > Daniel M. German > http://turingmachine.org > _______________________________________________ > Spdx-legal mailing list > [email protected] > https://lists.spdx.org/mailman/listinfo/spdx-legal _______________________________________________ Spdx-legal mailing list [email protected] https://lists.spdx.org/mailman/listinfo/spdx-legal
