SPDX Wiki - User contributions [en]

Technical Team/SPDX RDF Vocabularies and Terms/1.1/Vocabulary

2012-08-29T22:32:50Z

Pezra:

<h2>1.1 (Final)<h2>
<p>This page contains the latest draft version of the SPDX RDF vocabulary in various formats.  These are not considered stable at this time.</p><p>This document is under revision control at <a href="http://git.spdx.org/spdx-spec.git">http://git.spdx.org/spdx-spec.git</a>.</p><p>The HTML version is the authorative version.  The other versions are generated from the HTML for your convience.</p>

File:Terms-7.txt

2012-08-29T22:32:43Z

Pezra:

Abstract vocabulary description (distilled from annotated HTML)

File:Terms.ttl--7.txt

2012-08-29T22:32:29Z

Pezra:

Turtle (distilled from annotated HTML)

File:Terms.rdf--7.xml

2012-08-29T22:32:14Z

Pezra:

RDF/XML (distilled from annotated HTML)

File:Terms-7.html

2012-08-29T22:31:58Z

Pezra:

HTML (master version)

Technical Team/SPDX RDF Vocabularies and Terms/1.1/Vocabulary

2012-08-24T17:19:03Z

Pezra:

<h2>1.1-DRAFT (24 Aug 2012 17:18 UTC/6b70e2)<h2>
<p>This page contains the latest draft version of the SPDX RDF vocabulary in various formats.  These are not considered stable at this time.</p><p>This document is under revision control at <a href="http://git.spdx.org/spdx-spec.git">http://git.spdx.org/spdx-spec.git</a>.</p><p>The HTML version is the authorative version.  The other versions are generated from the HTML for your convience.</p>

File:Terms-6.txt

2012-08-24T17:18:55Z

Pezra:

Abstract vocabulary description (distilled from annotated HTML)

File:Terms.ttl--6.txt

2012-08-24T17:18:41Z

Pezra:

Turtle (distilled from annotated HTML)

File:Terms-6.html

2012-08-24T17:18:26Z

Pezra:

HTML (master version)

File:Terms.rdf--6.xml

2012-08-24T17:17:59Z

Pezra:

RDF/XML (distilled from annotated HTML)

Technical Team/SPDX RDF Vocabularies and Terms/1.1/Vocabulary

2012-08-24T17:06:29Z

Pezra:

<h2>1.1-DRAFT (24 Aug 2012 17:03 UTC/9e176e)<h2>
<p>This page contains the latest draft version of the SPDX RDF vocabulary in various formats.  These are not considered stable at this time.</p><p>This document is under revision control at <a href="http://git.spdx.org/spdx-spec.git">http://git.spdx.org/spdx-spec.git</a>.</p><p>The HTML version is the authorative version.  The other versions are generated from the HTML for your convience.</p>

File:Terms-5.txt

2012-08-24T17:06:22Z

Pezra:

Abstract vocabulary description (distilled from annotated HTML)

File:Terms.ttl--5.txt

2012-08-24T17:06:06Z

Pezra:

Turtle (distilled from annotated HTML)

File:Terms.rdf--5.xml

2012-08-24T17:05:50Z

Pezra:

RDF/XML (distilled from annotated HTML)

File:Terms-5.html

2012-08-24T17:05:08Z

Pezra:

HTML (master version)

Technical Team/SPDX RDF Vocabularies and Terms/1.1/Vocabulary

2012-08-21T18:24:13Z

Pezra:

<h2>1.1-DRAFT (21 Aug 2012 18:26 UTC/61361e)<h2>
<p>This page contains the latest draft version of the SPDX RDF vocabulary in various formats.  These are not considered stable at this time.</p><p>This document is under revision control at <a href="http://git.spdx.org/spdx-spec.git">http://git.spdx.org/spdx-spec.git</a>.</p><p>The HTML version is the authorative version.  The other versions are generated from the HTML for your convience.</p>

File:Terms-4.txt

2012-08-21T18:24:04Z

Pezra:

Abstract vocabulary description (distilled from annotated HTML)

File:Terms.ttl--4.txt

2012-08-21T18:23:49Z

Pezra:

Turtle (distilled from annotated HTML)

File:Terms.rdf--4.xml

2012-08-21T18:23:34Z

Pezra:

RDF/XML (distilled from annotated HTML)

File:Terms-4.html

2012-08-21T18:22:29Z

Pezra:

HTML (master version)

Technical Team/SPDX RDF Vocabularies and Terms/1.1/Vocabulary

2012-08-16T22:16:41Z

Pezra:

