Legal Team/Old/License Template Issues - Revision history

MartinMichlmayr: Convert to MediaWiki syntax

2013-03-07T14:33:38Z

Convert to MediaWiki syntax

Pezra at 20:21, 2 March 2011

2011-03-02T20:21:08Z

Pezra at 20:18, 2 March 2011

2011-03-02T20:18:20Z

Pezra at 17:24, 2 March 2011

2011-03-02T17:24:49Z

Pezra at 17:18, 2 March 2011

2011-03-02T17:18:47Z

Pezra at 17:18, 2 March 2011

2011-03-02T17:18:25Z

Pezra at 17:18, 2 March 2011

2011-03-02T17:18:04Z

Pezra at 17:16, 2 March 2011

2011-03-02T17:16:32Z

Pezra at 17:15, 2 March 2011

2011-03-02T17:15:19Z

Pezra at 17:14, 2 March 2011

2011-03-02T17:14:25Z

@@ Line 1: / Line 1: @@
-<h1>paragraph rearrangement</h1><p>
+==paragraph rearrangement==
-<strong>resolved</strong></p>
-<p>The consensus was that this is outside the scope of templatization.</p>
+'''resolved'''
-<h1>Whitespace normalization</h1><p>
+The consensus was that this is outside the scope of templatization.
-<strong>resolved</strong></p>
-<p>How to deal with whitespace repeation and newlines vs space vs tab</p>
-<ol>
+==Whitespace normalization==
-<li>replace all whitespace characters with SPACE</li>
-<li>collapse repeated spaces to one space character</li>
-</ol>
-<h1>Copyright notices</h1>
+'''resolved'''
-<p>The text some of licenses in our list contain a copyright statement.  Is this actually part of the license text?  In some cases (eg. gpl) it definitely is.  In others (eg. bsd) it does not feel like part of the license.  Would it be ok to remove the copyright statement from licenses where that statement does not apply to the text of the license itself.</p>
+How to deal with whitespace repeation and newlines vs space vs tab
-<h1>Replaceable parts</h1>
+# replace all whitespace characters with SPACE
-<p>Dealing with copyright owner, copyright year, etc.</p>
+# collapse repeated spaces to one space character
-<p>Some sort of demarcation of replaceable elements in a license.  These would be limited to a discrete list of supported element types.  For example, year and copyright holder.</p>
+==Copyright notices==
-<p>We could allow replaceable elements to be used in any license text at the risk of colliding with non-template parts of the license text. Alternatively, we could explicitly indicate that the license text of a particular licenses has replaceable elements.  An explicit indication of templatization would allow us to simply not use replaceable elements for licenses which would have collisions.  However, it would prevent us from templatizing licenses that would have collisions</p>
+The text some of licenses in our list contain a copyright statement. Is this actually part of the license text? In some cases (eg. gpl) it definitely is. In others (eg. bsd) it does not feel like part of the license. Would it be ok to remove the copyright statement from licenses where that statement does not apply to the text of the license itself.
-<p>Perhaps an esoteric template syntax would allow us to avoid the collision issue.  Maybe something like "{{{YEAR}}}"?</p>
+==Replaceable parts==
-<h1>Section/bullet numbering/lettering</h1>
+Dealing with copyright owner, copyright year, etc.
-<p>If a sdpx registered license has a list labeled a,b,a does it match license text that is identical except that the list is labeled i,ii,iii?</p>
-<p>this issue has not been explored</p>
+Some sort of demarcation of replaceable elements in a license. These would be limited to a discrete list of supported element types. For example, year and copyright holder.
-<h1>Different spellings of same word</h1>
+We could allow replaceable elements to be used in any license text at the risk of colliding with non-template parts of the license text. Alternatively, we could explicitly indicate that the license text of a particular licenses has replaceable elements. An explicit indication of templatization would allow us to simply not use replaceable elements for licenses which would have collisions. However, it would prevent us from templatizing licenses that would have collisions
-<p>color vs colour</p>
-<p>Issue not dealt with.  Perhaps a stemming algorithm of some sort?</p>
+<nowiki>Perhaps an esoteric template syntax would allow us to avoid the collision issue. Maybe something like "{{{YEAR}}}"?</nowiki>
-<h1>Separate field</h1>
+==Section/bullet numbering/lettering==
-<p>Is a separate field for the normalized/templated version of the license text necessary and desirable?</p>
+If a sdpx registered license has a list labeled a,b,a does it match license text that is identical except that the list is labeled i,ii,iii?
-<p>Normalization algorithm must be defined normatively in the spec.</p>
+this issue has not been explored
-<p>Explicit field for normalized/templated version could be helpful as examples.  Perhaps example of every standard license is unnecessary.</p>
+==Different spellings of same word==

