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

Difference between revisions of "Technical Team/Proposals/2012-02-01/Merged Model Proposal"

From SPDX Wiki
Jump to: navigation, search
(Convert to MediaWiki syntax)
Line 1: Line 1:
<p>Below is a class diagram merging Ed Warnicke's proposed SPDX Element model with the 1.0 model.&nbsp; Definately a work in progress.&nbsp; Most of the class definitions can be found in the 1.0 spec in the RDF appendix (model) or in Ed's proposal (<a href="http://spdx.org/wiki/rough-proposal-hierarchy-signing-and-supply-chain-friendliness-spdx-20">http://spdx.org/wiki/rough-proposal-hierarchy-signing-and-supply-chain-friendliness-spdx-20</a>).</p><p>The goals of this proposal are to:</p><p>- Support the use cases for the 1.0 spec</p><p>- Support the supply chain use cases</p><p>- Support the "hierarchical" or embedded package use cases</p><p>- Provide a more abstract model which can simplify the application of SPDX to some of the more complex use cases</p><p>This proposal extends the existing proposals by adding an SPDX Element Relationship which describes the type of relationship from one SPDX element to another.</p><p>&nbsp;See the attached document for the mapping between the SPDX 1.0 properties and this proposal.</p><p>See the attached document for a proposal on creating RDF references to other Licensable documents which can be verified through checksums.</p><p>&nbsp;Model updated based on technical team meeting discusions:</p><ul><li>Changed top level SPDXFile to SPDXDocument</li><li>Removed Annotation</li><li>Added SPDXDcoument Relationship</li></ul><p>&nbsp;&nbsp;</p><p>&nbsp;<img src="http://www.spdx.org/system/files/spdxmodel-3-14-2013.png" alt="Class Diagram" width="909" height="529" /></p>
+
Below is a class diagram merging Ed Warnicke's proposed SPDX Element model with the 1.0 model. Definately a work in progress. Most of the class definitions can be found in the 1.0 spec in the RDF appendix (model) or in [[Technical_Team/Proposals/Rough_proposal_for_provenance,_hierarchy_and_aggregation,_and_supply_chain_friendliness_in_SPDX_2.0|Ed's proposal]].
 +
 
 +
The goals of this proposal are to:
 +
 
 +
* Support the use cases for the 1.0 spec
 +
* Support the supply chain use cases
 +
* Support the "hierarchical" or embedded package use cases
 +
* Provide a more abstract model which can simplify the application of SPDX to some of the more complex use cases
 +
 
 +
This proposal extends the existing proposals by adding an SPDX Element Relationship which describes the type of relationship from one SPDX element to another.
 +
 
 +
See the attached document for the mapping between the SPDX 1.0 properties and this proposal.
 +
 
 +
See the attached document for a proposal on creating RDF references to other Licensable documents which can be verified through checksums.
 +
 
 +
Model updated based on technical team meeting discusions:
 +
 
 +
* Changed top level SPDXFile to SPDXDocument
 +
* Removed Annotation
 +
* Added SPDXDcoument Relationship
 +
 
 +
[[Image:Spdxmodel-3-14-2013.png|909px|Class Diagram]]
 +
 
 +
[[Category:Technical]]

Revision as of 08:22, 22 March 2013

Below is a class diagram merging Ed Warnicke's proposed SPDX Element model with the 1.0 model. Definately a work in progress. Most of the class definitions can be found in the 1.0 spec in the RDF appendix (model) or in Ed's proposal.

The goals of this proposal are to:

  • Support the use cases for the 1.0 spec
  • Support the supply chain use cases
  • Support the "hierarchical" or embedded package use cases
  • Provide a more abstract model which can simplify the application of SPDX to some of the more complex use cases

This proposal extends the existing proposals by adding an SPDX Element Relationship which describes the type of relationship from one SPDX element to another.

See the attached document for the mapping between the SPDX 1.0 properties and this proposal.

See the attached document for a proposal on creating RDF references to other Licensable documents which can be verified through checksums.

Model updated based on technical team meeting discusions:

  • Changed top level SPDXFile to SPDXDocument
  • Removed Annotation
  • Added SPDXDcoument Relationship

Class Diagram