<h2>1.1-DRAFT (16 Aug 2012 22:01 UTC/8cc379)<h2>
<p>This page contains the latest draft version of the SPDX RDF vocabulary in various formats.  These are not considered stable at this time.</p><p>This document is under revision control at <a href="http://git.spdx.org/spdx-spec.git">http://git.spdx.org/spdx-spec.git</a>.</p><p>The HTML version is the authorative version.  The other versions are generated from the HTML for your convience.</p>

File:Terms-3.txt

2012-08-16T22:16:34Z

Pezra:

Abstract vocabulary description (distilled from annotated HTML)

File:Terms.ttl--3.txt

2012-08-16T22:16:15Z

Pezra:

Turtle (distilled from annotated HTML)

File:Terms.rdf--3.xml

2012-08-16T22:16:00Z

Pezra:

RDF/XML (distilled from annotated HTML)

File:Terms-3.html

2012-08-16T22:15:44Z

Pezra:

HTML (master version)

Technical Team/Use Cases/2.0

2012-08-07T19:43:08Z

Pezra:

<p>We have several sources to begin pulling for SPDX Use Cases:</p><ol><li>The Pad from earlier conversations collected at <a href="http://spdx.org/wiki/use-cases-collected-20-discussion">Use Cases For SPDX 2.0 Discussion</a></li><li>The old <a href="http://spdx.org/wiki/spdx-use-case-1">SPDX 1.0 Use Cases</a> as well as the <a href="http://spdx.org/system/files/ecosystem.jpg">SDPX 1.0 Use Case Picture</a>.</li></ol><div> </div><div>I'd like to propose that we flesh out use cases here by having a brief summary listed here as a link to a more detailed child page.   Note, these use cases should be *<strong>doable</strong>* but in general not *<strong>required</strong>*.  Any item listed here that is not a link, should have a child page created for it.</div><div> </div><div><ol><li>Code commits (original work intended for the project)</li><ol><li><a href="http://spdx.org/wiki/committers-provides-spdx-data-code-being-committed">Committer provides SPDX data</a> [OK]</li><li><a href="http://spdx.org/wiki/contributor-makes-commit-subject-existing-spdx-data-project">Contributor makes commit  subject to existing SPDX data of project</a> [OK]</li></ol><li><a href="http://spdx.org/wiki/committer-annotates-source-files-spdx-data">Committer annotates source files with SPDX data</a> [OK]</li><li>Patches (original work intended for the project)</li><ol><li><a href="http://spdx.org/wiki/patch-provider-provides-spdx-data-patch">Patch provider provides SPDX data for the patch</a> [OK]</li><li><a href="http://spdx.org/wiki/patch-provider-provides-spdx-data-patch-indicating-it-licensed-however-hell-its-applied">Patch provider provides SPDX data for the patch indicating it is licensed however the hell its applied</a> [OK]</li><li><a href="http://spdx.org/wiki/patch-provider-provides-patch-subject-existing-spdx-data-project">Patch provider provides patch subject to existing SPDX data of project</a> [OK]</li></ol><li>Patch provider provides a patch that modifies existing SPDX data of project</li><ol><li><a href="http://spdx.org/wiki/downstream-consumers-contributing-patches-provide-spdx-data-upstream-doesnt-have-it">Downstream consumers contributing patches to provide SPDX data to an upstream that doesn't have it.</a>[OK]</li><li><a href="http://spdx.org/wiki/downstream-consumers-contributing-patches-provide-corrections-spdx-data-upstream-does-have-it">Downstream consumers contributing patches to provide corrections to SPDX data for an upstream that does have it.</a> [OK]</li></ol><li><a href="http://spdx.org/wiki/spdx-20-usecase-upstream-maintainer-providing-spdx-data">Upstream maintainer providing SPDX data</a></li><ol><li><a href="http://spdx.org/wiki/upstream-maintainer-providing-spdx-data-source-archive">Upstream maintainer providing SPDX data in source archive</a>[OK]</li><li><a href="http://spdx.org/wiki/upstream-maintainer-providing-spdx-data-scm">Upstream maintainer providing SPDX data in SCM</a> [OK]</li><li><a href="http://spdx.org/wiki/upstream-maintainer-providing-spdx-data-url">Upstream maintainer providing SPDX data at a URL</a> [OK]</li><li><a href="http://spdx.org/wiki/upstream-maintainer-preparing-release-artifacts-including-spdx-data">Upstream maintainer preparing release artifacts (including SPDX data).</a> [OK]</li></ol><li>Project maintainer incorporates another project</li><ol><li><a href="http://spdx.org/wiki/project-maintainer-incorporates-another-project-including-source">Project maintainer incorporates another project by including source</a> [OK]</li><li><a href="http://spdx.org/wiki/project-maintainer-incorporates-another-project-including-binary">Project maintainer incorporates another project by including binary</a> [OK]</li><li><a href="http://spdx.org/wiki/project-maintainer-pulling-individual-files-out-another-project-subsetting">Project maintainer pulling individual files out of another project (subsetting)</a> [OK]</li></ol><li>Ease adoption</li><ol><li><a href="http://spdx.org/wiki/low-cost-spdx-file">Allow a low investment SPDX producer to produce valid SPDX data</a> [OK-fathomed but not Approved for Implementation]</li><li><a href="http://spdx.org/wiki/producing-valid-spdx-files-face-missing-data">Produce a valid SPDX dataset even if some data is missing</a> [OK]</li></ol><li>Intermediate packager (rpm, deb, etc) passing on and adding to SPDX Data</li><ol><li>Intermediate packager builds source package from upstream source</li><ol><li><a href="http://spdx.org/wiki/intermediate-packager-builds-source-package-upstream-source-provides-spdx-data">Intermediate packager builds source package from upstream source that provides SPDX data</a> [OK]</li><li><a href="http://spdx.org/wiki/intermediate-packager-builds-source-package-upstream-source-does-not-provide-spdx-data">Intermediate packager builds source package from upstream source that does not provide SPDX data</a> [OK]</li></ol><li>Intermediate packager builds binary package from upstream source</li><ol><li><a href="http://spdx.org/wiki/intermediate-packager-builds-binary-package-upstream-source-provides-spdx-data">Intermediate packager builds binary package from upstream source that provides SPDX data</a> [OK]</li><li><a href="http://spdx.org/wiki/intermediate-packager-builds-binary-package-upstream-source-does-not-provides-spdx-data">Intermediate packager builds binary package from upstream source that does not provides SPDX data [OK]</a></li></ol><li>Intermediate packager adds patches to upstream source </li><ol><li><a href="http://spdx.org/wiki/intermediate-packager-adds-patches-upstream-source-provides-spdx-data">Intermediate packager adds patches to upstream source that provides SPDX data</a> [OK]</li><li><a href="http://spdx.org/wiki/intermediate-packager-adds-patches-upstream-source-does-not-provide-spdx-data">Intermediate packager adds patches to upstream source that does not provide SPDX data [OK]</a></li></ol><li>Intermediate packager adds someone else's patches to upstream source</li><ol><li><a href="http://spdx.org/wiki/intermediate-packager-adds-someone-elses-patches-upstream-source-provides-spdx-data">Intermediate packager adds someone else's patches to upstream source that provides SPDX data</a> [OK]</li><li><a href="http://spdx.org/wiki/intermediate-packager-adds-someone-elses-patches-upstream-source-does-not-provide-spdx-data">Intermediate packager adds someone else's patches to upstream source that does not provide SPDX data</a> [OK]</li></ol><li>Intermediate packager subsetting upstream source</li><ol><li><a href="http://spdx.org/wiki/intermediate-packager-subsetting-upstream-source-provides-spdx-data">Intermediate packager subsetting upstream source that provides SPDX data</a> [OK]</li><li><a href="http://spdx.org/wiki/intermediate-packager-subsetting-upstream-source-does-not-provide-spdx-data">Intermediate packager subsetting upstream source that does not provide SPDX data [OK]</a></li></ol></ol><li>Build systems (build systems want to pass on SPDX data for the thing they are building)</li><ol><li><a href="http://www.spdx.org/wiki/spdx-use-case-build-systems-yocto">Yocto</a></li><li>Linking</li><ol><li><a href="http://spdx.org/wiki/debian-has-interest-only-building-things-are-linking-license-compatible">Debian has an interest in only building things that are linking license compatible</a></li></ol><li>I just made a binary out of some source</li><ol><li><a href="http://spdx.org/wiki/spdx-data-indicating-subset-source-made-it-particular-binary-or-binary-package">SPDX data indicating subset of the source that made it into a particular binary or binary package</a></li></ol></ol><li>Aggregator aggregating many 'copyrightable items' for redistribution</li><ol><li><a title="Linux Distro" href="https://spdx.org/wiki/linux-distro">Linux Distros</a></li><li><a href="http://spdx.org/wiki/embedded-images-eg-router-images-switch-images">Embedded Images (e.g. router images, switch images)</a></li><li><a href="http://spdx.org/wiki/spdx-20-usecase-reference-implementations">Reference implementations </a>[Jack Manbeck]</li><li><a href="http://spdx.org/wiki/spdx-20-usecase-application-which-ships-documentation-media-software">Application which ships with documentation +  media + software</a> [Jack Manbeck]</li><li><a title="Use case details" href="http://spdx.org/wiki/application-which-ships-contrib-libraries">Application which ships with a contrib libraries</a></li><li><a title="Use case details" href="http://spdx.org/wiki/application-which-ships-development-tools">Application which ships with development tools</a></li><li><a href="http://spdx.org/wiki/subsetting-out-only-shippable-bits-stuff-coming-sdk">Subsetting out only the shippable bits of stuff coming from an SDK</a></li><li><a href="http://spdx.org/wiki/aggregators-aggregating-other-aggregations-redistribution">Aggregators aggregating other aggregations for redistribution</a></li></ol><li>Consumers receiving SPDX data</li><ol><li><a href="http://spdx.org/wiki/provide-sufficient-data-allow-consumer-comply-licenses-redistribution">Provide sufficient data to allow consumer to comply with licenses on redistribution</a></li></ol><li><a href="http://spdx.org/wiki/consuming-code-snippets">Consuming code snippets </a>(God help us all) (subfile pieces of code not originally intended for the project)</li><li>Signoff/multiple signoff on SPDX data</li><ol><li><a target="_blank" title="Contracts with multiple parties requiring signoff by all" href="https://spdx.org/wiki/multi-party-contracts">Contracts with multiple parties requiring signoff by al</a>l [Kate Stewart]</li></ol><li>Third party does licensing analysis</li><ol><li><a href="http://spdx.org/wiki/third-party-produces-bill-materials-software-package">Third party generates license analysis</a></li><li><a href="http://spdx.org/wiki/collecting-enough-information-allow-auditor-make-recommendations-remove-or-not-component">Collecting enough information to allow auditor to make recommendations to remove or not a component</a></li></ol><li>Auditor Analyzing/Sanity-checking/correcting Bill of Material he's handed</li><ol><li><a href="http://spdx.org/wiki/use-case-backtrack-binary-source-files">Backtrack from compiled/binary file to constituent files</a> </li><li>outbound: validate that SPDX goes hand in hand with what's being shipped [Kirsten Newcomer]</li><ol><li><a href="http://spdx.org/wiki/check-see-if-spdx-data-provided-matches-files-provided">Check to see if the SPDX data provided matches the files provided</a></li></ol></ol><li>Extensions:</li><ol><li><a href="http://spdx.org/wiki/communicate-data-beyond-what-described-spec">Communicate data beyond what is described in spec between consenting parties w/o breaking consumers that are not in the know</a></li><li><a href="http://spdx.org/wiki/license-list-extension">License list extensions, how do you handle folks who have more licenses than SPDX</a></li><li><a href="http://spdx.org/wiki/decorating-already-produces-and-signed-spdx-dataset-extension-data">Decorating an already produces and signed SPDX dataset with extension data</a> [Bill Schineller]</li></ol><li>Other arising during vetting...</li><ol><li>Given 2 SPDX files about the same codebase from the same source, be able to tell which is the later rev / more current and correct one.</li></ol></ol><div> Cross-cutting concerns:</div><div><div><ol><li>Provenance (the need to optionally use signing to validate who said what)</li><li>Trust</li><li>Handling staleness of data</li><li>Composite licensing</li><li>Ease of sharing information</li><ol><li>Collecting tribal knowledge along the way </li></ol><li>Guarding against file bloat</li><li>Simple simple simple</li><li>SPDX-Lite:</li><li>Clarity</li><li>Automation/toolifiability</li><li>Regionality</li></ol></div></div></div><div><h2>Themes:</h2></div><div> </div><div>Looking at these Use Cases, there are some underlying themes:</div><div><ol><li>Root of data (closer to upstream the better)</li><li>Subsetting of copyrightable things (and their SPDX data) (<strong>Note</strong>: Subsets of copyrightable things are usually also copyrightable things)</li><li>Aggregation of copyrightable things (and their SPDX data) (<strong>Note</strong>: Aggregations of copyrightable things are usually also copyrightable things).</li></ol></div><div> </div><div> </div><p> </p>

