Technical Team/Proposals/SPDX 2.0 Model Proposals - Revision history

Goneall at 18:47, 21 November 2013

2013-11-21T18:47:29Z

Goneall at 18:28, 21 November 2013

2013-11-21T18:28:57Z

MartinMichlmayr: Convert to MediaWiki syntax

2013-03-07T12:12:14Z

Convert to MediaWiki syntax

JackM at 17:59, 14 September 2012

2012-09-14T17:59:06Z

JackM at 19:13, 21 August 2012

2012-08-21T19:13:27Z

JackM at 19:12, 21 August 2012

2012-08-21T19:12:46Z

JackM at 19:10, 21 August 2012

2012-08-21T19:10:46Z

New page

3. This page brings together various modelling proposals for 2.0 under a common page. The models currently under discusson are: 1. <a title="Rough Conceptual Model" href="http://spdx.org/wiki/yet-another-rough-proposal-conceptual-model-spdx-2%20">Rough Conceptual Model</a> "This conceptual model is an attempt to incrementally add hierarchy and provenance capabilities to the existing SPDX model. Many of the <a href="http://spdx.org/wiki/spdx-20-use-cases">use cases</a> have been considered but further analysis is necessary to ensure that this model covers all scenarios. ..." 2. <a title="Supply Chain Model" href="http://spdx.org/wiki/rough-proposal-hierarchy-signing-and-supply-chain-friendliness-spdx-20">Provenance and Supply Chain Model </a>" A desire has been expressed to be able to have SPDX be capable of expressing  <ol><li><a href="http://spdx.org/wiki/sdpx-20-provenance">Provenance</a> (we can know precisely who said what and when about a package)</li><li>Hiearchy and Aggregation ( package A contains packages B, C, etc)</li><li>How software flows through a supply chain (upstream to packager, through several intermediate vendors to consumer) ..."</li></ol> 3. <a title="Merged Model Proposal" href="http://www.spdx.org/wiki/2012-feb-1-merged-model-proposal">Merged Model Proposal</a>"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 (<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>).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 ... "

@@ Line 24: / Line 24: @@
 * Provide a more abstract model which can simplify the application of SPDX to some of the more complex use cases ... "
-== [[Technical_Team/Proposals/2012-02-01/Usage_Relationship_Proposal|Usage Relationship Proposal]]
+== [[Technical_Team/Proposals/2012-02-01/Usage_Relationship_Proposal|Usage Relationship Proposal]] ==
 "Modification to the Merged Model Proposal to move the Usage property from the SPDXElement to the SPDXElementRelationship"
 [[Category:Technical]]

← Older revision		Revision as of 18:28, 21 November 2013
Line 24:		Line 24:
	* Provide a more abstract model which can simplify the application of SPDX to some of the more complex use cases ... "		* Provide a more abstract model which can simplify the application of SPDX to some of the more complex use cases ... "

		+	== [[Technical_Team/Proposals/2012-02-01/Usage_Relationship_Proposal\|Usage Relationship Proposal]]
		+
		+	"Modification to the Merged Model Proposal to move the Usage property from the SPDXElement to the SPDXElementRelationship"
	[[Category:Technical]]		[[Category:Technical]]

