Re: Purpose of license templatization
Peter Williams <peter.williams@...>
On Thu, Mar 3, 2011 at 5:31 AM, Tom Incorvia
I like the goal but i don't see how standardizing a license
normalization algorithm designed to remove non-material variations
advances this goal.
In prior discussions regarding template licenses like BSD, there has alwaysI think everyone agrees we need to handle this case.
The expectation is that by standardizing the licenses that will move peopleHaving a registry of licenses with standardized text (particularly
good, well formatted, cut-and-pastable text) may increase the use of
those licenses. However, i don't think we can assume that license
variations will ever be reduced to point that users will be able to do
without sophisticated matching. Even it that does happen someday, it
is not the world we live in today.
The net is that the reasonable alternative to tool sophistication is theMaybe. Personally, i doubt we will ever see the day when there are
few license variation than there are now.
My thought is that we start with a basic approach (exact match minus whiteIf we did this, what would a non-match due to a non-material variation
mean? (Say some "a"s where switched to "an"s.)
Could i, as a human, look at it and decide that it is clearly one of
the standard licenses and so produce an spdx file in when the licenses
in file and concluded licenses both reference the standard license?
Or would i be forced to use a non-standard license (even though is is
clearly one of the standard licenses)?