Technical Team/SPDX RDF Vocabularies and Terms/1.1/Vocabulary

2012-07-17T19:03:01Z

Pezra:

<h2>1.1-DRAFT (17 Jul 2012 18:47 UTC/7a3204)<h2>
<p>This page contains the latest draft version of the SPDX RDF vocabulary in various formats.  These are not considered stable at this time.</p><p>This document is under revision control at <a href="http://git.spdx.org/spdx-spec.git">http://git.spdx.org/spdx-spec.git</a>.</p><p>The HTML version is the authorative version.  The other versions are generated from the HTML for your convience.</p>

Technical Team/SPDX RDF Vocabularies and Terms/1.1/Vocabulary

2012-07-17T19:02:22Z

Pezra:

<h2>1.1-DRAFT (18 Jun 2012 21:44 UTC/40656d)<h2>
<p>This page contains the latest draft version of the SPDX RDF vocabulary in various formats.  These are not considered stable at this time.</p><p>This document is under revision control at <a href="http://git.spdx.org/spdx-spec.git">http://git.spdx.org/spdx-spec.git</a>.</p><p>The HTML version is the authorative version.  The other versions are generated from the HTML for your convience.</p>

File:Terms-2.txt

2012-07-17T19:02:16Z

Pezra:

Abstract vocabulary description (distilled from annotated HTML)

