Hi Alan, The function is supported in the code, but there is no command line (yet). I plan on adding a command line in the next release of the tools. Gary

Gary, Are you referring to the SPDX tools 1.25? I’m not seeing a command to do license comparisons. Alan Tse Copyright and Open Source Licensing Director Western Digital Technologies,

Hi Allan, I've added this option on the triplecheck reporter. Given a text sample will show exact text matches on the license list: Tools -> Search Licenses It uses the previous version of the SPDX

Forgot to add - We do have a proposal to make some of the tools available on the website. One of our Google Summer of Code students is interesting in taking that on later this year or in the summer.

The SPDX Workgroup Tools has a function which will compare two license texts and report back if the text is equivalent based on the license matching guidelines. It would not be much work to write

To avoid accidentally including a duplicate in the future, is anyone aware of or using a tool to quickly compare a new license against the existing list of SPDX licenses to see if it is close?

Thanks Sam. Agree (Plexus Classworlds License, Open LDAP Public License v2.0.1 and the Fedora JCharts Variant are the same template license). Have we dealt with a situation in the past were we

This looks to me to be identical to existing licenses, http://spdx.org/licenses/Plexus and http://spdx.org/licenses/OLDAP-2.0.1, excepting for different copyrights, licensors, product names and email

The BSD-JCharts Variant is a template license in the Fedora list:https://fedoraproject.org/wiki/Licensing:BSD?rd=Licensing/BSD (Scan for “JCharts Variant”). The license has similarities to

from today’s call here: http://wiki.spdx.org/view/Legal_Team/Minutes/2014-11-24 PLEASE NOTE THE ACTION ITEMS FOR ALL IN #4, 5, AND 6!! Also posted minutes from last call:

Jilayne, As discussed, here’s a link for the NASA license that’s filled in (item 2a): http://worldwind.arc.nasa.gov/worldwind-nosa-1.3.html Alan Tse Copyright and Open Source Licensing

Proposed explanation text: Release 2.0 of the SPDX Specification introduces license expression syntax that supports the ability to identify common variations on standard licenses without the need to

Don’t forget our call today (instead of Thursday) for the Legal Team @ 10am PT / 1pm ET We’ve got a lot to cover, so please review the agenda and various links prior to the call, so we can jump

Hi All, The following issues have been resolved for the next release of the license list as described below. If anyone has any concern with how it has been resolved, please respond to this email

Hi, I would like to propose the addition of the ICU license to the SPDX license list. As compared to the existing SPDX licenses, ICU most closely resembles the X11 license. As compared to the X11

Hello SPDX Legal, Please ignore meeting invites fromthomas.incorvia@... (my personal email address). There is an Outlook 10 / Google Calendar bug that causes forwarded recurring meeting

This event has been changed. more details » Changed: Updated Invitation: SPDX Legal Team Meeting @ Every 2 weeks from 1pmto 2pm on Thursday from Thu Mar 6 to Thu Dec 25(mdolan@...) Changed: This

Hi All, Just a reminder that we have our legal conference call tomorrow, Thursday at 10am PT. We have quite a bit to cover! Agenda will include: 1) new license requests: (see email threads with

This is an interesting scenario, as it’s not really an open source license, but really a binary license with permissive grants and yet also a restriction against reverse engineering, etc. That’s