Thanks, Steve and Kyle. The link to the draft is particularly helpful.
I don't want to rehash the many, many discussions about which licenses
should be included in the official list; suffice to say, are there any best
practices folks here are aware of for naming these? I saw
Hi Richard,
Here are some minutes from a previous review mentioning a potential long term
solution for non-listed exceptions:
https://wiki.spdx.org/view/Legal_Team/Archive/license_expression_syntax
I also recall a discussion on the topic. It has been a while (and my memory is
far from
Hi Richard,
Thanks for this -- all good points and I agree, in the example you gave I'd
represent it in the way you described.
As an FYI, regarding custom exceptions (and agreed that the example you
gave wouldn't fit into the "exception list" category) -- there is an open
issue for consideration
If you have a standard license text (that maps to one of the SPDX
license identifiers) coupled with some additional nonstandardized
terms, which are not captured by anything in the exceptions list
(which IIRC are not supposed to cover supplementary restrictive terms
anyway, though I seem to
