If a license is requested for a package that exists in ClearlyDefined data but the specific version requested does not have data, interpret the license from the existing data.
The interpreted license will be each identified license for all versions AND together and including AND LicenseRef-clearlydefined-NODATA. In this way, we do not have do figure out where in the list of versions the requested version lies and attempt to determine which license applies if there are multiple licenses. The LicenseRef-clearlydefined-NODATA tells the consumer that there was no license data for this specific coordinates (package + version) and the return license was interpreted.
Examples...
a dependency where all licenses are MIT for all versions and a new version appears, it is interpreted as MIT AND LicenseRef-clearlydefined-NODATA
a dependency where early versions were Apache-2.0 and later versions were MIT, the interpreted license will be Apache-2.0 AND MIT AND LicenseRef-clearlydefined-NODATA
Description
If a license is requested for a package that exists in ClearlyDefined data but the specific version requested does not have data, interpret the license from the existing data.
The interpreted license will be each identified license for all versions
ANDtogether and includingAND LicenseRef-clearlydefined-NODATA. In this way, we do not have do figure out where in the list of versions the requested version lies and attempt to determine which license applies if there are multiple licenses. TheLicenseRef-clearlydefined-NODATAtells the consumer that there was no license data for this specific coordinates (package + version) and the return license was interpreted.Examples...
a dependency where all licenses are
MITfor all versions and a new version appears, it is interpreted asMIT AND LicenseRef-clearlydefined-NODATAa dependency where early versions were
Apache-2.0and later versions wereMIT, the interpreted license will beApache-2.0 AND MIT AND LicenseRef-clearlydefined-NODATA