Legal Team/License List/Licenses Under Consideration

From SPDX Wiki
Jump to: navigation, search

The SPDX Legal team tracks new License List Requests at:
Refer to the "Licenses Readme" worksheet in the document for an explanation of each of the columns in the list.

The Legal team also tracks License Exceptions List Requests in the document at:
Refer to the "Exceptions Readme" worksheet in the document for an explanation of each of the columns in the list.

Older license requests from release 1.20 or earlier are identified in the table below. Entries submitted prior to release 1.18 had their Date Submitted arbitrarily set to January 1, 2013.

Status Name Explanation
Accepted in v__ The license was added to indicated version of the SPDX License List. The SPDX License List version indicated may be yet to be released in the case where a license is accepted in between SPDX License List releases.
Under Review A license addition has been requested and is currently under review.
Not Accepted The license was reviewed by the Legal Team and it was decided to not add the license to the SPDX License List at this time.
On Hold This means that more research is needed or there are other extenuating factors that have prevented a decision on the addition of the license to be made. See the Notes for more information.

Licenses Accepted in v1.20

License Full Name Short Identifier Template Needed Status Date Submitted Notes
Caldera License Caldera No 3 Accepted in v1.20 2014-04-01 See

Submitted by Maciej Wereski. "This license is used in some older software (e.g. The Traditional Vi)."

Per Tom Incorvia: "Due primarily to the licensing information stated prior to the slightly modified BSD-4-Clause, I would recommend that this be reviewed by SPDX as a license distinct from the BSD-4-Clause. The platform limitations, in particular, appear to make this a distinct license."

Because of significant differences in license terms, it was decided to call this license the Caldera License (Caldera) rather than BSD 4-clause Caldera License (BSD-4-Clause-Caldera), even though the text is generally structured in a manner similar to the BSD-4-Clause.

Bzip2 License Bzip2 No 3 Accepted in v1.20 2014-02-10 See

Submitted by Oliver Fendt of Siemens AG. "bzip2 is a popular package and often used, thus an entry in the spdx license list would make life easier."

Creative Commons 4.0 License Family (see details below) 3 Accepted in v1.20 2013-11-27 Six new licenses, detailed below. See email from Oliver Fendt.

See discussion here: and access the six variants here:

Creative Commons Attribution 4.0 International Public License CC-BY-4.0 No 3 Accepted in v1.20 2014-07-09
Creative Commons Attribution-NoDerivatives 4.0 International Public License CC-BY-ND-4.0 No 3 Accepted in v1.20 2014-07-09
Creative Commons Attribution-NonCommercial 4.0 International Public License CC-BY-NC-4.0 No 3 Accepted in v1.20 2014-07-09
Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International Public License CC-BY-NC-ND-4.0 No 3 Accepted in v1.20 2014-07-09
Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International Public License CC-BY-NC-SA-4.0 No 3 Accepted in v1.20 2014-07-09
Creative Commons Attribution-ShareAlike 4.0 International Public License CC-BY-SA-4.0 No 3 Accepted in v1.20 2014-07-09
Fedora Good List Licenses (see list) (see list) 3 Accepted in v1.20 2013-08-01 Project to reconcile the "Fedora Good List" at

with the SPDX License List. Review status details are available at

Ruby License Ruby No 3 Accepted in v1.20 2013-09-12 see discussion here:

working with Ruby project to come up with accurate way to identify different license variations

The substantive part of the license text at will be added/updated in v1.20 of the SPDX License List.

Zend Engine License 2.00 Zend-2.00 No 3 Accepted in v1.20 2013-01-01 different license for Zend Engine and Zend Framework and variations as such. more research needed. see research done thus far in attachment below

Zend software is now under the BSD license. See The older license text is available via wayback:

Unicode Terms of Use Unicode-TOU No 3 Accepted in v1.20 2013-01-01 to add? (from FSF list) - Unicode LIcense Agreement for Data Files and Software – are there other versions or other Unicode licenses? It does not appear so, based on the info on this page: ... → realized that Fedora has a different Unicode license(for Character Database, Fedora uses short identifier: UCD, found here: ) than the Unicode license above from the FSF list. more research needed to see if there are others, so can appropriately name, etc.

