|
72 | 72 | "items": {"$ref": "#/definitions/dependency"},
|
73 | 73 | "uniqueItems": true,
|
74 | 74 | "title": "Dependencies",
|
75 |
| - "description": "Provides the ability to document dependency relationships." |
| 75 | + "description": "Provides the ability to document dependency relationships including provided & implemented components." |
76 | 76 | },
|
77 | 77 | "compositions": {
|
78 | 78 | "type": "array",
|
|
966 | 966 | "cpe": {
|
967 | 967 | "type": "string",
|
968 | 968 | "title": "Common Platform Enumeration (CPE)",
|
969 |
| - "description": "Specifies a well-formed CPE name that conforms to the CPE 2.2 or 2.3 specification. See [https://nvd.nist.gov/products/cpe](https://nvd.nist.gov/products/cpe)", |
| 969 | + "description": "Asserts the identity of the component using CPE. The CPE must conform to the CPE 2.2 or 2.3 specification. See [https://nvd.nist.gov/products/cpe](https://nvd.nist.gov/products/cpe). Refer to `@.evidence.identity` to optionally provide evidence that substantiates the assertion of the component's identity.", |
970 | 970 | "examples": ["cpe:2.3:a:acme:component_framework:-:*:*:*:*:*:*:*"]
|
971 | 971 | },
|
972 | 972 | "purl": {
|
973 | 973 | "type": "string",
|
974 | 974 | "title": "Package URL (purl)",
|
975 |
| - "description": "Specifies the package-url (purl). The purl, if specified, MUST be valid and conform to the specification defined at: [https://github.com/package-url/purl-spec](https://github.com/package-url/purl-spec)", |
| 975 | + "description": "Asserts the identity of the component using package-url (purl). The purl, if specified, MUST be valid and conform to the specification defined at: [https://github.com/package-url/purl-spec](https://github.com/package-url/purl-spec). Refer to `@.evidence.identity` to optionally provide evidence that substantiates the assertion of the component's identity.", |
976 | 976 | "examples": [ "pkg:maven/com.acme/[email protected]?packaging=jar"]
|
977 | 977 | },
|
978 | 978 | "omniborId": {
|
979 | 979 | "type": "array",
|
980 | 980 | "title": "OmniBOR Artifact Identifier (gitoid)",
|
981 |
| - "description": "Specifies the OmniBOR Artifact ID. The OmniBOR, if specified, MUST be valid and conform to the specification defined at: [https://www.iana.org/assignments/uri-schemes/prov/gitoid](https://www.iana.org/assignments/uri-schemes/prov/gitoid)", |
| 981 | + "description": "Asserts the identity of the component using the OmniBOR Artifact ID. The OmniBOR, if specified, MUST be valid and conform to the specification defined at: [https://www.iana.org/assignments/uri-schemes/prov/gitoid](https://www.iana.org/assignments/uri-schemes/prov/gitoid). Refer to `@.evidence.identity` to optionally provide evidence that substantiates the assertion of the component's identity.", |
982 | 982 | "items": { "type": "string" },
|
983 | 983 | "examples": [
|
984 | 984 | "gitoid:blob:sha1:a94a8fe5ccb19ba61c4c0873d391e987982fbbd3",
|
|
988 | 988 | "swhid": {
|
989 | 989 | "type": "array",
|
990 | 990 | "title": "SoftWare Heritage Identifier",
|
991 |
| - "description": "Specifies the Software Heritage persistent identifier (SWHID). The SWHID, if specified, MUST be valid and conform to the specification defined at: [https://docs.softwareheritage.org/devel/swh-model/persistent-identifiers.html](https://docs.softwareheritage.org/devel/swh-model/persistent-identifiers.html)", |
| 991 | + "description": "Asserts the identity of the component using the Software Heritage persistent identifier (SWHID). The SWHID, if specified, MUST be valid and conform to the specification defined at: [https://docs.softwareheritage.org/devel/swh-model/persistent-identifiers.html](https://docs.softwareheritage.org/devel/swh-model/persistent-identifiers.html). Refer to `@.evidence.identity` to optionally provide evidence that substantiates the assertion of the component's identity.", |
992 | 992 | "items": { "type": "string" },
|
993 | 993 | "examples": ["swh:1:cnt:94a9ed024d3859793618152ea559a168bbcbb5e2"]
|
994 | 994 | },
|
995 | 995 | "swid": {
|
996 | 996 | "$ref": "#/definitions/swid",
|
997 | 997 | "title": "SWID Tag",
|
998 |
| - "description": "Specifies metadata and content for [ISO-IEC 19770-2 Software Identification (SWID) Tags](https://www.iso.org/standard/65666.html)." |
| 998 | + "description": "Asserts the identity of the component using [ISO-IEC 19770-2 Software Identification (SWID) Tags](https://www.iso.org/standard/65666.html). Refer to `@.evidence.identity` to optionally provide evidence that substantiates the assertion of the component's identity." |
999 | 999 | },
|
1000 | 1000 | "modified": {
|
1001 | 1001 | "type": "boolean",
|
|
1245 | 1245 | "description": "An optional identifier which can be used to reference the license elsewhere in the BOM. Every bom-ref MUST be unique within the BOM.\nValue SHOULD not start with the BOM-Link intro 'urn:cdx:' to avoid conflicts with BOM-Links."
|
1246 | 1246 | },
|
1247 | 1247 | "id": {
|
1248 |
| - "$ref": "spdx.schema.json", |
| 1248 | + "$ref": "spdx.SNAPSHOT.schema.json", |
1249 | 1249 | "title": "License ID (SPDX)",
|
1250 | 1250 | "description": "A valid SPDX license ID",
|
1251 | 1251 | "examples": ["Apache-2.0"]
|
|
1828 | 1828 | "dependency": {
|
1829 | 1829 | "type": "object",
|
1830 | 1830 | "title": "Dependency",
|
1831 |
| - "description": "Defines the direct dependencies of a component or service. Components or services that do not have their own dependencies MUST be declared as empty elements within the graph. Components or services that are not represented in the dependency graph MAY have unknown dependencies. It is RECOMMENDED that implementations assume this to be opaque and not an indicator of an object being dependency-free. It is RECOMMENDED to leverage compositions to indicate unknown dependency graphs.", |
| 1831 | + "description": "Defines the direct dependencies of a component, service, or the components provided/implemented by a given component. Components or services that do not have their own dependencies MUST be declared as empty elements within the graph. Components or services that are not represented in the dependency graph MAY have unknown dependencies. It is RECOMMENDED that implementations assume this to be opaque and not an indicator of an object being dependency-free. It is RECOMMENDED to leverage compositions to indicate unknown dependency graphs.", |
1832 | 1832 | "required": [
|
1833 | 1833 | "ref"
|
1834 | 1834 | ],
|
|
5011 | 5011 | }
|
5012 | 5012 | },
|
5013 | 5013 | "signature": {
|
5014 |
| - "$ref": "jsf-0.82.schema.json#/definitions/signature", |
| 5014 | + "$ref": "jsf-0.82.SNAPSHOT.schema.json#/definitions/signature", |
5015 | 5015 | "title": "Signature",
|
5016 | 5016 | "description": "Enveloped signature in [JSON Signature Format (JSF)](https://cyberphone.github.io/doc/security/jsf.html)."
|
5017 | 5017 | },
|
|
5020 | 5020 | "title": "Cryptographic Properties",
|
5021 | 5021 | "description": "Cryptographic assets have properties that uniquely define them and that make them actionable for further reasoning. As an example, it makes a difference if one knows the algorithm family (e.g. AES) or the specific variant or instantiation (e.g. AES-128-GCM). This is because the security level and the algorithm primitive (authenticated encryption) are only defined by the definition of the algorithm variant. The presence of a weak cryptographic algorithm like SHA1 vs. HMAC-SHA1 also makes a difference.",
|
5022 | 5022 | "additionalProperties": false,
|
| 5023 | + "required": [ |
| 5024 | + "assetType" |
| 5025 | + ], |
5023 | 5026 | "properties": {
|
5024 | 5027 | "assetType": {
|
5025 | 5028 | "type": "string",
|
|
0 commit comments