SPDXReports2014

Rationale for Choosing the CC0 1.0 for SPDX File Data (SPDX-TR-2014-1)

Title: Rationale for Choosing the CC0 1.0 for SPDX File Data Author(s): Mark Gisi, Wind River Report Id:: SPDX-TR-2014-1 Report: PDF link Abstract: The SPDX Legal working group evaluated several license candidates that could be used to cover the data contained in a SPDX file and selected the Creative Commons CC0 1.0 - Universal Public Domain Dedication license. We present the license candidates that were considered and the respective pros and cons of each.

Accessing SPDX Licenses (SPDX-TR-2014-2)

Title: Accessing SPDX Licenses Author(s): Gary O'Neall, Source Auditor Report Id:: SPDX-TR-2014-2 Report: PDF link Abstract: The Software Products Data Exchange (SPDX) maintains a list of standard licenses commonly used in open source software. This document describes various methods of accessing the current and previous versions of the list. Several methods of accessing the license list are provided ranging from simply reading the license list on the website to programmatically accessing the license list information online. This document is organized from the easiest method of access targeted at more casual users to the most sophisticated access targeted at software programmers. This document does not go into any details on how to submit new licenses or suggest changes to existing licenses. Information on the license list process and additional information on SPDX licenses can be found at http://spdx.org/spdx-license-list.

SPDX Version 2.0 – Requirements and User Stories (SPDX-TR-2014-3)

Title: SPDX Version 2.0 – Requirements and User Stories Author(s): Kirsten Newcomer, Black Duck Software Report Id:: SPDX-TR-2014-3 Report: PDF link Abstract: The goal of this document is to provide a high-level view of the features targeted for v2.0 of the SPDX specification and to provide a mapping of use cases to features. Certain terminology in the document is taken from the Scrum software development methodology. Scrum is a form of agile software development. The use of the term Epic is one such example. An Agile Epic is a group of related user stories. A User story is an independent, testable requirement.