License on this page will be added:

Processed License Requests

License Status Date Submitted Notes
GPL-2.0 identifier 3 Not Accepted 2013-01-01 issue of potential confusion with short identifier "GPL-2.0" meaning GPLv2 only; whereas GPLv2 or later, uses short identifier "GPL-2.0+" should short identifier be changed to "GPL-2.0-only" for symmetry and clarity?
  1. what would the ramifications of changing a short identifier be? had said we wouldn't not change short identifiers
  2. alternatively, could add in Notes field for all GNU licenses that short identifier "GPL-2.0" = GPL v2 only for clarification (but will this be "obvious" enough?

The "or later" concept is addressed with the SPDX License Exceptions List in v2.0

MX4J License 3 Not Accepted 2014-04-04 See

Submitted by via bugzilla. "The MX4J license is a license that is identified by multiple license scanning tools (including Ninka and FOSSology), but it is not included in the SPDX 1.2 Standard License List. Consider including this license in the 2.0 spec?"

Per Dennis Clark: "Opinion: A quick glance at the MX4J license text indicates that it is really Apache 1.1, even though the authors have given it the specific name of The MX4J License, Version 1.0. Rather than perpetuate the redundant license name, it might be better for scanning tools to recognize this as Apache 1.1." This request will be reviewed by the SPDX Legal Working Group.

It was determined that the MX4J text is the same as the Apache 1.1, which allows for variations in Year, Owner and Contact, so it is already covered by that license and there is no need to add this one.

Microsoft patterns & practices License (MSPPL) 3 Not Accepted 2014-03-05 See

Submitted by Oliver Fendt. "This license is used quite frequently in the context of the programming language C#"

The major concern regarding this license text is the lack of a specific Version designation for this text by Microsoft, which could change the text at any time without providing a new unique identifier. This is a common situation with many free proprietary licenses that are specific to a vendor and contain various restrictions that tie the license to that vendor only. It would be better to capture the specific applicable text using the SPDX License Ref option when specifying that this license applies to a software package being used.

Eclipse Distribution License - v 1.0 3 Not Accepted 2014-03-03 See

Submitted by Mike Milinkovich of the Eclipse Foundation. "The EDL-1.0 is used by Eclipse projects with the approval of the Eclipse Board of Directors." The license is used in multiple Eclipse projects.

However, the license text is the same as the SPDX BSD-3-Clause, which allows for variations in Year and Owner, so it is already covered by that license and there is no need to add this one.

IBM PowerPC Initialization and Boot Software (IBM-pibs) 2 Accepted in v1.19 2013-7-30;a=blob;f=arch/powerpc/cpu/ppc4xx/4xx_pci.c

A disjunctive license offering a choice of GPL 2.0 or an IBM open source license. Also see:

Sun Industry Standards Source License 1.2 (SISSL-1.2) 2 Accepted in v1.19 2013-7-18

" It also seems that there is a 1.2 version of this license ( )." from Camille Moulin via, in the context of a discussion about whether the ID for SISSL (which has no version suffix) should be changed. Also see: and

Artistic License (Perl) 1.0 2 Accepted in v1.19 2013-6-03

Even though, the ‘Artistic License – 1.0’ and ‘Artistic License – 2.0’ are included in the SPDX License List, I feel a need to also include the ‘‘Artistic License (Perl) – 1.0’. The ‘Artistic License (Perl) - 1.0’ contains an extra clause and is used in a wide range of PERL based programs. Discussed on 6/6 legal call: --> conferred with OSI and decided to add Artistic-1.0-cl8 and Artistic-1.0-Perl to reflect all contingencies here

Do What The F*ck You Want To Public License 3 Not Accepted 2013-12-27 we have version 2.0 on the list, but do not have previous versions. Also question about whether version number should be added to short identifier (i.e., WTFPL-2.0 instead of WTFPL currently)

Insufficient usage.

Unlicense 3 Accepted in v1.19 2013-01-01 see thread here:
FLORA 4 Not Accepted 2013-01-01 decided not to add at this point in time, pending completion of license inclusion guidelines. see for most recent thread on the topic and meeting minutes where discussed at: Legal_Team/Minutes/2012-10-31