THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx
Technical Team/Use Cases/2.0/Project maintainer pulling individual files out of another project (subsetting)
From SPDX Wiki
< Technical Team | Use Cases/2.0
Revision as of 13:19, 7 March 2013 by MartinMichlmayr (Talk | contribs)
- Title: Project maintainer pulling individual files out of another project (subsetting)
- Primary Actor: Member of upstream maintainer team
- Goal in Context: To include individual files from another project (subsetting), and reference the SPDX data from the incorporated project for those files.
- Stakeholders and Interests:
- Upstream maintainers:
- To communicate the licensing information for their copyrightable artifacts including the included project.
- To have their licenses respected
- Incorporated Project maintainers:
- To have their licenses respected
- Consumers of upstreams copyrightable artifacts:
- To receive accurate and clear information of licensing of artifacts
- To be able to comply easily with licenses for artifacts
- To be able to subset, extend, or aggregate artifacts and pass on clear authoritative verifiable license for the resulting new copyrightable artifacts.
- Upstream maintainers:
- Preconditions:
- Incorporated project maintainers have selected licenses for the copyrightable artifacts originating with the project (package, files, etc) and provided SPDX data for those copyrightable artifacts.
- Upstream has identified license data for other copyrightable artifacts they consume
- Main Success Scenario: Upstream communicates accurate complete licensing information for their copyrightable artifacts in an SPDX data format including the information for the incorporated project.
- Failed End Condition: Upstream communicates inaccurate incomplete licensing information for their copyrightable artifacts.
- Trigger:
- Incorporate of another projects copyrightable artifacts.
- Notes: