Gary O'Neall
Gary O'Neall
The SPDX 3.0 uses a different toolchain - closing as resolved
I believe this has been answered - closing issue as resolved
> stay with the current set of properties from 2.3 and do not change --> a mapping needs to be maintained and not all features from 3.0 are available I...
> I'm not even sure that all 29 of them are useful, so we might as well be explicit to what is allowed instead of a blanket "use anything by...
> none of the SPDX Lite fields are about Files or Snippets, so they cannot appear inside files. Two thoughts: - We include a union of the Lite fields with...
I believe this is resolved in 3.0.
@stefan6419846 Thanks for pointing this out. > The license XML can be accessed in the license-list-data repository under the license-list-XML directory. A recent decision was made to support the license...
This is now implemented in the license-list-data repo - closing as resolved.
Although it has been a while, I do recall when we created the DESCRIBES requirement. I think the description in the DESCRIBES is not very accurate based on my (perhaps...
I just re-read the issue. Since this is tag/value, I would allow no DESCRIBES relationship if there is a single package. You would create an implicit DESCRIBES relationship when deserializing....