Technical Team/Best Practices - Revision history

JackM: /* Annotations (replaces Reviewer Comments) */

2015-07-02T15:31:18Z

‎Annotations (replaces Reviewer Comments)

2015-07-02T15:30:59Z

‎Relationships and Multiple SPDX Documents in one

2015-07-02T15:30:43Z

‎Simple 2.0 Document

2015-07-02T15:30:29Z

‎Examples

2015-07-02T15:30:08Z

‎Examples

2015-06-23T13:52:04Z

‎Using the SPDX License List

2015-06-23T13:45:28Z

‎Annotations (replaces Reviewer Comments)

2015-06-23T13:45:11Z

‎JAR File

2015-06-23T13:44:42Z

‎Multiple SPDX Documents in one

2015-06-23T13:30:40Z

‎Examples

@@ Line 272: / Line 272: @@
 == Annotations (replaces Reviewer Comments) ==
-Example project: GNU Time http://mirror.sdunix.com/gnu/time/
+Example project: GNU Time 1.7  http://mirror.sdunix.com/gnu/time/
 This example shows document for a simple application with reviewer comments added after the fact.

@@ Line 215: / Line 215: @@
 == Relationships and Multiple SPDX Documents in one ==
-GNU CPIO - http://mirror.sdunix.com/gnu/cpio/  Has source, test code, documentation and its not "overly" large.
+GNU CPIO 2.10 - http://mirror.sdunix.com/gnu/cpio/  Has source, test code, documentation and its not "overly" large.
 This example shows  a single SPDX document for an application. Within that document are multiple SPDX documents with relationships that clarify the context the files are used in. Basically it is broken down as follows:

@@ Line 178: / Line 178: @@
 This is a simple use case illustrating an SPDX 2.0 Document. The GNU Time program uses a small number of files so its "easy" to get your head around and how an spdx document could be generated.
-Example project: GNU Time http://mirror.sdunix.com/gnu/time/
+Example project: GNU Time 1.7 http://mirror.sdunix.com/gnu/time/
 <br>

@@ Line 161: / Line 161: @@
 * GNU CPIO  version 2.10 - http://mirror.sdunix.com/gnu/cpio/
-* GNU Time  - http://mirror.sdunix.com/gnu/time/
+* GNU Time  version 1.7  - http://mirror.sdunix.com/gnu/time/
 * SPDX Tool - http://git.spdx.org/spdx-tools.git/

@@ Line 160: / Line 160: @@
 This section contains examples of working with SPDX documents. The examples, unless otherwise noted, will focus on illustrating a single concept or use case. The following projects are used throughout the use cases to make digesting the use cases easier as you will not have to continually re-familiarize yourself with a new application each time.
-* GNU CPIO - http://mirror.sdunix.com/gnu/cpio/
+* GNU CPIO  version 2.10 - http://mirror.sdunix.com/gnu/cpio/
-* GNU Time - http://mirror.sdunix.com/gnu/time/
+* GNU Time  - http://mirror.sdunix.com/gnu/time/
 * SPDX Tool - http://git.spdx.org/spdx-tools.git/

← Older revision		Revision as of 13:52, 23 June 2015
Line 183:		Line 183:

	== Using the SPDX License List ==		== Using the SPDX License List ==
		+
		+	These are various real world examples of how people are incorporating the SPDX License List.
		+
		+	{\| class="wikitable"
		+	\|-
		+	! Who
		+	! Link
		+	! Description
		+	\|-
		+	\| GitHub
		+	\| https://developer.github.com/v3/licenses/
		+	\| GitHub projects use the short identifiers from the license list to represent the licensing of their project.
		+	\|-
		+	\| Yota
		+	\| http://docs.yottabuild.org/reference/module.html
		+	\| Yota projects use the short identifiers from the license list and links back to the license list text to represent the licensing of their project.
		+	\|}
		+
		+	These are working notes:

	* a site which provides a pick list of SPDX licenses, and based on choice stores the declared license for an OSS project		* a site which provides a pick list of SPDX licenses, and based on choice stores the declared license for an OSS project

← Older revision		Revision as of 13:45, 23 June 2015
Line 234:		Line 234:

	=== JAR File ===		=== JAR File ===
−
−	~~This example shows an executable jar with an SPDX referencing back to another SPDX document that describes the source that built it.~~

	Example project: SPDX Tool - http://git.spdx.org/spdx-tools.git/		Example project: SPDX Tool - http://git.spdx.org/spdx-tools.git/
		+
		+	This example shows an executable jar with an SPDX referencing back to another SPDX document that describes the source that built it.

@@ Line 194: / Line 194: @@
 <br>
-== Multiple SPDX Documents in one ==
+== Relationships and Multiple SPDX Documents in one ==
-Jack: Use this for a test case of multiple documents related to one another and multiple documents in one.
+GNU CPIO - http://mirror.sdunix.com/gnu/cpio/  Has source, test code, documentation and its not "overly" large.
-[https://www.openssl.org/ OpenSSL Website]
+This example shows  a single SPDX document for an application. Within that document are multiple SPDX documents with relationships that clarify the context the files are used in. Basically it is broken down as follows:
-GNU CPIO - http://mirror.sdunix.com/gnu/cpio/  Has source, test code, documentation and its not "overly" large.
+{| class="wikitable"
 <br>