@@ Line 27: / Line 27: @@
 <h1>Section/bullet numbering/lettering</h1>
-<p>What if in one license a list has a,b,c and in another i,ii,iii?</p>
+<p>If a sdpx registered license has a list labeled a,b,a does it match license text that is identical except that the list is labeled i,ii,iii?</p>
 <p>this issue has not been explored</p>

@@ Line 12: / Line 12: @@
 <li>collapse repeated spaces to one space character</li>
 </ol>
 <h1>Replaceable parts</h1>

← Older revision		Revision as of 17:24, 2 March 2011
Line 31:		Line 31:

	<p>Issue not dealt with. Perhaps a stemming algorithm of some sort?</p>		<p>Issue not dealt with. Perhaps a stemming algorithm of some sort?</p>
		+
		+	<h1>Separate field</h1>
		+
		+	<p>Is a separate field for the normalized/templated version of the license text necessary and desirable?</p>
		+
		+	<p>Normalization algorithm must be defined normatively in the spec.</p>
		+
		+	<p>Explicit field for normalized/templated version could be helpful as examples. Perhaps example of every standard license is unnecessary.</p>

@@ Line 10: / Line 10: @@
 <ol>
 <li>replace all whitespace characters with SPACE</li>
-collapse repeated spaces to one space character
+<li>collapse repeated spaces to one space character</li>
 </ol>

@@ Line 1: / Line 1: @@
-<h2>Issues:</h2>
+<h2><del>paragraph rearrangement</del><h2>
-<ul>
+<p>The consensus was that this is outside the scope of templatization.</p>x
-<li>whitespace: repeation, newlines vs space vs tab</li>
-<li>replaceable parts: copyright owner, copyright year, etc</li>
-<li><del>paragraph rearrangement</del> (consensus was that this is outside the scope of templatization)</li>
-<li>section/bullet numbering/lettering: what if in one license a list has a,b,c and in another i,ii,iii</li>
-<li>different spellings of same word: color vs colour</li>
-</ul>
 <h2>Whitespace normalization</h2>
@@ Line 15: / Line 9: @@
 <ol>
 <li>replace all whitespace characters with SPACE</li>
-<il>collapse repeated spaces to one space character</li>
+collapse repeated spaces to one space character
 </ol>

← Older revision		Revision as of 17:14, 2 March 2011
Line 8:		Line 8:
	<li>different spellings of same word: color vs colour</li>		<li>different spellings of same word: color vs colour</li>
	</ul>		</ul>
		+
		+	<h2>Whitespace normalization</h2>
		+
		+	<p>How to deal with whitespace repeation and newlines vs space vs tab</p>
		+
		+	<ol>
		+	<li>replace all whitespace characters with SPACE</li>
		+	<il>collapse repeated spaces to one space character</li>
		+	</ol>
		+
		+	<h2>Replaceable parts</h2>
		+	<p>Dealing with copyright owner, copyright year, etc.</p>
		+
		+	<p>Some sort of demarcation of replaceable elements in a license. These would be limited to a discrete list of supported element types. For example, year and copyright holder.</p>
		+
		+	<p>We could allow replaceable elements to be used in any license text at the risk of colliding with non-template parts of the license text. Alternatively, we could explicitly indicate that the license text of a particular licenses has replaceable elements. An explicit indication of templatization would allow us to simply not use replaceable elements for licenses which would have collisions. However, it would prevent us from templatizing licenses that would have collisions</p>
		+
		+	<p>Perhaps an esoteric template syntax would allow us to avoid the collision issue. Maybe something like "{{{YEAR}}}"?</p>
		+
		+	<h2>section/bullet numbering/lettering</h2>
		+	<p>What if in one license a list has a,b,c and in another i,ii,iii?</p>
		+
		+	<p>this issue has not been explored</p>
		+
		+	<h2>Different spellings of same word</h2>
		+	<p>color vs colour</p>
		+
		+	<p>Issue not dealt with. Perhaps a stemming algorithm of some sort?</p>