File:Terms.ttl--2.txt

2012-07-17T19:02:03Z

Pezra:

Turtle (distilled from annotated HTML)

File:Terms.rdf--2.xml

2012-07-17T19:01:49Z

Pezra:

RDF/XML (distilled from annotated HTML)

Technical Team/SPDX RDF Vocabularies and Terms/1.1/Vocabulary

2012-07-17T19:00:58Z

Pezra:

File:Terms-2.html

2012-07-17T19:00:49Z

Pezra:

HTML (master version)

Technical Team/SPDX RDF Vocabularies and Terms/1.1/Vocabulary

2012-06-19T18:05:58Z

Pezra:

Technical Team/SPDX RDF Vocabularies and Terms/1.1/Vocabulary

2012-06-19T18:05:47Z

Pezra:

File:Terms-1.html

2012-06-19T18:05:27Z

Pezra:

HTML (master version)

Technical Team/SPDX RDF Vocabularies and Terms/1.1/Vocabulary

2012-06-19T18:00:51Z

Pezra:

Technical Team/SPDX RDF Vocabularies and Terms/1.1/Vocabulary

2012-06-18T21:46:25Z

Pezra:

File:Terms-1.txt

2012-06-18T21:46:18Z

Pezra:

Abstract vocabulary description (distilled from annotated HTML)

