Hi Mary: You wrote: > Would changing the operator case affect tooling? A good practice for tools is to be flexible and lenient when accepting inputs in general, and optionally be strict (and report warning or errors then only) For instance, there is no easily discernible pattern of why an SPDX license identifier is all upper case, all lower case or mixed case, so it is hard for a human to avoid mistakes and there are many such minor case errors in the wild wrt. the case of SPDX license identifiers. Yet all SPDX identifiers are unique, ignoring the case. So in practice, most tools would ignore the case when parsing and output an expression using the specified "canonical" case of identifiers and operators.
At least that's the default behavior for the tools I maintain, so any change or mistake in case is not an issue. -- Cordially Philippe Ombredanne +1 650 799 0949 | [email protected] AboutCode - Open source for open source - https://www.aboutcode.org VulnerableCode - the open code and open data vulnerability database - https://github.com/nexb/vulnerablecode ScanCode - scan your code, for origin/license/vulnerabilities, report SBOMs - https://github.com/nexB/scancode-toolkit https://github.com/nexB/scancode.io package-url - the mostly universal SBOM identifier for packages - https://github.com/package-url DejaCode - What's in your code?! - http://www.dejacode.com nexB Inc. - http://www.nexb.com -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1808): https://lists.spdx.org/g/spdx/message/1808 Mute This Topic: https://lists.spdx.org/mt/102715215/21656 Group Owner: [email protected] Unsubscribe: https://lists.spdx.org/g/spdx/leave/2655439/21656/1698928721/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