← Older revision		Revision as of 12:12, 7 March 2013
Line 1:		Line 1:
−	~~<p> </p><p>~~This page brings together various modelling proposals for 2.0 under a common page. The models currently under discusson are shown below with a brief excerpt from the page:~~</p><p> </p><p>1. <a title~~=~~"Rough Conceptual Model" href~~=~~"http:~~//~~spdx.org/wiki/yet-another-rough-proposal-conceptual-model-spdx-2%20">~~Rough Conceptual Model~~</a></p><p>~~"This conceptual model is an attempt to incrementally add hierarchy and provenance capabilities to the existing SPDX model. Many of the ~~<a href="http:~~//~~spdx~~.~~org/wiki/spdx-20-~~use-cases~~">use cases</a>~~ have been considered but further analysis is necessary to ensure that this model covers all scenarios. ..."~~</p><p> </p><p>2. <a title~~=~~"Supply Chain Model" href~~=~~"http:~~//~~spdx~~.~~org/wiki/rough-proposal-hierarchy-signing-and-supply-chain-friendliness-spdx-20">~~Provenance and Supply Chain Model ~~</a></p><p>~~" A desire has been expressed to be able to have SPDX be capable of expressing</~~p><ol><li><a href="http://spdx~~.~~org/wiki/sdpx-20-provenance">~~Provenance~~</a>~~ (we can know precisely who said what and when about a package)~~</li><li>~~Hiearchy and Aggregation ( package A contains packages B, C, etc)~~</li><li>~~How software flows through a supply chain (upstream to packager, through several intermediate vendors to consumer) ..."~~</li></ol><p> </p><p>3. <a title~~=~~"Merged Model Proposal" href~~=~~"http:~~/~~/www.spdx.org/wiki~~/2012-~~feb~~-~~1-merged-model-proposal">~~Merged Model Proposal~~</a></p><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 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> </p><p> </p><p> </p>~~	+	This page brings together various modelling proposals for 2.0 under a common page. The models currently under discusson are shown below with a brief excerpt from the page:
		+
		+	== [[Technical_Team/Proposals/Yet_another_rough_proposal_for_conceptual_model_of_SPDX_2\|Rough Conceptual Model]] ==
		+
		+	"This conceptual model is an attempt to incrementally add hierarchy and provenance capabilities to the existing SPDX model. Many of the [[Technical_Team/Use_Cases/2.0\|use cases]] have been considered but further analysis is necessary to ensure that this model covers all scenarios. ..."
		+
		+	== [[Technical_Team/Proposals/Rough_proposal_for_provenance,_hierarchy_and_aggregation,_and_supply_chain_friendliness_in_SPDX_2.0\|Provenance and Supply Chain Model]] ==
		+
		+	"A desire has been expressed to be able to have SPDX be capable of expressing
		+
		+	# [[Technical_Team/SDPX_2.0_Provenance\|Provenance]] (we can know precisely who said what and when about a package)
		+	# Hiearchy and Aggregation ( package A contains packages B, C, etc)
		+	# How software flows through a supply chain (upstream to packager, through several intermediate vendors to consumer) ..."
		+
		+	== [[Technical_Team/Proposals/2012-02-01/Merged_Model_Proposal\|Merged Model Proposal]] ==
		+
		+	"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 ... "
		+
		+	[[Category:Technical]]

← Older revision		Revision as of 19:13, 21 August 2012
Line 1:		Line 1:
−	<p> </p><p>This page brings together various modelling proposals for 2.0 under a common page. The models currently under discusson are shown below with a brief ~~exceprt~~ from the page:</p><p> </p><p>1. <a title="Rough Conceptual Model" href="http://spdx.org/wiki/yet-another-rough-proposal-conceptual-model-spdx-2%20">Rough Conceptual Model</a></p><p>"This conceptual model is an attempt to incrementally add hierarchy and provenance capabilities to the existing SPDX model. Many of the <a href="http://spdx.org/wiki/spdx-20-use-cases">use cases</a> have been considered but further analysis is necessary to ensure that this model covers all scenarios. ..."</p><p> </p><p>2. <a title="Supply Chain Model" href="http://spdx.org/wiki/rough-proposal-hierarchy-signing-and-supply-chain-friendliness-spdx-20">Provenance and Supply Chain Model </a></p><p>" A desire has been expressed to be able to have SPDX be capable of expressing</p><ol><li><a href="http://spdx.org/wiki/sdpx-20-provenance">Provenance</a> (we can know precisely who said what and when about a package)</li><li>Hiearchy and Aggregation ( package A contains packages B, C, etc)</li><li>How software flows through a supply chain (upstream to packager, through several intermediate vendors to consumer) ..."</li></ol><p> </p><p>3. <a title="Merged Model Proposal" href="http://www.spdx.org/wiki/2012-feb-1-merged-model-proposal">Merged Model Proposal</a></p><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 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> </p><p> </p><p> </p>	+	<p> </p><p>This page brings together various modelling proposals for 2.0 under a common page. The models currently under discusson are shown below with a brief excerpt from the page:</p><p> </p><p>1. <a title="Rough Conceptual Model" href="http://spdx.org/wiki/yet-another-rough-proposal-conceptual-model-spdx-2%20">Rough Conceptual Model</a></p><p>"This conceptual model is an attempt to incrementally add hierarchy and provenance capabilities to the existing SPDX model. Many of the <a href="http://spdx.org/wiki/spdx-20-use-cases">use cases</a> have been considered but further analysis is necessary to ensure that this model covers all scenarios. ..."</p><p> </p><p>2. <a title="Supply Chain Model" href="http://spdx.org/wiki/rough-proposal-hierarchy-signing-and-supply-chain-friendliness-spdx-20">Provenance and Supply Chain Model </a></p><p>" A desire has been expressed to be able to have SPDX be capable of expressing</p><ol><li><a href="http://spdx.org/wiki/sdpx-20-provenance">Provenance</a> (we can know precisely who said what and when about a package)</li><li>Hiearchy and Aggregation ( package A contains packages B, C, etc)</li><li>How software flows through a supply chain (upstream to packager, through several intermediate vendors to consumer) ..."</li></ol><p> </p><p>3. <a title="Merged Model Proposal" href="http://www.spdx.org/wiki/2012-feb-1-merged-model-proposal">Merged Model Proposal</a></p><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 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> </p><p> </p><p> </p>

