CycloneDX / CycloneDX/specification

[2.0] formulation - docs make nosense

Open
#1,083 0 comments 0 reactions 1 assignee Claimed by @jkowalleck View on GitHub
cap: formulation CDX 2.0 defect
Dominant language
XSLT
Stars
547
Forks
93
Avg merge
7h 11m
Merged PRs (30d)
37

Description

the CDX 2.0 formulation docsmake nosens

for example:
https://github.com/CycloneDX/specification/blob/a1c8aeb2e4e6a72851fd937f210e9b5add1cf514/schema/2.0/model/cyclonedx-formulation-2.0.schema.json#L653

> A reference to the component or service [...]

`service` is done with CDX 2.0 - we only have components.

> [...] (e.g., reference to a service with data flow value of `inbound`)

where does this `inbound` come from? is this expected to be an enum value? if so, it is not defined nowhere.

same for this
https://github.com/CycloneDX/specification/blob/a1c8aeb2e4e6a72851fd937f210e9b5add1cf514/schema/2.0/model/cyclonedx-formulation-2.0.schema.json#L662
.. where comes this "outbound" from?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.