You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 grammar is normative.
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 grammar is normative.
What about adding something like "For the sake of clarity, a license exception in isolation is not a valid license expression"?
I'm pretty sure there are other tools out there (eg. Fossology) that incur in the same mistake, so make it clearer would do no harm and may help avoiding such mistake
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 is inappropriate in a technical specification like the SPDX spec. ABNF is a good choice for describing this kind of thing precisely and succinctly.
see fsfe/reuse-tool#890 and and spdx/Spdx-Java-Library#227
TL;DR:
Qt-GPL-exception-1.0
(or any other "standalone" license exception) is not a valid license expression that can be put in LicenseInfoInFile.That is implied by what is written in Annex D.1, but it would be better to make it more explicit, to avoid issues like the ones mentioned above
The text was updated successfully, but these errors were encountered: