spdx-spec
spdx-spec copied to clipboard
spdx
The SPDX specification in MarkDown and HTML formats.
Adding this relationship will support the use case where an auditor, analyst, package supplier or packager would like to communicate specific components that are distributed to clients. For example, JavaScript...
This is WIP, because I still need to fill in some of the Bazaar section. There's no reason to require `PackageDownloadLocation` if we also allow `NOASSERTION`. This commit deprecates `NOASSERTION`,...
This is a WIP proposal. I littered it with FIXMES for now, as I'm not completely sure the semantic that I've proposed works as expected... More than happy to have...
This section has never been particularly tight. For example, the old: `` is an [idstring] that is defined in Appendix. was probably intended to reference the old Appendix VII (removed...
This is a large diff, but I aimed for restructuring/polishing without changing the end result. I did make a few minor, intentional changes: * Extended `license-id` to include appendix I.3...
From the discussion on Nov 30, 2018 NTIA Formats WG call: SPDX does not have a way to encode timelines and events related the SPDX entities These events may be:...
The RDF property `spdx:describesPackages` was deprecated when SPDX 2.0 was released and has been replaced by the `documentDescribes` in non-RDF format and the relationships in RDF. Retaining this property is...
[This PR](https://github.com/spdx/spdx-spec/pull/567) removed the following text from [`chapters/document-creation-information.md`](https://github.com/spdx/spdx-spec/blob/development/v2.2.2/chapters/document-creation-information.md): >By using this document, or any portion hereof, you hereby agree that any copyright rights (as determined by your jurisdiction) in any...
This is a meta-issue to track all the licensing-related issues for the 3.0 spec release. Not all of these issues are agreed to be added to the spec; many require...
