Repository navigation
docs: recommend exact casing for DocumentRef-, LicenseRef-, and AdditionRef- prefixes (#1505) - #1507
Open
ShivanshhhG wants to merge 2 commits into
Open
ShivanshhhG wants to merge 2 commits into
ShivanshhhG wants to merge 2 commits into
Conversation
…ionRef- prefixes (spdx#1505) Clarify in the License Expression Annex case-sensitivity guidelines that, in addition to using the exact casing for license and exception identifiers from the License List and all uppercase for operators/special identifiers, it is also recommended to use the exact casing for the 'DocumentRef-', 'LicenseRef-', and 'AdditionRef-' prefixes. Fixes spdx#1505 Signed-off-by: SHIVANSH-ux-ys <singaser78@gmail.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
In #1475, recommendations for license expression casing were introduced. As discussed in #1505 by @bernhardreiter and @swinslow, the recommendation covered operators, special identifiers, and license/exception identifiers from the License List, but omitted explicit recommendations for the user-defined and external reference prefixes (
DocumentRef-,LicenseRef-, andAdditionRef-).This PR clarifies the case-sensitivity recommendations in
docs/annexes/spdx-license-expressions.mdto explicitly recommend using the exact casing forDocumentRef-,LicenseRef-, andAdditionRef-prefixes.Fixes #1505