Hi, I’d like to request NAIST’s ipadic license be added to the SPDX License List. Proposed license details are: Short identifier: IPADIC Full Name: NAIST IPADIC License URL: This is the most

Sam: I agree with you, both licenses are common enough in the wild. Both the MD4 and MD5 notices are found in RFCs, which is a good reference URL IMHO as they were crafted and submitted there by

Hi, I’d like to request the addition of RSA’s Message-Digest license to the SPDX License List. I have seen two variants of this license for MD4 and MD5 algorithms, with the difference between

Hi All, Below is the mid-2014 research on the Jython license. I was no involved in the follow up. Please also consider this information along with Sam Ellis'

J> Hi Daniel, J> I’m not seeing this error. Looks right on both the current license list and the preview for 2.0-rc2 at http://spdx.org/licenses/preview/ <http://spdx.org/licenses/preview/> Sorry

Hi, I’d like to propose adding the license for Jython (a Java implementation of Python) to the SPDX License List. As is a similar case for Python, portions of the Jython software are actually

from today’s call - http://wiki.spdx.org/view/Legal_Team/Minutes/2015-01-22 Thanks! Jilayne SPDX Legal Team co-lead opensource@...

Hi Daniel, I’m not seeing this error. Looks right on both the current license list and the preview for 2.0-rc2 at http://spdx.org/licenses/preview/ ?? thanks, Jilayne SPDX Legal Team

Also, regarding 2.0 - please check out the revised SPDX License List v2.0-rc2 on the web here: http://spdx.org/licenses/preview/ Changes have been made as per our discussions last call (pasted below

You should have gotten a repeating invite for our usual call time on every other Thursday. Dial-in info can be found here: http://wiki.spdx.org/view/Legal_Team Agenda for today’s call: 1) new

The Legal Team meets every other Thursday at 18:00 GMT (10:00AM PT, 11:00 MT, 12:00 CT, 1:00PM ET). Meeting minutes are posted here: http://wiki.spdx.org/view/Legal_Team/Minutes Call this number:

That seems like a good one to add!! Jilayne

I’ve fixed the characters, made sure I saved to UTF-8 format and pushed to Git. There are a few characters that might still show up funny, so Gary - if you could run this utility again once these

Thanks all. Should be an easy fix for the next release. Will get on it!! Jilayne Sent from a small, rectangular device.

Thanks Tom for the suggestion and thanks Sam for catching the error. I've added a check in the utility we use to create the license list pages. I found 5 additional licenses in the 2.0rc2 version

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