I was looking into the ABNF of SPDX and was wondering about the exceptions that are listed in the Scancode licensedb.
The ABNF states:
addition-expression = license-exception-id / addition-ref
with
license-exception-id = <short form license exception identifier from SPDX License List>
addition-ref = [%s"DocumentRef-"(idstring)":"]%s"AdditionRef-"(idstring)
idstring = 1*(ALPHA / DIGIT / "-" / "." )
This brings me to the conclusion that exceptions from Scancode's license DB should start with AdditionRef instead of LicenseRef. However, currently, they start with LicenseRef, e.g.:
Or is it intended to have the AdditionRef as prefix, e.g.
GPL-2.0-or-later WITH AdditionRef-LicenseRef-scancode-apromore-exception-2.0
in contrast to
GPL-2.0-or-later WITH AdditionRef-scancode-apromore-exception-2.0?
I was looking into the ABNF of SPDX and was wondering about the exceptions that are listed in the Scancode licensedb.
The ABNF states:
with
This brings me to the conclusion that exceptions from Scancode's license DB should start with
AdditionRefinstead ofLicenseRef. However, currently, they start withLicenseRef, e.g.:LicenseRef-scancode-apromore-exception-2.0LicenseRef-scancode-aptana-exception-3.0LicenseRef-scancode-bash-exception-gpl-2.0Or is it intended to have the
AdditionRefas prefix, e.g.GPL-2.0-or-later WITH AdditionRef-LicenseRef-scancode-apromore-exception-2.0in contrast to
GPL-2.0-or-later WITH AdditionRef-scancode-apromore-exception-2.0?