File:Terms.ttl--1.txt

2012-06-18T21:45:54Z

Pezra:

Turtle (distilled from annotated HTML)

File:Terms.rdf--1.xml

2012-06-18T21:45:27Z

Pezra:

RDF/XML (distilled from annotated HTML)

Technical Team/Proposals

2012-06-18T21:04:22Z

Pezra:

<div><strong>Proposals for v1.1</strong></div><ul><li><a href="http://spdx.org/wiki/2012-jun-18-standardnotice-field-license-class">2012-Jun-18: standardNotice field for License Class</a></li><li><a href="http://spdx.org/wiki/2012-jun-18-2-isosiapproved-field-listed-licenses">2012-Jun-18-2: isOsiApproved field for listed licenses</a></li></ul><div><strong>Proposals for vNEXT</strong></div><ul><li><a href="http://www.spdx.org/wiki/proposal-2010-10-21-1-license-urls">2010-10-21-1: License URLs</a></li><li><a href="http://www.spdx.org/wiki/proposal-2011-12-20-spdx-analysis-history-tracking">2011-12-20: SPDX Analysis History Tracking</a></li><li><a href="http://spdx.org/wiki/2012-mar-11-spdx-file-aggregation">2012-Mar-11: SPDX File Aggregation</a></li></ul><h2>Adopted proposals</h2><ul><li><a href="http://www.spdx.org/wiki/proposal-2010-10-21-3-artifactof">2010-10-21-3: artifactOf</a></li><li><a href="http://www.spdx.org/wiki/proposal-2010-10-21-4-composite-licensing">2010-10-21-4: Composite licensing</a></li><li><a href="http://spdx.org/wiki/proposal-2012-mar-06-detached-signed-spdx-files">2012-Mar-6: Detached signed SPDX files</a></li></ul><h2>Rejected proposals</h2><ul><li><a href="http://www.spdx.org/wiki/proposal-2010-10-21-2-file-origin">2010-10-21-2: File origin</a></li><li><a href="http://www.spdx.org/wiki/proposal-2010-12-07-1-tag-value-rdf-mapping">2010-12-07-1: Tag-value RDF mapping</a></li><li><a href="http://spdx.org/wiki/proposal-2012-01-17-signed-spdx-data">2012-01-17: Signed SPDX Data</a></li><li><a href="http://spdx.org/wiki/proposal-2012-mar-05-inline-signed-spdx-files">2012-Mar-5:<em> </em>Inlined signed SPDX files</a></li></ul><h2>Drafts</h2><ul><li><a href="http://www.spdx.org/wiki/proposal-2010-10-28-1-file-references">2010-10-28-1: File references</a></li><li><a href="http://www.spdx.org/wiki/proposal-2010-11-16-1-or-later-version-licensing">2010-11-16-1: Or later version licensing</a></li></ul>

