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/Check to see if the SPDX data provided matches the files provided and is trustworthy and most current for package"

From SPDX Wiki
Jump to: navigation, search
(Convert to MediaWiki syntax)
 
Line 1: Line 1:
−
<ol><li><strong>Title:</strong> Check to see if the SPDX data provided matches the files provided</li><li><strong>Primary Actor:</strong> Downstream consumer of a package</li><li><strong>Goal in Context:</strong> Verify that the license obligations for code provided by the upstream supplier matches the licensing information provided by the supplier</li><li><strong>Stakeholders and Interests:</strong></li><ol><li><strong>Upstream Supplier: </strong></li><ol><li>Express the contents of the delivered software and the license obligations in a manner which can be easily verified by the consumer</li></ol><li><strong>Downstream Consumer:</strong></li><ol><li>Verify the files match the description provided</li><li>Verify the origin of the files match</li><li>Verify the license obligations match</li><li>Provide the verified information to further downstream consumers</li></ol></ol><li><strong>Preconditions:</strong></li><ol><li>Upstream provider provides an SPDX file along with the package&nbsp;</li></ol><li><strong>Main Success Scenario:</strong></li><ol><li>Supplier provides package and SPDX file.</li><li>Consumer runs runs file checksums against received files and compares to the SPDX file to validate file origin.</li><li>Consumer compares SPDX author and reviewer information and compares to a "trusted" list of authors.&nbsp; Reviewer and supplier information is confirmed by verifying their signatures. (signing)</li><li>Consumer searches for any later revisions of the SPDX file which may contain corrections.</li><li>Consumer runs independent tools verifying information.&nbsp; If any corrections are required, an updated SPDX file is produced and sent back to the supplier for comment.</li></ol><li><strong>Failed End Condition:</strong> No SPDX file provided.&nbsp; No signatures for author and/or reviewers.&nbsp; Internally inconsistent SPDX file.</li><li><strong>Trigger:</strong><ol><li>Delivery of a software package</li></ol></li><li><strong>Notes:</strong>&nbsp; </li><ol><li>The scenerio could work without an initial SPDX file if all of the information is provided in a different format.&nbsp; In this scenario, an SPDX file would be created as an output and the input pre-conditions would be essentially all of the required fields of the SPDX document.</li><li>Possibly related/required functionality: the ability to easily compute the differences between different SPDX documents about the same or slightly different packages.&nbsp; e.g. two different SPDX producers provide&nbsp; SPDX documents for package 'time'.&nbsp; If they are indeed for the same exact package / set of files, do they agree on the overall licensing and per-file licensing?&nbsp; If they are for slightly different packages (e.g. 'time' package version X vs. time package Y, which files are different from in each SPDX doc and which licensing has changed? </li></ol></ol>
+
# '''Title:''' Check to see if the SPDX data provided matches the files provided
 +
# '''Primary Actor:''' Downstream consumer of a package
 +
# '''Goal in Context:''' Verify that the license obligations for code provided by the upstream supplier matches the licensing information provided by the supplier
 +
# '''Stakeholders and Interests:'''
 +
## '''Upstream Supplier: '''
 +
### Express the contents of the delivered software and the license obligations in a manner which can be easily verified by the consumer
 +
## '''Downstream Consumer:'''
 +
### Verify the files match the description provided
 +
### Verify the origin of the files match
 +
### Verify the license obligations match
 +
### Provide the verified information to further downstream consumers
 +
# '''Preconditions:'''
 +
## Upstream provider provides an SPDX file along with the package
 +
# '''Main Success Scenario:'''
 +
## Supplier provides package and SPDX file.
 +
## Consumer runs runs file checksums against received files and compares to the SPDX file to validate file origin.
 +
## Consumer compares SPDX author and reviewer information and compares to a "trusted" list of authors. Reviewer and supplier information is confirmed by verifying their signatures. (signing)
 +
## Consumer searches for any later revisions of the SPDX file which may contain corrections.
 +
## Consumer runs independent tools verifying information. If any corrections are required, an updated SPDX file is produced and sent back to the supplier for comment.
 +
# '''Failed End Condition:''' No SPDX file provided. No signatures for author and/or reviewers. Internally inconsistent SPDX file.
 +
# '''Trigger:'''
 +
## Delivery of a software package
 +
# '''Notes:'''
 +
## The scenerio could work without an initial SPDX file if all of the information is provided in a different format. In this scenario, an SPDX file would be created as an output and the input pre-conditions would be essentially all of the required fields of the SPDX document.
 +
## Possibly related/required functionality: the ability to easily compute the differences between different SPDX documents about the same or slightly different packages. e.g. two different SPDX producers provide SPDX documents for package 'time'. If they are indeed for the same exact package / set of files, do they agree on the overall licensing and per-file licensing? If they are for slightly different packages (e.g. 'time' package version X vs. time package Y, which files are different from in each SPDX doc and which licensing has changed?
 +
 
 +
[[Category:Technical]]

Latest revision as of 13:22, 7 March 2013

  1. Title: Check to see if the SPDX data provided matches the files provided
  2. Primary Actor: Downstream consumer of a package
  3. Goal in Context: Verify that the license obligations for code provided by the upstream supplier matches the licensing information provided by the supplier
  4. Stakeholders and Interests:
    1. Upstream Supplier:
      1. Express the contents of the delivered software and the license obligations in a manner which can be easily verified by the consumer
    2. Downstream Consumer:
      1. Verify the files match the description provided
      2. Verify the origin of the files match
      3. Verify the license obligations match
      4. Provide the verified information to further downstream consumers
  5. Preconditions:
    1. Upstream provider provides an SPDX file along with the package
  6. Main Success Scenario:
    1. Supplier provides package and SPDX file.
    2. Consumer runs runs file checksums against received files and compares to the SPDX file to validate file origin.
    3. Consumer compares SPDX author and reviewer information and compares to a "trusted" list of authors. Reviewer and supplier information is confirmed by verifying their signatures. (signing)
    4. Consumer searches for any later revisions of the SPDX file which may contain corrections.
    5. Consumer runs independent tools verifying information. If any corrections are required, an updated SPDX file is produced and sent back to the supplier for comment.
  7. Failed End Condition: No SPDX file provided. No signatures for author and/or reviewers. Internally inconsistent SPDX file.
  8. Trigger:
    1. Delivery of a software package
  9. Notes:
    1. The scenerio could work without an initial SPDX file if all of the information is provided in a different format. In this scenario, an SPDX file would be created as an output and the input pre-conditions would be essentially all of the required fields of the SPDX document.
    2. Possibly related/required functionality: the ability to easily compute the differences between different SPDX documents about the same or slightly different packages. e.g. two different SPDX producers provide SPDX documents for package 'time'. If they are indeed for the same exact package / set of files, do they agree on the overall licensing and per-file licensing? If they are for slightly different packages (e.g. 'time' package version X vs. time package Y, which files are different from in each SPDX doc and which licensing has changed?
Retrieved from "https://wiki.spdx.org/index.php?title=Technical_Team/Use_Cases/2.0/Check_to_see_if_the_SPDX_data_provided_matches_the_files_provided_and_is_trustworthy_and_most_current_for_package&oldid=1970"