THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx
Difference between revisions of "Legal Team/Old/License Template Issues"
| Line 1: | Line 1: | ||
| − | < | + | <h1>paragraph rearrangement</h1> |
<p>The consensus was that this is outside the scope of templatization.</p>x | <p>The consensus was that this is outside the scope of templatization.</p>x | ||
| − | < | + | </h1>Whitespace normalization</h1> |
<p>How to deal with whitespace repeation and newlines vs space vs tab</p> | <p>How to deal with whitespace repeation and newlines vs space vs tab</p> | ||
| Line 12: | Line 12: | ||
</ol> | </ol> | ||
| − | < | + | <h1>Replaceable parts</h1> |
<p>Dealing with copyright owner, copyright year, etc.</p> | <p>Dealing with copyright owner, copyright year, etc.</p> | ||
| Line 21: | Line 21: | ||
<p>Perhaps an esoteric template syntax would allow us to avoid the collision issue. Maybe something like "{{{YEAR}}}"?</p> | <p>Perhaps an esoteric template syntax would allow us to avoid the collision issue. Maybe something like "{{{YEAR}}}"?</p> | ||
| − | < | + | <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>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> | <p>this issue has not been explored</p> | ||
| − | < | + | <h1>Different spellings of same word</h1> |
<p>color vs colour</p> | <p>color vs colour</p> | ||
<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> | ||
Revision as of 17:16, 2 March 2011
Contents
paragraph rearrangement
The consensus was that this is outside the scope of templatization.
x</h1>Whitespace normalization</h1>
How to deal with whitespace repeation and newlines vs space vs tab
- replace all whitespace characters with SPACE
collapse repeated spaces to one space character
Replaceable parts
Dealing with copyright owner, copyright year, etc.
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.
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
Perhaps an esoteric template syntax would allow us to avoid the collision issue. Maybe something like "{{{YEAR}}}"?
section/bullet numbering/lettering
What if in one license a list has a,b,c and in another i,ii,iii?
this issue has not been explored
Different spellings of same word
color vs colour
Issue not dealt with. Perhaps a stemming algorithm of some sort?
