license-list-XML VS bitcoin-sv

The LGPLv3 exception had an atypical feature (for *GPL exceptions) and was possibly misdrafted, see: https://github.com/spdx/license-list-XML/issues/1672

X Doubt

Shortly after, they had the gall to ask for that garbage fire of a license to be included in a catalog of open source licenses. And then claimed to not understand how that request could possibly be denied...

My doubt is if there is some programmatic use of SPDX. If not why they have such a strict syntax as specified here. Also there are multiple extra tools on the github repo for parsing, comparing and even generating spdx files like this. Now if user is just mentioning the license identifiers why do we need all these? And what does it mean to compare licenses as it seems that they're using string comparison techniques to find closest match to license in their catalogue.

Yes, they acted very puzzled when an open source license catalog refused to include their weird thing.

At some point, Daniel Connolly applied for OpenBSV to be included in the SPDX license list, but was promptly rejected due its field of use restriction.

After regular development activity, all bitcoinSV branches show now activity for over a month.

You can read the license at: https://github.com/bitcoin-sv/bitcoin-sv/blob/master/LICENSE

Have you read the BSV license?

For more information please visit https://www.bitcoinsv.io/ and https://github.com/bitcoin-sv/bitcoin-sv/

There you go: https://github.com/bitcoin-sv/bitcoin-sv/commit/f498f103f6cb8bf033b430723c4d3c5cf567e63f