Difference between revisions of "Technical Team/Use Cases/2.0"

1. Code commits (original work intended for the project)
1. <a href="http://spdx.org/wiki/committers-provides-spdx-data-code-being-committed">Committer provides SPDX data</a> [OK]
2. <a href="http://spdx.org/wiki/contributor-makes-commit-subject-existing-spdx-data-project">Contributor makes commit  subject to existing SPDX data of project</a> [OK]
2. <a href="http://spdx.org/wiki/committer-annotates-source-files-spdx-data">Committer annotates source files with SPDX data</a> [OK]
3. Patches (original work intended for the project)
1. <a href="http://spdx.org/wiki/patch-provider-provides-spdx-data-patch">Patch provider provides SPDX data for the patch</a> [OK]
2. <a href="http://spdx.org/wiki/patch-provider-provides-spdx-data-patch-indicating-it-licensed-however-hell-its-applied">Patch provider provides SPDX data for the patch indicating it is licensed however the hell its applied</a> [OK]
3. <a href="http://spdx.org/wiki/patch-provider-provides-patch-subject-existing-spdx-data-project">Patch provider provides patch subject to existing SPDX data of project</a> [OK]
4. Patch provider provides a patch that modifies existing SPDX data of project
1. <a href="http://spdx.org/wiki/downstream-consumers-contributing-patches-provide-spdx-data-upstream-doesnt-have-it">Downstream consumers contributing patches to provide SPDX data to an upstream that doesn't have it.</a>[OK]
2. <a href="http://spdx.org/wiki/downstream-consumers-contributing-patches-provide-corrections-spdx-data-upstream-does-have-it">Downstream consumers contributing patches to provide corrections to SPDX data for an upstream that does have it.</a> [OK]
5. <a href="http://spdx.org/wiki/spdx-20-usecase-upstream-maintainer-providing-spdx-data">Upstream maintainer providing SPDX data</a>
1. <a href="http://spdx.org/wiki/upstream-maintainer-providing-spdx-data-source-archive">Upstream maintainer providing SPDX data in source archive</a>[OK]
2. <a href="http://spdx.org/wiki/upstream-maintainer-providing-spdx-data-scm">Upstream maintainer providing SPDX data in SCM</a> [OK]
3. <a href="http://spdx.org/wiki/upstream-maintainer-providing-spdx-data-url">Upstream maintainer providing SPDX data at a URL</a> [OK]
4. <a href="http://spdx.org/wiki/upstream-maintainer-preparing-release-artifacts-including-spdx-data">Upstream maintainer preparing release artifacts (including SPDX data).</a> [OK]
6. Project maintainer incorporates another project
1. <a href="http://spdx.org/wiki/project-maintainer-incorporates-another-project-including-source">Project maintainer incorporates another project by including source</a> [OK]
2. <a href="http://spdx.org/wiki/project-maintainer-incorporates-another-project-including-binary">Project maintainer incorporates another project by including binary</a> [OK]
3. <a href="http://spdx.org/wiki/project-maintainer-pulling-individual-files-out-another-project-subsetting">Project maintainer pulling individual files out of another project (subsetting)</a> [OK]
7. Ease adoption
1. <a href="http://spdx.org/wiki/low-cost-spdx-file">Allow a low investment SPDX producer to produce valid SPDX data</a> [OK-fathomed but not Approved for Implementation]
2. <a href="http://spdx.org/wiki/producing-valid-spdx-files-face-missing-data">Produce a valid SPDX dataset even if some data is missing</a> [OK]
8. Intermediate packager (rpm, deb, etc) passing on and adding to SPDX Data
1. Intermediate packager builds source package from upstream source
1. <a href="http://spdx.org/wiki/intermediate-packager-builds-source-package-upstream-source-provides-spdx-data">Intermediate packager builds source package from upstream source that provides SPDX data</a> [OK]
2. <a href="http://spdx.org/wiki/intermediate-packager-builds-source-package-upstream-source-does-not-provide-spdx-data">Intermediate packager builds source package from upstream source that does not provide SPDX data</a> [OK]
2. Intermediate packager builds binary package from upstream source
1. <a href="http://spdx.org/wiki/intermediate-packager-builds-binary-package-upstream-source-provides-spdx-data">Intermediate packager builds binary package from upstream source that provides SPDX data</a> [OK]
2. <a href="http://spdx.org/wiki/intermediate-packager-builds-binary-package-upstream-source-does-not-provides-spdx-data">Intermediate packager builds binary package from upstream source that does not provides SPDX data [OK]</a>
3. Intermediate packager adds patches to upstream source 
1. <a href="http://spdx.org/wiki/intermediate-packager-adds-patches-upstream-source-provides-spdx-data">Intermediate packager adds patches to upstream source that provides SPDX data</a> [OK]
2. <a href="http://spdx.org/wiki/intermediate-packager-adds-patches-upstream-source-does-not-provide-spdx-data">Intermediate packager adds patches to upstream source that does not provide SPDX data [OK]</a>
4. Intermediate packager adds someone else's patches to upstream source
1. <a href="http://spdx.org/wiki/intermediate-packager-adds-someone-elses-patches-upstream-source-provides-spdx-data">Intermediate packager adds someone else's patches to upstream source that provides SPDX data</a> [OK]
2. <a href="http://spdx.org/wiki/intermediate-packager-adds-someone-elses-patches-upstream-source-does-not-provide-spdx-data">Intermediate packager adds someone else's patches to upstream source that does not provide SPDX data</a> [OK]
5. Intermediate packager subsetting upstream source
1. <a href="http://spdx.org/wiki/intermediate-packager-subsetting-upstream-source-provides-spdx-data">Intermediate packager subsetting upstream source that provides SPDX data</a> [OK]
2. <a href="http://spdx.org/wiki/intermediate-packager-subsetting-upstream-source-does-not-provide-spdx-data">Intermediate packager subsetting upstream source that does not provide SPDX data [OK]</a>
9. Build systems (build systems want to pass on SPDX data for the thing they are building)
1. <a href="http://www.spdx.org/wiki/spdx-use-case-build-systems-yocto">Yocto</a> [OK]
2. Linking
1. <a href="http://spdx.org/wiki/debian-has-interest-only-building-things-are-linking-license-compatible">Debian has an interest in only building things that are linking license compatible</a> [OK]
3. I just made a binary out of some source
1. <a href="http://spdx.org/wiki/spdx-data-indicating-subset-source-made-it-particular-binary-or-binary-package">SPDX data indicating subset of the source that made it into a particular binary or binary package</a> [OK]
10. Aggregator aggregating many 'copyrightable items' for redistribution
1. <a title="Linux Distro" href="https://spdx.org/wiki/linux-distro">Linux Distros</a> [OK]
2. <a href="http://spdx.org/wiki/embedded-images-eg-router-images-switch-images">Embedded Images (e.g. router images, switch images)</a> [OK]
3. <a href="http://spdx.org/wiki/spdx-20-usecase-reference-implementations">Reference implementations </a>[OK]
4. <a href="http://spdx.org/wiki/spdx-20-usecase-application-which-ships-documentation-media-software">Application which ships with documentation +  media + software</a> [OK]
5. <a title="Use case details" href="http://spdx.org/wiki/application-which-ships-contrib-libraries">Application which ships with a contrib libraries</a> [OK]
6. <a title="Use case details" href="http://spdx.org/wiki/application-which-ships-development-tools">Application which ships with development tools</a> [OK]
7. <a href="http://spdx.org/wiki/subsetting-out-only-shippable-bits-stuff-coming-sdk">Subsetting out only the shippable bits of stuff coming from an SDK</a> [OK]
8. <a href="http://spdx.org/wiki/aggregators-aggregating-other-aggregations-redistribution">Aggregators aggregating other aggregations for redistribution</a> [OK]
11. Consumers receiving SPDX data
1. <a href="http://spdx.org/wiki/provide-sufficient-data-allow-consumer-comply-licenses-redistribution">Provide sufficient data to allow consumer to comply with licenses on redistribution</a> Alcatel-Lucent requirements attached [OK]
12. <a href="http://spdx.org/wiki/consuming-code-snippets">Consuming code snippets </a>(God help us all) (subfile pieces of code not originally intended for the project) [OK]
13. Signoff/multiple signoff on SPDX data
1. <a target="_blank" title="Contracts with multiple parties requiring signoff by all" href="https://spdx.org/wiki/multi-party-contracts">Contracts with multiple parties requiring signoff by al</a>l [MORE INFO REQUESTED Kate Stewart]
14. Third party does licensing analysis
1. <a href="http://spdx.org/wiki/third-party-produces-bill-materials-software-package">Third party generates license analysis</a> [OK]
2. <a href="http://spdx.org/wiki/collecting-enough-information-allow-auditor-make-recommendations-remove-or-not-component">Collecting enough information to allow auditor to make recommendations to remove or not a component</a> [MORE INFO REQUESTED]
15. Auditor Analyzing/Sanity-checking/correcting Bill of Material he's handed
1. <a href="http://spdx.org/wiki/use-case-backtrack-binary-source-files">Backtrack from compiled/binary file to constituent files</a> [MORE STUDY NEEDED]
2. outbound: validate that SPDX goes hand in hand with what's being shipped [Kirsten Newcomer]
1. <a href="http://spdx.org/wiki/check-see-if-spdx-data-provided-matches-files-provided" title="Check to see if the SPDX data provided matches the files provided and is trustworthy and most current for package">Check to see if the SPDX data provided matches the files provided</a> [OK larger scope]
16. Extensions:
1. <a href="http://spdx.org/wiki/communicate-data-beyond-what-described-spec">Communicate data beyond what is described in spec between consenting parties w/o breaking consumers that are not in the know</a> [OK]
2. <a href="http://spdx.org/wiki/license-list-extension">License list extensions, how do you handle folks who have more licenses than SPDX</a> [OK]
3. <a href="http://spdx.org/wiki/decorating-already-produces-and-signed-spdx-dataset-extension-data">Decorating an already produces and signed SPDX dataset with extension data</a> [Bill Schineller]
17. Other arising during vetting...
1. Given 2 SPDX files about the same codebase from the same source, be able to tell which is the later rev / more current and correct one.

Themes:

1. Root of data (closer to upstream the better)
2. Subsetting of copyrightable things (and their SPDX data) (Note: Subsets of copyrightable things are usually also copyrightable things)
3. Aggregation of copyrightable things (and their SPDX data) (Note: Aggregations of copyrightable things are usually also copyrightable things).