Well my idea in answering this email is to put general names on clauses, For instance there are liability clauses in MPL, CDDL, and Apache2 if I am not mistaking. The conditions of these clauses are

FYI, the presence of the� depends on the application that is reading the file, so is often missed. A check for � can be done with a windows find command for the character string^u65533. Tom

Hi there, I would like to suggest the following to be added to the list of equivalent terms: “noninfringement“ and “non-infringement” --dmg --- Daniel M.

Talking about "synonyms". Today I discovered that the BSD-2-Clause-NetBSD is identical to the BSD-2-Clause (the template has been filled with the NetBSD Foundation). --dmg

Hi, I would like to report that the EUPL-1.1 license (https://spdx.org/licenses/EUPL-1.1) contains bad character in the following text in bullet 5: For the sake of this clause, "Compatible

Gary> I have a few questions and suggestions: Gary> - Would the range be any SPDX expression? Gary> - I would suggest a different term - maybe equivalent licenses. Synonyms Gary> imply two names

Hi Michel, Thanks for sharing this, it is quite interesting. This is a bit different, I think. from what Daniel is suggesting, though. I think Daniel is suggesting “synonyms” for license

HI Daniel, Thanks for the follow-up. That’s helpful to know. I think we will need to do, along the lines of our discussion on the call this week, is to review these cases individually and then

I’m not sure I understand why we need this. For the licenses that have been deprecated but can be otherwise represented using the new License Expression Syntax, I can see this being helpful, but

hi everybody, I am sorry I have been quiet during the last 6 months, but sometimes work gets on the way of doing fun work :) I want to announce that there have been some changes in Ninka lately. I

Hi everyone, New License List Requests from Sam.Ellis@... have been added to the Licenses Under Consideration list:

Great, thanks, Dennis. I also added a note to the meeting minutes from yesterday as a reminder for next call :) Jilayne

Well I think the proper way to do this would be standardize a decomposition of license conditions. For example "acknowledgement" means that there is some acknowledgement to put in the

Hi Jilayne, i looked into the Sleepycat license. You asked if others use it (I'll look into it, I think i have seen it used by others). but... One interesting aspect of this license is that because

Hi Jilayne, i looked into the Sleepycat license. You asked if others use it (I'll look into it, I think i have seen it used by others). but... One interesting aspect of this license is that because

Sure, in my queue to add to the tracking list.

Thanks Sam. Dennis - can you add this to the tracking list (as well as a couple others Sam requested) and we’ll make sure it’s on the agenda for the Jan 22 call? Thanks! Jilayne SPDX Legal Team

HI All, I realized this request fell through the cracks. It is on Dennis’ (new) tracking list here:

http://wiki.spdx.org/view/Legal_Team/Minutes/2015-01-08 Thanks for the great discussion today! The next Legal Call will be on Jan 22 Unless anyone raises an objection via the mailing list, we will

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