← Older revision		Revision as of 19:12, 21 August 2012
Line 1:		Line 1:
−	<p> </p><p>3. This page brings together various modelling proposals for 2.0 under a common page.~~</p><p> </p><p>~~The models currently under discusson are:</p><p> </p><p>1. <a title="Rough Conceptual Model" href="http://spdx.org/wiki/yet-another-rough-proposal-conceptual-model-spdx-2%20">Rough Conceptual Model</a> </p><p>"This conceptual model is an attempt to incrementally add hierarchy and provenance capabilities to the existing SPDX model. Many of the <a href="http://spdx.org/wiki/spdx-20-use-cases">use cases</a> have been considered but further analysis is necessary to ensure that this model covers all scenarios. ..."</p><p> </p><p>2. <a title="Supply Chain Model" href="http://spdx.org/wiki/rough-proposal-hierarchy-signing-and-supply-chain-friendliness-spdx-20">Provenance and Supply Chain Model </a></p><p>" A desire has been expressed to be able to have SPDX be capable of expressing~~</p><p> </p><p> ~~</p><ol><li><a href="http://spdx.org/wiki/sdpx-20-provenance">Provenance</a> (we can know precisely who said what and when about a package)</li><li>Hiearchy and Aggregation ( package A contains packages B, C, etc)</li><li>How software flows through a supply chain (upstream to packager, through several intermediate vendors to consumer) ..."</li></ol><p> </p><p>3. <a title="Merged Model Proposal" href="http://www.spdx.org/wiki/2012-feb-1-merged-model-proposal">Merged Model Proposal</a></p><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 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> </p><p> </p><p> </p>	+	<p> </p><p>This page brings together various modelling proposals for 2.0 under a common page. The models currently under discusson are shown below with a brief exceprt from the page:</p><p> </p><p>1. <a title="Rough Conceptual Model" href="http://spdx.org/wiki/yet-another-rough-proposal-conceptual-model-spdx-2%20">Rough Conceptual Model</a></p><p>"This conceptual model is an attempt to incrementally add hierarchy and provenance capabilities to the existing SPDX model. Many of the <a href="http://spdx.org/wiki/spdx-20-use-cases">use cases</a> have been considered but further analysis is necessary to ensure that this model covers all scenarios. ..."</p><p> </p><p>2. <a title="Supply Chain Model" href="http://spdx.org/wiki/rough-proposal-hierarchy-signing-and-supply-chain-friendliness-spdx-20">Provenance and Supply Chain Model </a></p><p>" A desire has been expressed to be able to have SPDX be capable of expressing</p><ol><li><a href="http://spdx.org/wiki/sdpx-20-provenance">Provenance</a> (we can know precisely who said what and when about a package)</li><li>Hiearchy and Aggregation ( package A contains packages B, C, etc)</li><li>How software flows through a supply chain (upstream to packager, through several intermediate vendors to consumer) ..."</li></ol><p> </p><p>3. <a title="Merged Model Proposal" href="http://www.spdx.org/wiki/2012-feb-1-merged-model-proposal">Merged Model Proposal</a></p><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 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> </p><p> </p><p> </p>

← Older revision	Revision as of 17:59, 14 September 2012
(No difference)