Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

README: Make an explicit commitment to case-insensitive uniqueness #651

Closed
wants to merge 1 commit into from
Closed

README: Make an explicit commitment to case-insensitive uniqueness #651

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,12 @@ Please note that the format for this repository is internal to the SPDX legal te

In contrast, the output files in the [SPDX license-list-data repository](https://github.com/spdx/license-list-data) are stable and well-supported, and make the License List available in RDFa, HTML, text, and JSON formats. You can use [SPDX tools](https://github.com/spdx/tools) (or create your own) to consume the supported formats of the license list.

# Case insensitivity

This project commits to never, in any past or future version, contain identifiers which differ only in case but have different semantics.
For example, the presence of an [`MIT`](src/MIT.xml) identifier in the current list means that there will never be an `Mit` identifier which matches text not matched by the `MIT` identifier.
List consumers are enouraged to use the canonical identifier casing, but this uniqueness commitment ensures that case-insensitive comparison with listed identifiers will be unambiguous.

# How to contribute/participate

We welcome contribution! See [our contribution documentation](CONTRIBUTING.md) for details.