You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: schema/bom-1.5.proto
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ message Bom {
29
29
repeatedExternalReferenceexternal_references=7;
30
30
// Provides the ability to document dependency relationships.
31
31
repeatedDependencydependencies=8;
32
-
// Provides the ability to document aggregate completeness
32
+
// Compositions describe constituent parts (including components, services, and dependency relationships) and their completeness. Other inventory types such as vulnerabilities may also be described for completeness.
33
33
repeatedCompositioncompositions=9;
34
34
// Vulnerabilities identified in components or services.
35
35
repeatedVulnerabilityvulnerabilities=10;
@@ -568,11 +568,11 @@ enum Aggregate {
568
568
}
569
569
570
570
messageComposition {
571
-
// Indicates the aggregate completeness
571
+
// Specifies an aggregate type that describe how complete a relationship is.
572
572
Aggregateaggregate=1;
573
-
// The assemblies the aggregate completeness applies to
573
+
// The bom-ref identifiers of the components or services being described. Assemblies refer to nested relationships whereby a constituent part may include other constituent parts. References do not cascade to child parts. References are explicit for the specified constituent part only. Other inventory types such as vulnerabilities may also be described.
574
574
repeatedstringassemblies=2;
575
-
// The dependencies the aggregate completeness applies to
575
+
// The bom-ref identifiers of the components or services being described. Dependencies refer to a relationship whereby an independent constituent part requires another independent constituent part. References do not cascade to transitive dependencies. References are explicit for the specified dependency only.
576
576
repeatedstringdependencies=3;
577
577
// An optional identifier which can be used to reference the composition elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.
Copy file name to clipboardExpand all lines: schema/bom-1.5.schema.json
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -87,7 +87,7 @@
87
87
"items": {"$ref": "#/definitions/compositions"},
88
88
"uniqueItems": true,
89
89
"title": "Compositions",
90
-
"description": "Compositions describe constituent parts (including components, services, and dependency relationships) and their completeness."
90
+
"description": "Compositions describe constituent parts (including components, services, and dependency relationships) and their completeness. Other inventory types such as vulnerabilities may also be described for completeness."
91
91
},
92
92
"vulnerabilities": {
93
93
"type": "array",
@@ -1528,7 +1528,7 @@
1528
1528
"type": "string"
1529
1529
},
1530
1530
"title": "BOM references",
1531
-
"description": "The bom-ref identifiers of the components or services being described. Assemblies refer to nested relationships whereby a constituent part may include other constituent parts. References do not cascade to child parts. References are explicit for the specified constituent part only."
1531
+
"description": "The bom-ref identifiers of the components or services being described. Assemblies refer to nested relationships whereby a constituent part may include other constituent parts. References do not cascade to child parts. References are explicit for the specified constituent part only. Other inventory types such as vulnerabilities may also be described."
<xs:documentation>Compositions describe constituent parts (including components, services, and dependency relationships) and their completeness.</xs:documentation>
3217
+
<xs:documentation>Compositions describe constituent parts (including components, services, and dependency relationships) and their completeness. Other inventory types such as vulnerabilities may also be described for completeness.</xs:documentation>
0 commit comments