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

MartinMichlmayr: Convert to MediaWiki syntax

2013-03-07T13:54:26Z

Convert to MediaWiki syntax

Pezra at 20:57, 18 June 2012

2012-06-18T20:57:52Z

Pezra at 18:29, 18 June 2012

2012-06-18T18:29:33Z

Pezra at 18:27, 18 June 2012

2012-06-18T18:27:40Z

Pezra at 18:26, 18 June 2012

2012-06-18T18:26:39Z

Pezra at 18:25, 18 June 2012

2012-06-18T18:25:09Z

Pezra at 18:24, 18 June 2012

2012-06-18T18:24:15Z

Pezra at 18:23, 18 June 2012

2012-06-18T18:23:54Z

Pezra at 18:22, 18 June 2012

2012-06-18T18:22:23Z

Pezra at 18:22, 18 June 2012

2012-06-18T18:22:03Z

@@ Line 1: / Line 1: @@
-<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>
+Status: open
-<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;">
+== Issue ==
-* standardNotice
-  Cardinality: Optional, zero or one
+See [https://bugs.linuxfoundation.org/show_bug.cgi?id=1049 bug #1049]
-</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
+Standard licensing notices need to be published in a machine readable way to facilitate the implementation of license text matching guidelines.
-way to declare that a work is covered by the terms of this
 license.
-Status: stable
+== Proposal ==
-Domain: License
+Add a `standardNotice` property to the License class whose value is a string. The cardinality of this property would be "Optional, zero or one"
-Range: xsd:string
+== Detailed Changes ==
-</pre></li>
+* No changes are required in the Tag-Value section of the spec
-<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>
+* 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.

@@ Line 16: / Line 16: @@
 license.
-Status: testing
+Status: stable
 Domain: License

← Older revision		Revision as of 18:29, 18 June 2012
Line 1:		Line 1:
−	<p><strong>Status:</strong>~~ draft~~</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>	+	<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>:		<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>:

← Older revision		Revision as of 18:26, 18 June 2012
Line 24:		Line 24:
	</pre></li>		</pre></li>

−	<li><p>The license ~~license~~ 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 ~~use~~ RDFa to make that information machine readable.</p></li></ul>	+	<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>

@@ Line 1: / Line 1: @@
 <p><strong>Status:</strong>&nbsp;draft</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.html#License">License class details</a>:
+<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;">
@@ Line 8: / Line 8: @@
 </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.html#supplier">supplier section</a> and an appropriate entry would be added to the properties index:</p>
+<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

← Older revision	Revision as of 18:27, 18 June 2012
(No difference)

@@ Line 22: / Line 22: @@
 Range: xsd:string
-</pre</li>
+</pre></li>
 <li><p>The license license 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 use RDFa to make that information machine readable.</p></li></ul>

@@ Line 9: / Line 9: @@
 </li>
 <li><p>The following text would be added to the RDF terms document immediately before the <a href="http://spdx.org/rdf/terms.html#supplier">supplier section</a> and an appropriate entry would be added to the properties index:</p>
-<pre style="margin-left: 3ex; word-wrap: normal;>
+<pre style="margin-left: 3ex; word-wrap: normal;">
 Property: standardNotice