Annotation Property: comment
http://www.w3.org/2000/01/rdf-schema#comment
Usage (137)
-
http://spdx.org/rdf/terms#Annotationcomment "An Annotation is a comment on an SpdxItem by an agent." (en)
-
http://spdx.org/rdf/terms#AnyLicenseInfocomment "The AnyLicenseInfo class includes all resources that represent licensing information." ()
-
http://spdx.org/rdf/terms#Checksumcomment "A Checksum is value that allows the contents of a file to be authenticated. Even small changes to the content of the file will change its checksum. This class allows the results of a variety of checksum and cryptographic message digest algorithms to be represented.
" (en)
-
http://spdx.org/rdf/terms#ConjunctiveLicenseSetcomment "A ConjunctiveLicenseSet represents a set of licensing information all of which apply." (en)
-
http://spdx.org/rdf/terms#CreationInfocomment "A CreationInfo provides information about the individuals, organizations and tools involved in the creation of an SpdxDocument." (en)
-
http://spdx.org/rdf/terms#DisjunctiveLicenseSetcomment "A DisjunctiveLicenseSet represents a set of licensing information where only one license applies at a time. This class implies that the recipient gets to choose one of these licenses they would prefer to use." (en)
-
http://spdx.org/rdf/terms#ExternalDocumentRefcomment "Purpose: Identify any external SPDX documents referenced within this SPDX document.
Intent: SPDX elements may be related to other SPDX elements. These elements may be in external SPDX documents. An SPDX element could be a file, package, or SPDX document." (en)
-
http://spdx.org/rdf/terms#ExtractedLicenseInfocomment "An ExtractedLicensingInfo represents a license or licensing notice that was found in the package. Any license text that is recognized as a license may be represented as a License rather than an ExtractedLicensingInfo." (en)
-
http://spdx.org/rdf/terms#Filecomment "A File represents a named sequence of information that is contained in a software package." (en)
-
http://spdx.org/rdf/terms#Licensecomment "A License represents a copyright license. The SPDX license list website is annotated with these properties (using RDFa) to allow license data published there to be easily processed.
The license list is populated in accordance with the License List fields guidelines. These guidelines are not normative and may change over time. SPDX tooling should not rely on values in the license list conforming to the current guidelines." (en)
-
http://spdx.org/rdf/terms#LicenseExceptioncomment "An exception to a license." (en)
-
http://spdx.org/rdf/terms#ListedLicensecomment "A license which is included in the SPDX License List (http://spdx.org/licenses)." (en)
-
http://spdx.org/rdf/terms#OrLaterOperatorcomment "A license with an or later operator indicating this license version or any later version of the license (e.g. GPL-2.0+)" (en)
-
http://spdx.org/rdf/terms#Packagecomment "A Package represents a collection of software files that are delivered as a single functional component.
A package can contain sub-packages, but the information in this class is a reference to the entire contents of the package listed." (en)
-
http://spdx.org/rdf/terms#PackageVerificationCodecomment "A manifest based verification code (the algorithm is defined in section 4.7 of the full specification) of the SPDX Item. This allows consumers of this data and/or database to determine if an SPDX item they have in hand is identical to the SPDX item from which the data was produced. This algorithm works even if the SPDX document is included in the SPDX item." (en)
-
http://spdx.org/rdf/terms#Relationshipcomment "Purpose: This class provides information about the relationship between two
SPDX elements. For example, you can represent a relationship between two different Files, between a Package and a File, between two Packages, or between one SPDXDocument and another SPDXDocument." (en)
-
http://spdx.org/rdf/terms#Reviewcomment "A Review represents an audit and signoff by an individual, organization or tool on the information in an SpdxDocument." (en)
-
http://spdx.org/rdf/terms#SimpleLicenseingInfocomment "The SimpleLicenseInfo class includes all resources that represent simple, atomic, licensing information." (en)
-
http://spdx.org/rdf/terms#Snippetcomment "The set of bytes in a file. The name of the snippet is the name of the file appended with the byte range in parenthesis (ie: “./file/name(2145:5532)”)" (en)
-
http://spdx.org/rdf/terms#SpdxDocumentcomment "An SpdxDocument is a summary of the contents, provenance, ownership and licensing analysis of a specific software package. This is, effectively, the top level of SPDX information." (en)
-
http://spdx.org/rdf/terms#SpdxElementcomment "An SpdxElement is any thing described in SPDX, either a document or an SpdxItem. SpdxElements can be related to other SpdxElements." ()
-
http://spdx.org/rdf/terms#SpdxItemcomment "An SpdxItem is a potentially copyrightable work." (en)
-
http://spdx.org/rdf/terms#WithExceptionOperatorcomment "Sometimes a set of license terms apply except under special circumstances. In this case, use the binary “WITH” operator to construct a new <SPDX-License-Expression> to represent the special exception situation. A valid license expression is where the left operand is a valid <SPDX-License-Expression> value and the right operand is an SPDX License List Exception Identifier (SPDX LL Exception Identifier) that represents the special exception terms. SPDX License LL Identifiers can be found on the SPDX License List. The syntax for the “WITH” operator is:
<SPDX-License-Expression-2> = (<SPDX-License-Expression-1> WITH <SPDX-LL-Exception-Identifier>)
For example, when the Bison exception is to be applied to GPL-2.0+, the expression would be:
(GPL-2.0+ WITH Bison-exception-2.2), where:
<SPDX-License-Expression-1> = GPL-2.0+
<SPDX-LL-Exception-Identifier> = Bison-exception-2.2
<SPDX-License-Expression-1> = (GPL-2.0+ WITH Bison-exception-2.2)
If the applicable exception is not found on the SPDX License List, then use LicenseRef-[idString] to express the license and exception." (en)
-
http://spdx.org/rdf/terms#agentcomment "Agent (eg. person, group, software or physical artifact).." (en)
-
http://spdx.org/rdf/terms#algorithmcomment "Identifies the algorithm used to produce the subject Checksum.
Currently, SHA-1 is the only supported algorithm. It is anticipated that other algorithms will be supported at a later time.
" (en)
-
http://spdx.org/rdf/terms#annotationcomment "Provide additional information about an SpdxElement.
" (en)
-
http://spdx.org/rdf/terms#annotationTypecomment "This field describes the type of annotation." (en)
-
http://spdx.org/rdf/terms#annotationType_othercomment "Type of annotation which does not fit in any of the pre-defined annotation types." (en)
-
http://spdx.org/rdf/terms#annotationType_reviewcomment "A Review represents an audit and signoff by an individual, organization or tool on the information for an SpdxElement." (en)
-
http://spdx.org/rdf/terms#annotatorcomment "This field identifies the person, organization or tool that has commented on a file, package, or entire document. " (en)
-
http://spdx.org/rdf/terms#artifactOfcomment "Indicates the project in which the SpdxElement originated.
Tools must preserve doap:homepage and doap:name properties and the URI (if one is known) of doap:Project resources that are values of this property. All other properties of doap:Projects are not directly supported by SPDX and may be dropped when translating to or from some SPDX formats." (en)
-
http://spdx.org/rdf/terms#byteRangecomment "String of the form \d+:\d+ denoting a range of bytes." (en)
-
http://spdx.org/rdf/terms#checksumcomment "The checksum property provides a mechanism that can be used to verify that the contents of a File or Package have not changed." (en)
-
http://spdx.org/rdf/terms#checksumAlgorithm_sha1comment "Indicates the algorithm used was SHA-1" ()
-
http://spdx.org/rdf/terms#checksumValuecomment "The checksumValue property provides a lower case hexidecimal encoded digest value produced using a specific algorithm." ()
-
http://spdx.org/rdf/terms#copyrightTextcomment " Identify the copyright holders of the package, as well as any dates present. This will be a free form text field extracted from package information files. The options to populate this field are limited to:
(a) any text related to a copyright notice, even if not complete;
(b) NONE if the package contains no copyright information whatsoever; or
(c) NOASSERTION, if the SPDX file creator has not examined the contents the package or if the SPDX file creator has intentionally provided no information (no meaning should be implied by doing so).
" ()
-
http://spdx.org/rdf/terms#createdcomment "Identify when the SPDX file was originally created. The date is to be specified according to combined date and time in UTC format as specified in ISO 8601 standard. This field is distinct from the fields in section 7, which involves the addition of information during a subsequent review." ()
-
http://spdx.org/rdf/terms#creationInfocomment "The creationInfo property relates an SpdxDocument to a set of information about the creation of the SpdxDocument." (en)
-
http://spdx.org/rdf/terms#creatorcomment "Identify who (or what, in the case of a tool) created the SPDX file. If the SPDX file was created by an individual, indicate the person's name. If the SPDX file was created on behalf of a company or organization, indicate the entity name. If the SPDX file was created using a software tool, indicate the name and version for that tool. If multiple participants or tools were involved, use multiple instances of this field. Person name or organization name may be designated as “anonymous” if appropriate." (en)
-
http://spdx.org/rdf/terms#dataLicensecomment "Compliance with the SPDX specification includes populating the SPDX fields therein with data related to such fields ("SPDX-Metadata"). The SPDX specification contains numerous fields where an SPDX document creator may provide relevant explanatory text in SPDX-Metadata.
Without opining on the lawfulness of "database rights" (in jurisdictions where applicable), such explanatory text is copyrightable subject matter in most Berne Convention countries.
By using the SPDX specification, or any portion hereof, you hereby agree that any copyright rights (as determined by your jurisdiction) in any SPDX-Metadata, including without limitation explanatory text, shall be subject to the terms of the Creative Commons CC0 1.0 Universal license. For SPDX-Metadata not containing any copyright rights, you hereby agree and acknowledge that the SPDX-Metadata is provided to you "as-is" and without any representations or warranties of any kind concerning the SPDX-Metadata, express, implied, statutory or otherwise, including without limitation warranties of title, merchantability, fitness for a particular purpose, non-infringement, or the absence of latent or other defects, accuracy, or the presence or absence of errors, whether or not discoverable, all to the greatest extent permissible under applicable law." (en)
-
http://spdx.org/rdf/terms#datecomment "A date-time stamp." (en)
-
http://spdx.org/rdf/terms#describesFilecomment "The describesFile property relates an SpdxDocument to the file which it describes." (en)
-
http://spdx.org/rdf/terms#describesPackagecomment "The describesPackage property relates an SpdxDocument to the package which it describes." (en)
-
http://spdx.org/rdf/terms#descriptioncomment "This field is a more detailed description of the package. It may also be extracted from the packages itself.
" (en)
-
http://spdx.org/rdf/terms#downloadLocationcomment "This section identifies the download Universal Resource Locator (URL), or a specific location within a version control system (VCS) for the package at the time that the SPDX file was created. If there is no public (or internal) URL, then it is explicitly marked as NONE. If there is insufficient knowledge about whether a public or internal download mechanism exists or not, then NOASSERTION should be used.
Data Format: uniform resource locator | VCS location | “NONE” | “NOASSERTION”
For version-controlled files, the VCS location syntax is similar to a URL and has the:
<vcs_tool>+<transport>://<host_name>[/<path_to_repository>][@<revision_tag_or_branch>][#<sub_path>]
This VCS location compact notation (inspired and mostly adopted from https://pip.pypa.io/en/latest/reference/pip_install.html#vcs-support as of 20150220) supports referencing locations in version control systems such as Git, Mercurial, Subversion and Bazaar, and specifies the type of VCS tool using url prefixes: “git+”, “hg+”, “bzr+”, “svn+” and specific transport schemes such as SSH or HTTPS.
Specifying sub-paths, branch names, a commit hash, a revision or a tag name is recommended, and supported using the "@"delimiter for commits and the "#" delimiter for sub-paths.
Using user names and password in the host_name is not supported and should be considered as an error. User access control to URLs or VCS repositories must be handled outside of an SPDX document.
In VCS location compact notations, the trailing slashes in <host_name>, <path_to_repository> are not significant. Leading and trailing slashes in <sub_path> are not significant." (en)
-
http://spdx.org/rdf/terms#examplecomment "Text for examples in describing an SPDX element." (en)
-
http://spdx.org/rdf/terms#externalDocumentIdcomment "externalDocumentId is a string containing letters, numbers, “.”, “-” or “+” which uniquely identifies an external document within this document.
" (en)
-
http://spdx.org/rdf/terms#externalDocumentRefcomment "Any external SPDX documents referenced within an SPDX document. This property is primarily used to verify the external SPDX document reference through use of the checksum." (en)
-
http://spdx.org/rdf/terms#extractedTextcomment "Purpose: Provide a copy of the actual text of the license reference extracted from the package or file that is associated with the License Identifier Assigned to aid in future analysis.
" (en)
-
http://spdx.org/rdf/terms#fileContributorcomment "This field provides a place for the SPDX file creator to record file contributors. Contributors could include names of copyright holders and/or authors who may not be copyright holders yet contributed to the file content." (en)
-
http://spdx.org/rdf/terms#fileNamecomment "The name of the file relative to the root of the package." (en)
-
http://spdx.org/rdf/terms#fileTypecomment "The type of the file." ()
-
http://spdx.org/rdf/terms#fileType_applicationcomment " The file is associated with a specific application type (MIME type of application/* )" (en)
-
http://spdx.org/rdf/terms#fileType_archivecomment "Indicates the file is an archive file." (en)
-
http://spdx.org/rdf/terms#fileType_audiocomment "The file is associated with an audio file (MIME type of audio/* , ie. .mp3 );
IMAGE if the file is assoicated with an picture image file (MIME type of image/*, ie. .jpg, .gif )" (en)
-
http://spdx.org/rdf/terms#fileType_binarycomment "Indicates the file is not a text file. spdx:filetype_archive is preferred for archive files even though they are binary." (en)
-
http://spdx.org/rdf/terms#fileType_documentationcomment "The file serves as documentation." (en)
-
http://spdx.org/rdf/terms#fileType_imagecomment "The file is assoicated with an picture image file (MIME type of image/*, ie. .jpg, .gif )." (en)
-
http://spdx.org/rdf/terms#fileType_othercomment "Indicates the file is not a source, archive or binary file." (en)
-
http://spdx.org/rdf/terms#fileType_sourcecomment "Indicates the file is a source code file." (en)
-
http://spdx.org/rdf/terms#fileType_spdxcomment "The file is an SPDX document." (en)
-
http://spdx.org/rdf/terms#fileType_textcomment "The file is human readable text file (MIME type of text/*)." (en)
-
http://spdx.org/rdf/terms#fileType_videocomment "The file is associated with a video file type (MIME type of video/*)." (en)
-
http://spdx.org/rdf/terms#fromFilecomment "File containing the SPDX element (e.g. the file contaning a snippet)." (en)
-
http://spdx.org/rdf/terms#hasExtractedLicensingInfocomment "Indicates that a particular ExtractedLicensingInfo was defined in the subject SpdxDocument.
" (en)
-
http://spdx.org/rdf/terms#hasFilecomment "Indicates that a particular file belongs to a package." (en)
-
http://spdx.org/rdf/terms#isOsiApprovedcomment "Indicates if the OSI has approved the license." (en)
-
http://spdx.org/rdf/terms#licenseCommentscomment "This field provides a place for the SPDX file creator to record any relevant background information or analysis that went in to arriving at the Concluded License for an SPDX item. If the Concluded License does not match the Declared License or License Information from Files, this should be explained by the SPDX file creator. Its is also preferable to include an explanation here when the Concluded License is NOASSERTION.
" (en)
-
http://spdx.org/rdf/terms#licenseConcludedcomment "This field contains the license the SPDX file creator has concluded as governing the SPDX item or alternative values, if the governing license cannot be determined. The options to populate this field are limited to:
(a) the SPDX License List short form identifier, if the Concluded License is on the SPDX License List;
(b) a reference to the license text denoted by the LicenseRef-[idString], if the Concluded License is not on the SPDX License List;
(c) NOASSERTION should be used if:
(i) the SPDX file creator has attempted to but cannot reach a reasonable objective determination of the Concluded License;
(ii) the SPDX file creator is uncomfortable concluding a license, despite some license information being available;
(iii) the SPDX file creator has made no attempt to determine a Concluded License;
(iv) the SPDX file creator has intentionally provided no information (no meaning should be implied by doing so); or
(v) there is no licensing information from which to conclude a license for the package.
With respect to (a) and (b) above, if there is more than one Concluded License, all should be included. If the package recipient has a choice of multiple licenses, then each of the choices should be recited as a "disjunctive" license. If the Concluded License is not the same as the Declared License, a written explanation should be provided in the Comments on License field (section 3.15). With respect to (c), a written explanation in the Comments on License field (section 3.15) is preferred.
" (en)
-
http://spdx.org/rdf/terms#licenseDeclaredcomment "This field lists the licenses that have been declared by the authors of the package. Any license information that does not originate from the package authors, e.g. license information from a third party repository, should not be included in this field. The options to populate this field are limited to:
(a) the SPDX License List short form identifier, if the license is on the SPDX License List;
(b) a reference to the license, denoted by LicenseRef-[idString], if the Declared License is not on the SPDX License List;
(c) NONE, if no license information is detected in any of the files; or
(d) NOASSERTION, if the SPDX file creator has not examined the contents of the package or if the SPDX file creator has intentionally provided no information (no meaning should be implied by doing so).
With respect to “a” and “b” above, if license information for more than one license is contained in the file, all should be reflected in this field. If the license information offers the package recipient a choice of licenses, then each of the choices should be recited as "disjunctive" licenses.
" (en)
-
http://spdx.org/rdf/terms#licenseExceptioncomment "An exception to a license." (en)
-
http://spdx.org/rdf/terms#licenseExceptionIdcomment "A human readable short form license exception identifier for a license. The license ID is iether on the standard license oist or the form "LicenseRef-"[idString] where [idString] is a unique string containing letters, numbers, ".", "-" or "+"." (en)
-
http://spdx.org/rdf/terms#licenseExceptionTextcomment "Full text of the license exception." (en)
-
http://spdx.org/rdf/terms#licenseIdcomment "A human readable short form license identifier for a license. The license ID is iether on the standard license oist or the form "LicenseRef-"[idString] where [idString] is a unique string containing letters, numbers, ".", "-" or "+"." (en)
-
http://spdx.org/rdf/terms#licenseInfoFromFilescomment "This field is to contain a list of all licenses found in the package. The relationship between licenses (i.e., conjunctive, disjunctive) is not specified in this field – it is simply a listing of all licenses found. The options to populate this list are limited to:
(a) the SPDX License List short form identifier, if a detected license is on the SPDX License List;
(b) a reference to the license, denoted by LicenseRef-[idString], if the detected license is not on the SPDX License List;
(c) NONE, if no license information is detected in any of the files; or
(d) NOASSERTION, if the SPDX file creator has not examined the contents of the actual files or if the SPDX file creator has intentionally provided no information (no meaning should be implied by doing so)." (en)
-
http://spdx.org/rdf/terms#licenseInfoInFilecomment "Licensing information that was discovered directly in the subject file. This is also considered a declared license for the file." (en)
-
http://spdx.org/rdf/terms#licenseListVersioncomment "An optional field for creators of the SPDX file to provide the version of the SPDX License List used when the SPDX file was created." (en)
-
http://spdx.org/rdf/terms#licenseTextcomment "Full text of the license." (en)
-
http://spdx.org/rdf/terms#membercomment "A license, or other licensing information, that is a member of the subject license set." (en)
-
http://spdx.org/rdf/terms#namecomment "The full human readable name of the item. " (en)
-
http://spdx.org/rdf/terms#noassertioncomment "Indicates that the preparer of the SPDX document is not making any assertion regarding the value of this field." ()
-
http://spdx.org/rdf/terms#nonecomment "When this value is used as the object of a property it indicates that the preparer of the SpdxDocument believes that there is no value for the property. This value should only be used if there is sufficient evidence to support this assertion." ()
-
http://spdx.org/rdf/terms#noticeTextcomment "This field provides a place for the SPDX file creator to record potential legal notices found in the file. This may or may not include copyright statements." (en)
-
http://spdx.org/rdf/terms#originatorcomment "If the package identified in the SPDX file originated from a different person or organization than identified as Package Supplier (see section 3.5 above), this field identifies from where or whom the package originally came. In some cases a package may be created and originally distributed by a different third party than the Package Supplier of the package. For example, the SPDX file identifies the package glibc and Red Hat as the Package Supplier, but Free Software Foundation is the Package Originator.
NOASSERTION should be used if:
(i) the SPDX file creator has attempted to but cannot reach a reasonable objective determination of who the originator is;
(ii) the project is orphaned and was obtained from a public website; or
(iii) the SPDX file creator has intentionally provided no information (no meaning should be implied by doing so)." (en)
-
http://spdx.org/rdf/terms#packageFileNamecomment "Provide the actual file name of the package, or path of the directory being treated as a package. This may include the packaging and compression methods used as part of the file name, if appropriate.
" (en)
-
http://spdx.org/rdf/terms#packageVerificationCodecomment "This field provides an independently reproducible mechanism identifying specific contents of a package based on the actual files (except the SPDX file itself, if it is included in the package) that make up each package and that correlates to the data in this SPDX file. This identifier enables a recipient to determine if any file in the original package (that the analysis was done on) has been changed and permits inclusion of an SPDX file as part of a package.
Algorithm:
verificationcode = 0
filelist = templist = “”
for all files in the package {
if file is an “excludes” file, skip it /* exclude SPDX analysis file(s) */
append templist with “SHA1(file)/n”
}
sort templist in ascending order by SHA1 value
filelist = templist with "/n"s removed. /* ordered sequence of SHA1 values with no separators */
verificationcode = SHA1(filelist)
Where SHA1(file) applies a SHA1 algorithm on the contents of file and returns the result in lowercase hexadecimal digits.
Required sort order: '0','1','2','3','4','5','6','7','8','9','a','b','c','d','e','f' (ASCII order)" (en)
-
http://spdx.org/rdf/terms#packageVerificationCodeValuecomment "The actual package verification code as a hex encoded value." (en)
-
http://spdx.org/rdf/terms#referencesFilecomment "Indicates that a particular file belongs as part of the set of analyzed files in the SpdxDocument." (en)
-
http://spdx.org/rdf/terms#relatedSpdxElementcomment "A related SpdxElement." (en)
-
http://spdx.org/rdf/terms#relationshipcomment "Defines a relationship between two SPDX elements. The SPDX element may be a Package, File, or SpdxDocument." (en)
-
http://spdx.org/rdf/terms#relationshipTypecomment "Describes the type of relationship between two SPDX elements." (en)
-
http://spdx.org/rdf/terms#relationshipType_amendscomment "Is to be used when (current) SPDXRef-DOCUMENT amends the SPDX information in SPDXRef-B." (en)
-
http://spdx.org/rdf/terms#relationshipType_ancestorOfcomment "Is to be used when SPDXRef-A is an ancestor (same lineage but pre-dates) SPDXRef-B." (en)
-
http://spdx.org/rdf/terms#relationshipType_buildToolOfcomment "To be used when SPDXRef-A is used to to build SPDXRef-B." (en)
-
http://spdx.org/rdf/terms#relationshipType_containedBycomment "Is to be used when SPDXRef-A is contained by SPDXRef-B.
" (en)
-
http://spdx.org/rdf/terms#relationshipType_containscomment "Is to be used when SPDXRef-A contains SPDXRef-B.
" (en)
-
http://spdx.org/rdf/terms#relationshipType_copyOfcomment "Is to be used when SPDXRef-A is an exact copy of SPDXRef-B.
" (en)
-
http://spdx.org/rdf/terms#relationshipType_dataFilecomment "Is to be used when SPDXRef-A is a data file used in SPDXRef-B.
" (en)
-
http://spdx.org/rdf/terms#relationshipType_descendantOfcomment "Is to be used when SPDXRef-A is a descendant of (same lineage but postdates) SPDXRef-B.
" (en)
-
http://spdx.org/rdf/terms#relationshipType_describedBycomment "Is to be used when SPDXRef-A is described by SPDXREF-Document
" (en)
-
http://spdx.org/rdf/terms#relationshipType_describescomment "Is to be used when SPDXRef-DOCUMENT describes SPDXRef-A." (en)
-
http://spdx.org/rdf/terms#relationshipType_distributionArtifactcomment "Is to be used when distributing SPDXRef-A requires that SPDXRef-B also be distributed.
" (en)
-
http://spdx.org/rdf/terms#relationshipType_documentationcomment "To be used when SPDXRef-A provides documentation of SPDXRef-B." (en)
-
http://spdx.org/rdf/terms#relationshipType_dynamicLinkcomment "Is to be used when SPDXRef-A dynamically links to SPDXRef-B." (en)
-
http://spdx.org/rdf/terms#relationshipType_expandedFromArchivecomment "Is to be used when SPDXRef-A is expanded from the archive SPDXRef-B.
" (en)
-
http://spdx.org/rdf/terms#relationshipType_fileAddedcomment "Is to be used when SPDXRef-A is a file added to SPDXRef-B.
" (en)
-
http://spdx.org/rdf/terms#relationshipType_fileDeletedcomment "Is to be used when SPDXRef-A is a file was deleted from to SPDXRef-B.
" (en)
-
http://spdx.org/rdf/terms#relationshipType_fileModifiedcomment "Is to be used when SPDXRef-A is a file that was modified from SPDXRef-B.
" (en)
-
http://spdx.org/rdf/terms#relationshipType_generatedFromcomment "Is to be used when SPDXRef-A was generated from SPDXRef-B.
" (en)
-
http://spdx.org/rdf/terms#relationshipType_generatescomment "Is to be used when SPDXRef-A generates the SPDXRef-B.
" (en)
-
http://spdx.org/rdf/terms#relationshipType_hasPrerequisitecomment "Is to be used when SPDXRef-A has as a prerequisite SPDXRef-B." (en)
-
http://spdx.org/rdf/terms#relationshipType_metafileOfcomment "To be used when SPDXRef-A is a metafile of SPDXRef-B." (en)
-
http://spdx.org/rdf/terms#relationshipType_optionalComponentOfcomment "To be used when SPDXRef-A is an optional component of SPDXRef-B." (en)
-
http://spdx.org/rdf/terms#relationshipType_othercomment "to be used for a relationship which has not been defined in the formal SPDX specification. A description of the relationship should be included in the Relationship comments field." (en)
-
http://spdx.org/rdf/terms#relationshipType_packageOfcomment "To be used when SPDXRef-A is used as a package as part of SPDXRef-B." (en)
-
http://spdx.org/rdf/terms#relationshipType_patchAppliedcomment "Is to be used when SPDXRef-A is a patch file that has been applied to SPDXRef-B.
" (en)
-
http://spdx.org/rdf/terms#relationshipType_patchForcomment "Is to be used when SPDXRef-A is a patch file for (to be applied to) SPDXRef-B.
" (en)
-
http://spdx.org/rdf/terms#relationshipType_prerequisiteForcomment "Is to be used when SPDXRef-A is a prerequisite for SPDXRef-B" (en)
-
http://spdx.org/rdf/terms#relationshipType_staticLinkcomment "Is to be used when SPDXRef-A statically links to SPDXRef-B." (en)
-
http://spdx.org/rdf/terms#relationshipType_testcaseOfcomment "Is to be used when SPDXRef-A is a test case used in testing SPDXRef-B." (en)
-
http://spdx.org/rdf/terms#relationshipType_variantOfcomment "Is to be used when SPDXRef-A is a variant of (same lineage but not clear which came first) SPDXRef-B.
" (en)
-
http://spdx.org/rdf/terms#reviewDatecomment "The date and time at which the SpdxDocument was reviewed. This value must be in UTC and have 'Z' as its timezone indicator." (en)
-
http://spdx.org/rdf/terms#reviewedcomment "The review property relates a SpdxDocument to the review history." (en)
-
http://spdx.org/rdf/terms#reviewercomment "The name and, optionally, contact information of the person who performed the review.
Values of this property must conform to the agent and tool syntax." (en)
-
http://spdx.org/rdf/terms#sourceInfocomment "This field provides a place for the SPDX file creator to record any relevant background information or additional comments about the origin of the package. For example, this field might include comments indicating whether the package was pulled from a source code management system or has been repackaged.
" (en)
-
http://spdx.org/rdf/terms#spdxDocumentcomment "A propoerty containing an SPDX document." (en)
-
http://spdx.org/rdf/terms#specVersioncomment " Provide a reference number that can be used to understand how to parse and interpret the rest of the file. It will enable both future changes to the specification and to support backward compatibility. The version number consists of a major and minor version indicator. The major field will be incremented when incompatible changes between versions are made (one or more sections are created, modified or deleted). The minor field will be incremented when backwards compatible changes are made." (en)
-
http://spdx.org/rdf/terms#standardLicenseHeadercomment "License author's preferred text to indicated that a file is covered by the license." (en)
-
http://spdx.org/rdf/terms#standardLicenseTemplatecomment "License template which describes sections of the license which can be varied. See License Template section of the specification for format information." (en)
-
http://spdx.org/rdf/terms#summarycomment "This field is a short description of the package." (en)
-
http://spdx.org/rdf/terms#suppliercomment "Identify the actual distribution source for the package/directory identified in the SPDX file. This may or may not be different from the originating distribution source for the package. The name of the Package Supplier must be an organization or recognized author and not a web site. For example, Sourceforge is a host website, not a supplier, the supplier for http://sourceforge.net/projects/bridge/ is "The Linux Foundation."
NOASSERTION should be used if:
(i) the SPDX file creator has attempted to but cannot reach a reasonable objective determination of who the supplier is;
(ii) the project is orphaned and was obtained from a public website; or
(iii) the SPDX file creator has intentionally provided no information (no meaning should be implied by doing so). " (en)
-
http://spdx.org/rdf/terms#usedBycomment "Describes how the related relatedSpdxElement is used by this SpdxElement." (en)
-
http://spdx.org/rdf/terms#verificationCodeExcludedFilecomment "A file that was excluded when calculating the package verification code. This is usually a file containing SPDX data regarding the package. If a package contains more than one SPDX file all SPDX files must be excluded from the package verification code. If this is not done it would be impossible to correctly calculate the verification codes in both files." (en)
-
http://spdx.org/rdf/terms#versionInfocomment "Identify the version of the package." (en)
-
http://usefulinc.com/ns/doap#homepagecomment "This field provides a place for the SPDX file creator to record a web site that serves as the package's home page. This link can also be used to reference further information about the package referenced by the SPDX file creator.
" (en)
-
http://www.w3.org/2000/01/rdf-schema#seeAlsocomment "rdfs:seeAlso is an instance of rdf:Property that is used to indicate a resource that might provide additional information about the subject resource." (en)
-
http://www.w3.org/2003/06/sw-vocab-status/ns#term_statuscomment "The AnyLicenseInfo class includes all resources that represent licensing information." ()