[spdx-tech] capitalization rules for SPDX license ids and operators
You can refresh your memory on the discussions (2015-2020) by reading https://github.com/spdx/spdx-spec/issues/63 😉
I still like my example from that thread: Do we really want to be able to understand
Mit and gpl-2.0 And Gpl-1.0+ aNd ePl-1.0 aND isc
or can we simplify our lives and have one way of expressing the combinations?
From: Spdx-tech@... <Spdx-tech@...>
On Behalf Of J Lovejoy
Hi Legal, Tech teams,
Intel Deutschland GmbH
On Thu, Jul 29, 2021 at 9:52 AM Alexios Zavras <alexios.zavras@...> wrote:
You can refresh your memory on the discussions (2015-2020) by reading https://github.com/spdx/spdx-spec/issues/63
IMHO it would be a good time to revisit this.From: Spdx-tech@... <Spdx-tech@...> On Behalf Of J LovejoyHowever, please be aware that it is often important to match with the case of the canonical identifier on the SPDX License List. This is because the canonical identifier's case is used in the URL of the license's or exception's entry on the List, and because the canonical identifier is translated to a URI in RDF documents.I'm wondering - was there a particular reason that the license expression operators are case-sensitive (while the license ids are not)?
The case of license identifier does not and never did really matter
otherwise. It does not matter to users. And most tools do not care
The tyranny of a serialization format (e.g. RDF) or a technical
requirement such as URL on a website should not impact everyone. These
should be solved differently.
What about adopting a simple way: define once for all that a canonical
license expression and identifier representation are either all
lowercase or all uppercase and be done with this topic for good.
+1 650 799 0949 | pombredanne@...
DejaCode - What's in your code?! - http://www.dejacode.com
AboutCode - Open source for open source - https://www.aboutcode.org
nexB Inc. - http://www.nexb.com