THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx

Difference between revisions of "Technical Team/Use Cases/2.0/SPDX data indicating subset of the source that made it into a particular binary or binary package"

From SPDX Wiki
Jump to: navigation, search
(Convert to MediaWiki syntax)
 
Line 1: Line 1:
−
<ol style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: 13px;" type="1"><li class="MsoNormal"><strong>Title:</strong>&nbsp;SPDX data indicating subset of the source that made it into a particular binary or binary package</li><li class="MsoNormal"><strong>Primary Actor:</strong>&nbsp;Builder of binary copyrightable artifact</li><li class="MsoNormal"><strong>Goal in Context:</strong>&nbsp;To be able to indicate the SPDX data for the source code copyrightable artifacts that made their way into a particular copyrightable binary artifacts.</li><li class="MsoNormal"><strong>&nbsp;Stakeholders and Interests:</strong>&nbsp;<ol type="1"><li class="MsoNormal"><strong>Binary Builder:&nbsp;</strong><ol type="1"><li class="MsoNormal">To communicate the licensing information for their binary copyrightable artifact, including what source files where built into it and a reference to their SPDX data.</li><li class="MsoNormal">To have their licenses respected</li><li class="MsoNormal">To help consumers understand what they are getting.</li></ol></li><li class="MsoNormal"><strong>Consumers of application copyrightable artifacts:</strong><ol type="1"><li class="MsoNormal">To receive accurate and clear information of licensing of artifacts</li><li class="MsoNormal">To be able to comply easily with licenses for artifacts</li><li class="MsoNormal">To be able to subset, extend, or aggregate artifacts and pass on clear authoritative verifiable license for the resulting new copyrightable artifacts.</li></ol></li></ol></li><li class="MsoNormal"><strong>Preconditions:</strong>&nbsp;<ol type="1"><li class="MsoNormal">Binary builder has some way to understand what source is built into their binary</li><li class="MsoNormal">Binary builder has some understanding of the license informatino for the source built into their binary and an expression of it in SPDX form.</li></ol></li><li class="MsoNormal"><strong>Main Success Scenario:</strong>&nbsp;Binary builder builds a binary from a selection of source code files and can indicate exactly the SPDX data for that binary by referencing the source files SPDX data.</li><li class="MsoNormal"><strong>Failed End Condition:&nbsp;</strong>Binary builder builds a binary from a selection of source code files and cannot indicate exactly the SPDX data for that binary by referencing the source files SPDX data.</li><li class="MsoNormal"><strong>Trigger:</strong><ol type="1"><li class="MsoNormal">Binary build time</li><li class="MsoNormal">Commit time?</li></ol></li><li class="MsoNormal"><strong>Notes:</strong>&nbsp; analagous to the 'Postgres without contrib directory' scenario (i.e. my binary was built from all that source described by that SPDX file, EXCEPT I intentionally left out the contrib folder that was under GPL. &nbsp;Said another way, my build only included this subset of files. &nbsp;Similar to Yocto build scenario..)</li></ol>
+
# '''Title:''' SPDX data indicating subset of the source that made it into a particular binary or binary package
 +
# '''Primary Actor:''' Builder of binary copyrightable artifact
 +
# '''Goal in Context:''' To be able to indicate the SPDX data for the source code copyrightable artifacts that made their way into a particular copyrightable binary artifacts.
 +
# ''' Stakeholders and Interests:'''
 +
## '''Binary Builder: '''
 +
### To communicate the licensing information for their binary copyrightable artifact, including what source files where built into it and a reference to their SPDX data.
 +
### To have their licenses respected
 +
### To help consumers understand what they are getting.
 +
## '''Consumers of application 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.
 +
# '''Preconditions:'''
 +
## Binary builder has some way to understand what source is built into their binary
 +
## Binary builder has some understanding of the license informatino for the source built into their binary and an expression of it in SPDX form.
 +
# '''Main Success Scenario:''' Binary builder builds a binary from a selection of source code files and can indicate exactly the SPDX data for that binary by referencing the source files SPDX data.
 +
# '''Failed End Condition: '''Binary builder builds a binary from a selection of source code files and cannot indicate exactly the SPDX data for that binary by referencing the source files SPDX data.
 +
# '''Trigger:'''
 +
## Binary build time
 +
## Commit time?
 +
# '''Notes:''' analagous to the 'Postgres without contrib directory' scenario (i.e. my binary was built from all that source described by that SPDX file, EXCEPT I intentionally left out the contrib folder that was under GPL. Said another way, my build only included this subset of files. Similar to Yocto build scenario..)
 +
 
 +
[[Category:Technical]]

Latest revision as of 13:19, 7 March 2013

  1. Title: SPDX data indicating subset of the source that made it into a particular binary or binary package
  2. Primary Actor: Builder of binary copyrightable artifact
  3. Goal in Context: To be able to indicate the SPDX data for the source code copyrightable artifacts that made their way into a particular copyrightable binary artifacts.
  4. Stakeholders and Interests:
    1. Binary Builder:
      1. To communicate the licensing information for their binary copyrightable artifact, including what source files where built into it and a reference to their SPDX data.
      2. To have their licenses respected
      3. To help consumers understand what they are getting.
    2. Consumers of application copyrightable artifacts:
      1. To receive accurate and clear information of licensing of artifacts
      2. To be able to comply easily with licenses for artifacts
      3. To be able to subset, extend, or aggregate artifacts and pass on clear authoritative verifiable license for the resulting new copyrightable artifacts.
  5. Preconditions:
    1. Binary builder has some way to understand what source is built into their binary
    2. Binary builder has some understanding of the license informatino for the source built into their binary and an expression of it in SPDX form.
  6. Main Success Scenario: Binary builder builds a binary from a selection of source code files and can indicate exactly the SPDX data for that binary by referencing the source files SPDX data.
  7. Failed End Condition: Binary builder builds a binary from a selection of source code files and cannot indicate exactly the SPDX data for that binary by referencing the source files SPDX data.
  8. Trigger:
    1. Binary build time
    2. Commit time?
  9. Notes: analagous to the 'Postgres without contrib directory' scenario (i.e. my binary was built from all that source described by that SPDX file, EXCEPT I intentionally left out the contrib folder that was under GPL. Said another way, my build only included this subset of files. Similar to Yocto build scenario..)
Retrieved from "https://wiki.spdx.org/index.php?title=Technical_Team/Use_Cases/2.0/SPDX_data_indicating_subset_of_the_source_that_made_it_into_a_particular_binary_or_binary_package&oldid=1924"