Technical Team/Proposals/2012-06-18/standardNotice field for License class

2012-06-18T20:57:52Z

Pezra:

<p><strong>Status:</strong>open</p><p><strong>Issue</strong></p><p><strong></strong>See <a href="https://bugs.linuxfoundation.org/show_bug.cgi?id=1049">bug #1049</a></p><p>Standard licensing notices need to be published in a machine readable way to facilitate the implementation of license text matching guidelines.</p><p><strong>Proposal</strong></p><p><strong><br /></strong>Add a `standardNotice` property to the License class whose value is a string. The cardinality of this property would be "Optional, zero or one"</p><p><strong>Detailed Changes</strong></p><ul><li>No changes are required in the Tag-Value section of the spec</li>
<li>The follow text would be added the the RDF terms document in the properties section of the the <a href="http://spdx.org/rdf/terms#License">License class details</a>:

<pre style="margin-left: 3ex;">
* standardNotice

Cardinality: Optional, zero or one
</pre>
</li>
<li><p>The following text would be added to the RDF terms document immediately before the <a href="http://spdx.org/rdf/terms#supplier">supplier section</a> and an appropriate entry would be added to the properties index:</p>
<pre style="margin-left: 3ex;">
Property: standardNotice

The block of text specified in the license as the preferred
way to declare that a work is covered by the terms of this
license.

Status: stable

Domain: License

Range: xsd:string

</pre></li>

<li><p>The license list web site generator would be updated to add a "Standard Notice" section after the "Text" section in the details pages of license for which one is known and would annotate the notice text with RDFa to make that information machine readable.</p></li></ul>

Technical Team/Proposals

2012-06-18T20:57:24Z

Pezra:

<ul><li><a href="http://spdx.org/wiki/2012-jun-18-standardnotice-field-license-class">2012-Jun-18: standardNotice field for License Class</a></li><li><a href="http://spdx.org/wiki/2012-jun-18-2-isosiapproved-field-listed-licenses">2012-Jun-18-2: isOsiApproved field for listed licenses</a></li><li><a href="http://www.spdx.org/wiki/proposal-2010-10-21-1-license-urls">2010-10-21-1: License URLs</a></li><li><a href="http://www.spdx.org/wiki/proposal-2011-12-20-spdx-analysis-history-tracking">2011-12-20: SPDX Analysis History Tracking</a></li><li><a href="http://spdx.org/wiki/2012-mar-11-spdx-file-aggregation">2012-Mar-11: SPDX File Aggregation</a></li></ul><h2>Adopted proposals</h2><ul><li><a href="http://www.spdx.org/wiki/proposal-2010-10-21-3-artifactof">2010-10-21-3: artifactOf</a></li><li><a href="http://www.spdx.org/wiki/proposal-2010-10-21-4-composite-licensing">2010-10-21-4: Composite licensing</a></li><li><a href="http://spdx.org/wiki/proposal-2012-mar-06-detached-signed-spdx-files">2012-Mar-6: Detached signed SPDX files</a></li></ul><h2>Rejected proposals</h2><ul><li><a href="http://www.spdx.org/wiki/proposal-2010-10-21-2-file-origin">2010-10-21-2: File origin</a></li><li><a href="http://www.spdx.org/wiki/proposal-2010-12-07-1-tag-value-rdf-mapping">2010-12-07-1: Tag-value RDF mapping</a></li><li><a href="http://spdx.org/wiki/proposal-2012-01-17-signed-spdx-data">2012-01-17: Signed SPDX Data</a></li><li><a href="http://spdx.org/wiki/proposal-2012-mar-05-inline-signed-spdx-files">2012-Mar-5:<em> </em>Inlined signed SPDX files</a></li></ul><h2>Drafts</h2><ul><li><a href="http://www.spdx.org/wiki/proposal-2010-10-28-1-file-references">2010-10-28-1: File references</a></li><li><a href="http://www.spdx.org/wiki/proposal-2010-11-16-1-or-later-version-licensing">2010-11-16-1: Or later version licensing</a></li></ul>

Technical Team/Proposals/2012-06-18/isOsiApproved field for listed licenses

2012-06-18T20:55:11Z

Pezra:

<p><strong>Status:</strong> open</p>

<h2><strong>Issue</strong></h2>

