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

Difference between revisions of "Technical Team/Proposals/2010-10-21/artifactOf"

From SPDX Wiki
Jump to: navigation, search
(Convert to MediaWiki syntax)
 
(5 intermediate revisions by one other user not shown)
Line 1: Line 1:
−
<h2>Status</h2><p>
+
Status: adopted
  
−
<strong>Open</strong>
+
Alternative to [[Technical_Team/Proposals/2010-10-21/File_origin]]
  
−
Alternative to <a href="http://www.spdx.org/wiki/proposal-2010-10-21-2-file-origin">Proposal 2010-10-21-1: File origin</a></p>
+
==Issue==
  
−
<h2>Issue</h2>
+
The origin of a file is an important fact that is not described by and spdx file.
  
−
<p>The origin of a file is an important fact that is not described by and spdx file.</p>
+
==Proposal==
  
−
<h2>Proposal</h2>
+
Define a property of File whose value is a DOAP Project. The DOAP Project will contain the project name and homepage URL when they are known. It also might also included more complete information regarding a project, if such information is known. For more information regarding DOAP see [http://en.wikipedia.org/wiki/Description_of_a_Project Wikipedia] and [http://schemapedia.com/schemas/doap Schemapedia]
  
−
<p>Define a property of File whose value is a DOAP Project. The DOAP Project will contain the project name and homepage URL when they are known.  It also might also included more complete information regarding a project, if such information is known.  For more information regarding DOAP see <a href="http://en.wikipedia.org/wiki/Description_of_a_Project">Wikipedia</a> and <a href="http://schemapedia.com/schemas/doap">Schemapedia</a> </p>
+
Multiple instances of this property are allowed because the exact origin of a file may be unclear. If a file was first created in a project A and then copied and modified in project B the file version of the file in project be would be an artifact of both projects A and B.
  
−
<p>Multiple instances of this property are allowed because the exact origin of a file may be unclear.  If a file was first created in a project A and then copied and modified in project B the file version of the file in project be would be an artifact of both projects A and B.</p>
+
==Additions to spec==
−
 
+
−
<h3>Additions to spec</h3><p>
+
  
 
5.6 ArtifactOf
 
5.6 ArtifactOf
 +
 
5.6.1 Purpose: Identify the project(s) of which this file is a part.
 
5.6.1 Purpose: Identify the project(s) of which this file is a part.
 +
 
5.6.2 Intent: By providing data regarding the project(s) where this file originated or occurs the reader can better identify the source and use it to do further research if needed.
 
5.6.2 Intent: By providing data regarding the project(s) where this file originated or occurs the reader can better identify the source and use it to do further research if needed.
 +
 
5.6.3 Cardinality: Optional, 0 or more.
 
5.6.3 Cardinality: Optional, 0 or more.
 +
 
5.6.4 Tag: "ArtifactOf"
 
5.6.4 Tag: "ArtifactOf"
 +
 
5.6.5 RDF: /RDF/SPDXDoc/Describes/File/ArtifactOf
 
5.6.5 RDF: /RDF/SPDXDoc/Describes/File/ArtifactOf
 +
 
5.6.6 Data Format:
 
5.6.6 Data Format:
−
</p>
 
  
−
<p>The value of this property is a doap:Project. For the RDF/XML format it may be any valid doap:Project resource, including a URI reference. For the tag value format project information is limited to name and homepage. These tags are are semantically equivalent to doap:name and doap:homepage properties, respectively. Either name or homepage may be omitted in the tag value format.</p>
+
The value of this property is a doap:Project. For the RDF/XML format it may be any valid doap:Project resource, including a URI reference. For the tag value format project information is limited to name and homepage. These tags are are semantically equivalent to doap:name and doap:homepage properties, respectively. Either name or homepage may be omitted in the tag value format.
 +
 
 +
5.6.7 Example:
 +
 
 +
    ArtifactOf.name: JUnit
 +
    ArtifactOf.homepage: http://www.junit.org
  
−
<p>5.6.7 Example:
+
[[Category:Technical]]
−
</p><p>&nbsp;</p>
+
−
<pre>        ArtifactOf: Project(name: JUnit<br />                            homepage: http://www.junit.org)<br /></pre>
+

Latest revision as of 11:48, 7 March 2013

Status: adopted

Alternative to Technical_Team/Proposals/2010-10-21/File_origin

Issue

The origin of a file is an important fact that is not described by and spdx file.

Proposal

Define a property of File whose value is a DOAP Project. The DOAP Project will contain the project name and homepage URL when they are known. It also might also included more complete information regarding a project, if such information is known. For more information regarding DOAP see Wikipedia and Schemapedia

Multiple instances of this property are allowed because the exact origin of a file may be unclear. If a file was first created in a project A and then copied and modified in project B the file version of the file in project be would be an artifact of both projects A and B.

Additions to spec

5.6 ArtifactOf

5.6.1 Purpose: Identify the project(s) of which this file is a part.

5.6.2 Intent: By providing data regarding the project(s) where this file originated or occurs the reader can better identify the source and use it to do further research if needed.

5.6.3 Cardinality: Optional, 0 or more.

5.6.4 Tag: "ArtifactOf"

5.6.5 RDF: /RDF/SPDXDoc/Describes/File/ArtifactOf

5.6.6 Data Format:

The value of this property is a doap:Project. For the RDF/XML format it may be any valid doap:Project resource, including a URI reference. For the tag value format project information is limited to name and homepage. These tags are are semantically equivalent to doap:name and doap:homepage properties, respectively. Either name or homepage may be omitted in the tag value format.

5.6.7 Example: 

   ArtifactOf.name: JUnit
   ArtifactOf.homepage: http://www.junit.org
Retrieved from "https://wiki.spdx.org/index.php?title=Technical_Team/Proposals/2010-10-21/artifactOf&oldid=607"