Skip to content

Commit b2c5ca5

Browse files
committed
docs
Signed-off-by: Jan Kowalleck <[email protected]>
1 parent 09a8717 commit b2c5ca5

File tree

3 files changed

+4
-2
lines changed

3 files changed

+4
-2
lines changed

schema/bom-1.7.proto

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -423,6 +423,7 @@ message LicenseExpressionDetailed {
423423

424424
// Specifies the details and attributes related to a software license identifier.
425425
// (An SPDX expression may be a compound of license identifiers.)
426+
// The field `license_identifier` serves as the key which identifies each record. The key is not meant to be unique, as one and the same license identifier could apply to multiple, different but similar license details, texts, etc.
426427
message ExpressionDetails {
427428
// A valid SPDX license identifier. Refer to https://spdx.org/specifications for syntax requirements.
428429
// This field serves as the primary key, which uniquely identifies each record.
@@ -446,7 +447,7 @@ message LicenseExpressionDetailed {
446447
optional string bom_ref = 2;
447448
// Declared licenses and concluded licenses represent two different stages in the licensing process within software development. Declared licenses refer to the initial intention of the software authors regarding the licensing terms under which their code is released. On the other hand, concluded licenses are the result of a comprehensive analysis of the project's codebase to identify and confirm the actual licenses of the components used, which may differ from the initially declared licenses. While declared licenses provide an upfront indication of the licensing intentions, concluded licenses offer a more thorough understanding of the actual licensing within a project, facilitating proper compliance and risk management. Observed licenses are defined in `@.evidence.licenses`. Observed licenses form the evidence necessary to substantiate a concluded license.
448449
optional LicenseAcknowledgementEnumeration acknowledgement = 3;
449-
// Details for parts of the `expression`. The field `details.license_identifier` serves as the primary key, which uniquely identifies each record.
450+
// Details for parts of the `expression`.
450451
repeated ExpressionDetails details = 4;
451452
}
452453

schema/bom-1.7.schema.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1500,7 +1500,7 @@
15001500
"type": "array",
15011501
"items": {
15021502
"type": "object",
1503-
"description": "Specifies the details and attributes related to a software license identifier.\n(An SPDX expression may be a compound of license identifiers.)",
1503+
"description": "Specifies the details and attributes related to a software license identifier.\n(An SPDX expression may be a compound of license identifiers.)\nThe property `licenseIdentifier` serves as the key which identifies each record. The key is not meant to be unique, as one and the same license identifier could apply to multiple, different but similar license details, texts, etc.",
15041504
"required": [
15051505
"licenseIdentifier"
15061506
],

schema/bom-1.7.xsd

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1000,6 +1000,7 @@ limitations under the License.
10001000
<xs:documentation>
10011001
Specifies the details and attributes related to a software license identifier.
10021002
(An SPDX expression may be a compound of license identifiers.)
1003+
The attribute `license-identifier` serves as the key which identifies each record. The key is not meant to be unique, as one and the same license identifier could apply to multiple, different but similar license details, texts, etc.
10031004
</xs:documentation>
10041005
</xs:annotation>
10051006
<xs:sequence>

0 commit comments

Comments
 (0)