<p>See also: <a href="https://bugs.linuxfoundation.org/show_bug.cgi?id=1050">bug #1050</a></p>

<p>The legal working group track whether each license has been approved by the OSI. That information should be published as part of the official license list.</p>

<h2><strong>Proprosal</strong></h2>

<p>Add a boolean <code>isOsiApproved</code> property to the <code>License</code> class to indicated whether the OSI has approved the license. Update the license list web site to display this information and annotate it with RDFa so that the information is machine readable.</p>

<h2><strong>Detailed Changes</strong></h2>

<ul>
<li><p>Add the following text to the <a href="http://spdx.org/rdf/terms#License">License class definition section</a> of the RDF terms documentation:</p>
<pre style="margin-left: 3ex;">
* isOsiApproved
Cardinality: Mandatory, one
</pre>
</li>

<li><p>Add the following text to the properties section of the RDF terms documentation immediately preceding the <code>licenseComments</code> section:</p>

<pre style="margin-left: 3ex;">
Property: isOsiApproved

Indicates if the Open Source Initiative has approved the
license as being an open source license. A link to the OSI
license page for this license should be provided use the
seeAlso property when this property is affirmative.

Status:
stable
Domain:
License
Range:
xsd:boolean
</pre>
</li>

<li><p>Updated license list web site generator to display "Is OSI approved" after the "Other web pages for this license" info in the header block of license details pages.</p>
</li>

</ul>

Technical Team/Proposals/2012-06-18/isOsiApproved field for listed licenses

2012-06-18T20:54:17Z

Pezra:

<p><strong>Status:</strong> open</p>

<h2><strong>Issue</strong></h2>

<p>See also: <a href="https://bugs.linuxfoundation.org/show_bug.cgi?id=1050">bug #1050</a></p>

<p>The legal working group track whether each license has been approved by the OSI. That information should be published as part of the official license list.</p>

<h2><strong>Proprosal</strong></h2>

<p>Add a boolean <code>isOsiApproved</code> property to the <code>License</code> class to indicated whether the OSI has approved the license. Update the license list web site to display this information and annotate it with RDFa so that the information is machine readable.</p>

<h2><strong>Detailed Changes</strong></h2>

<ul>
<li><p>Add the following text to the <a href="http://spdx.org/rdf/terms#License">License class definition section</a> of the RDF terms documentation:</p>
<pre style="margin-left: 3ex;">
* isOsiApproved
Cardinality: Mandatory, one
</pre>
</li>

<li><p>Add the following text to the properties section of the RDF terms documentation immediately preceding the <code>licenseComments</code> section:</p>

<pre style="margin-left: 3ex;">
Property: isOsiApproved

Indicates if the Open Source Initiative has approved the
license as being an open source license. A link to the OSI
license page for this license should be provided use the
seeAlso property when this property is affirmative.

Status:
testing
Domain:
License
Range:
xsd:boolean
</pre>
</li>

<li><p>Updated license list web site generator to display "Is OSI approved" after the "Other web pages for this license" info in the header block of license details pages.</p>
</li>

</ul>

Technical Team/Proposals/2012-06-18/isOsiApproved field for listed licenses

2012-06-18T20:53:47Z

Pezra:

<p><strong>Status:</strong> open</p>

<h2><strong>Issue</strong></h2>

<p>See also: <a href="https://bugs.linuxfoundation.org/show_bug.cgi?id=1050">bug #1050</a></p>

<p>The legal working group track whether each license has been approved by the OSI. That information should be published as part of the official license list.</p>

<h2>Proprosal</h2>

<p>Add a boolean <code>isOsiApproved</code> property to the <code>License</code> class to indicated whether the OSI has approved the license. Update the license list web site to display this information and annotate it with RDFa so that the information is machine readable.</p>

<h2>Detailed Changes</h2>

<ul>
<li><p>Add the following text to the <a href="http://spdx.org/rdf/terms#License">License class definition section</a> of the RDF terms documentation:</p>
<pre style="margin-left: 3ex;">
* isOsiApproved
Cardinality: Mandatory, one
</pre>
</li>

<li><p>Add the following text to the properties section of the RDF terms documentation immediately preceding the <code>licenseComments</code> section:</p>

<pre style="margin-left: 3ex;">
Property: isOsiApproved

Indicates if the Open Source Initiative has approved the
license as being an open source license. A link to the OSI
license page for this license should be provided use the
seeAlso property when this property is affirmative.

Status:
testing
Domain:
License
Range:
xsd:boolean
</pre>
</li>

<li><p>Updated license list web site generator to display "Is OSI approved" after the "Other web pages for this license" info in the header block of license details pages.</p>
</li>

