On Mon, Nov 20, 2023 at 3:28 PM Neal Gompa <[email protected]> wrote: > > Hey folks, > > As Fedora has been moving toward SPDX identifiers, I'd like to revisit > something I brought up several years ago: the enforcement of uppercase > operands. > > I personally find the uppercase operands difficult to read and they > make the whole stanza difficult for me to easily pick out the > individual licenses. > > For example, one of my packages has this: GPL-2.0-or-later and MIT and > BSD-1-Clause and BSD-2-Clause and BSD-3-Clause and BSL-1.0 and > LGPL-2.1-or-later and CC0-1.0 and (CC0-1.0 or OpenSSL or Apache-2.0) > and LicenseRef-Fedora-Public-Domain and (BSD-3-Clause or GPL-2.0-only) > > For me, I find this tremendously easier because all the identifiers > are capitalized, so I can easily read the total combination and then > process the boolean logic described. > > When all the operands are uppercase, it's hard for me to tell at a > glance between license tags and operands, and it's much more difficult > for me to read. > > There's an insistence that SPDX mandates uppercase operands, but from > what I can tell, tools don't care one way or another. Can we please > adjust SPDX guidance so lowercase operands are permitted?
(not sure if this should be on spdx-legal, this is a question about the SPDX license expression grammar) I assume this would require a change to the SPDX spec, which says: "License expression operators (AND, OR and WITH) should be matched in a case-sensitive manner." https://spdx.github.io/spdx-spec/v2.3/SPDX-license-expressions/ Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1799): https://lists.spdx.org/g/spdx/message/1799 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]] -=-=-=-=-=-=-=-=-=-=-=-
