Re: explanation for ensuring no duplicate identifiers
|
Alexios Zavras
My only comment would be to change “ASCII characters” to “ASCII printable characters”.
Looking at the Overview page, it needs a little care:
-- zvr –
From: Spdx-legal@... <Spdx-legal@...>
On Behalf Of J Lovejoy
Hi all,
As discussed on the call today (related to Issue https://github.com/spdx/license-list-XML/pull/651 ), we will add an explicit statement regarding not duplicating identifiers in the explanation of fields on the Overview page for the license list: https://spdx.org/spdx-license-list/license-list-overview
I had the task to suggest some additional language, including discussion about character type. The relevant text is as follows, with proposed changes in red:
B) License or Exception Identifier (aka "SPDX Short Identifier") • Short identifier to be used to identify a license or exception match to licenses or exceptions contained on the SPDX License List in the context of an SPDX file, in source file, or elsewhere • Short identifiers have no spaces in them and only use ASCII characters • Short identifiers consist of an abbreviation based on a common short name or acronym for the license or exception • Where applicable, the abbreviation will be followed by a dash and then the version number, in X.Y format • Where applicable, and if possible, the short identifier should be harmonized with other well-known open source naming sources (i.e., OSI, Fedora, etc.) • Short identifiers should be as short in length as possible while staying consistent with all other naming criteria • Short identifiers must not be duplicative: newly added short identifiers will be checked to ensure they are different from all pre-existing short identifiers, regardless of upper/lower case
Let me know your thoughts,
Jilayne Intel Deutschland GmbH
|
|
|