</ul>

Technical Team/Proposals/2012-06-18/isOsiApproved field for listed licenses

2012-06-18T20:53:31Z

Pezra:

<p><strong>Status:</strong> open</p>

<h2>Issue</h2>

<p>See also: <a href="https://bugs.linuxfoundation.org/show_bug.cgi?id=1050">bug #1050</a></p>

<p>The legal working group track whether each license has been approved by the OSI. That information should be published as part of the official license list.</p>

<h2>Proprosal</h2>

<p>Add a boolean <code>isOsiApproved</code> property to the <code>License</code> class to indicated whether the OSI has approved the license. Update the license list web site to display this information and annotate it with RDFa so that the information is machine readable.</p>

<h2>Detailed Changes</h2>

<ul>
<li><p>Add the following text to the <a href="http://spdx.org/rdf/terms#License">License class definition section</a> of the RDF terms documentation:</p>
<pre style="margin-left: 3ex;">
* isOsiApproved
Cardinality: Mandatory, one
</pre>
</li>

<li><p>Add the following text to the properties section of the RDF terms documentation immediately preceding the <code>licenseComments</code> section:</p>

<pre style="margin-left: 3ex;">
Property: isOsiApproved

Indicates if the Open Source Initiative has approved the
license as being an open source license. A link to the OSI
license page for this license should be provided use the
seeAlso property when this property is affirmative.

Status:
testing
Domain:
License
Range:
xsd:boolean
</pre>
</li>

<li><p>Updated license list web site generator to display "Is OSI approved" after the "Other web pages for this license" info in the header block of license details pages.</p>
</li>

</ul>

Technical Team/Proposals/2012-06-18/isOsiApproved field for listed licenses

2012-06-18T20:50:04Z

Pezra:

<p><strong>Status:</strong> draft</p>

<h2>Issue</h2>

<p>See also: bug #...</p>

<p>The legal working group track whether each license has been approved by the OSI. That information should be published as part of the official license list.</p>

<h2>Proprosal</h2>

<p>Add a boolean <code>isOsiApproved</code> property to the <code>License</code> class to indicated whether the OSI has approved the license. Update the license list web site to display this information and annotate it with RDFa so that the information is machine readable.</p>

<h2>Detailed Changes</h2>

<ul>
<li><p>Add the following text to the <a href="http://spdx.org/rdf/terms#License">License class definition section</a> of the RDF terms documentation:</p>
<pre style="margin-left: 3ex;">
* isOsiApproved
Cardinality: Mandatory, one
</pre>
</li>

<li><p>Add the following text to the properties section of the RDF terms documentation immediately preceding the <code>licenseComments</code> section:</p>

<pre style="margin-left: 3ex;">
Property: isOsiApproved

Indicates if the Open Source Initiative has approved the
license as being an open source license. A link to the OSI
license page for this license should be provided use the
seeAlso property when this property is affirmative.

Status:
testing
Domain:
License
Range:
xsd:boolean
</pre>
</li>

<li><p>Updated license list web site generator to display "Is OSI approved" after the "Other web pages for this license" info in the header block of license details pages.</p>
</li>

</ul>

Technical Team/Proposals/2012-06-18/isOsiApproved field for listed licenses

2012-06-18T20:48:57Z

Pezra:

<p><strong>Status:</strong> draft</p>

<h2>Issue</h2>

<p>See also: bug #...</p>

<p>The legal working group track whether each license has been approved by the OSI. That information should be published as part of the official license list.</p>

<h2>Proprosal</h2>

<p>Add a boolean <code>isOsiApproved</code> property to the <code>License</code> class to indicated whether the OSI has approved the license. Update the license list web site to display this information and annotate it with RDFa so that the information is machine readable.</p>

<h2>Detailed Changes</h2>

<ul>
<li><p>Add the following text to the <a href="http://spdx.org/rdf/terms#License">License class definition section</a> of the RDF terms documentation:</p>
<pre style="margin-left: 3ex;">
* isOsiApproved
Cardinality: Mandatory, one
</pre>
</li>

<li><p>Add the following text to the properties section of the RDF terms documentation immediately preceding the <code>licenseComments</code> section:</p>

<pre style="margin-left: 3ex;">
Property: isOsiApproved

Indicates if the Open Source Initiative has approved the
license as being an open source license. A link to the OSI
license page for this license should be provided in a
seeAlso property when this property is affirmative.

Status:
testing
Domain:
License
Range:
xsd:boolean
</pre>
</li>

<li><p>Updated license list web site generator to display "Is OSI approved" after the "Other web pages for this license" info in the header block of license details pages.</p>
</li>

</ul>