Kate Stewart
Kate Stewart
Size of File (optional) - express as number of bytes similar to mechanism used for snippet. Will be useful for heuristics working with snippets and licensing.
Thomas: Expand §8.3.4 Annotation Type with new values “LICENSE” | “PATENT”. Enables annotator to more precisely indicate type of annotation Discussed use case brought up by customers - will save...
From meeting, there is still too much ambiguity around the algorithm to include in 2.3. see: https://github.com/spdx/spdx-spec/pull/734 for background.
Problem: how do we capture sets of related licenses, esp. Translations - Proposed solution: treat every license as separate file, then describe relationship w/ new element? - Any way to...
Thomas: Make the matching template formats of license part of the spec - both SPDX listed licenses and NON-SPDX listed licenses. Would like to add matching guidelines annotation to SPDX...
Thomas: Instead of PackageCopyrightText and CopyrightText add introduce new PackageCopyrightHolder and CopyrightText. Both optional and more than one entry can exists per SPDX-File or SPDX-Package. Better indicates individual rights holders...
This was https://bugs.linuxfoundation.org/show_bug.cgi?id=1334 **Kate Stewart 2015-12-08 16:57:25 UTC** From David Wheeler on December 4, 2015 The current Appendix IV is also overly complex and confusing: * There's no need to...
From Mark Atwood: **Proposed**: two methods for for organizations to self-declare SPDX license identifiers. The two methods will be referred to a “organization names” and “dns names”. **Organization Name:** The...
This was https://bugs.linuxfoundation.org/show_bug.cgi?id=1189 Moving it here so we don't loose track of it, but this is likely to be handled by other projects outside SPDX (OpenChain, SParts (w/ Hyperledger), etc.)...
Use Case: Enable reproduce accurate results, some parameter metadata for the tooling would be useful to captured, and fed back into a different run of the tools. Use Case: Location...