Peter Monks

@zcaudate thanks for the feedback. Yeah I don't see a license upgrade as a burning necessity - more just some easy housekeeping I can do without risk of breaking the...

The ABNF grammar in Annex D.1 makes this explicit, and I've always understood the sentence "The exact syntax of license expressions is described below in ABNF." to mean that that...

It seems to me that the logical conclusion of that argument would be that the entire ABNF grammar needs to be duplicated and translated to plain English, which I'd argue...

I have the same issue, albeit with iterm2.

While not wanting to propose or suggest any particular solution, one possibility might be to convert the [fallback mechanism](https://github.com/technomancy/lein-licenses#fallbacks) into an override mechanism, so that any "Public Domain" licenses can...

My use case is that I work for an [Open Source software foundation](https://symphony.foundation/), and we have to validate the licenses of all inbound contributions (including transitive dependencies) before we can...

A similar issue is showing up for `[org.ow2.asm/asm-all "4.2"]`, which `lein-licenses` reports as `BSD`, when in fact it's `BSD-3-Clause` (to use the SPDX license identifier). There is no such license...

Yep I think that's about the sum of it, and I suspect the bulk of the work will be to make `lein-licenses` aware of the new property. Where I think...

> and according to SPDX putting that into every source file is also encouraged, but as the template is quite minimal I'm not sure this is a good idea. Yeah...

> We already support a vector of :licenses instead of :license if you have more than one. Sure, though that isn't sufficient to unambiguously express dual licensing (AND), alternative licensing...