THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx
Difference between revisions of "Legal Team/non-English-licenses"
| Line 11: | Line 11: | ||
# Add the license to the SPDX License List in the "canonical" or original language; or the language version as requested (or what came first) | # Add the license to the SPDX License List in the "canonical" or original language; or the language version as requested (or what came first) | ||
# Assign a short identifier based on 1 | # Assign a short identifier based on 1 | ||
| − | # If the license has "official" translations, then provide links to such translations in the notes field (but do not add translations as different languages) | + | # If the license has "official" translations, then provide links to such translations in the notes field (but do not add translations as different languages) where "official" translations are those by the license author or otherwise blessed by the license author |
| − | + | ||
the above implies the following: | the above implies the following: | ||
* one short identifers can be used for all official translations | * one short identifers can be used for all official translations | ||
* one can consider a match across any official translation | * one can consider a match across any official translation | ||
Revision as of 02:26, 1 June 2017
Working Page for Policy on Non-English Licenses
The issue of how or how to best handle licenses in languages other than English or with multiple language translations has come up repeatedly over the years of the SPDX License List's existence. This is especially critical in relation to how short identifiers are assigned and when a license is considered a match (or a different license). There are a number of non-English licenses or licenses with multiple language translations on the SPDX License List and the treatment thereof has formed a sort of "default policy". However, such treatment is not complete and does not fully address the question of license matching.
Jilayne Lovejoy and Kate Stewart presented the background of the issue and current "default policy" along with a list of questions to an international audience at the FSFE Legal and Licensing Workshop in April 2017. This page is for capturing various discussions that have come out of that to try to form concrete proposals to be considered by the larger SPDX community and then a sensible and complete policy formed.
As a starting point, please review the slides from the presentation available here: https://docs.google.com/presentation/d/1miQz9F7q_oVbYCibTuhSrJ_qog6eHWs0DxcXxQ-ZLuk/edit?usp=sharing
Summary of current "default policy" and questions/issues to be resolved
By way of summary (also in the above slides), the SPDX License List default policy for non-English license can be described as:
- Add the license to the SPDX License List in the "canonical" or original language; or the language version as requested (or what came first)
- Assign a short identifier based on 1
- If the license has "official" translations, then provide links to such translations in the notes field (but do not add translations as different languages) where "official" translations are those by the license author or otherwise blessed by the license author
the above implies the following:
- one short identifers can be used for all official translations
- one can consider a match across any official translation
