Skip to content

Conversation

@viveksahu26
Copy link
Collaborator

@viveksahu26 viveksahu26 commented Jan 8, 2026

This PR adds the following changes:

  • It include detailed fields of BSI TR-03183:2.0.0 fields, corresponding field in SPDX:2.3, SPDX:3.0 and CDX:1.6.
  • This guide will act as a source of truth for our core implementation.
  • Our logic should sync with it.
  • In future for any changes, will update this and then core implementation.

This is related to issues: #591 #587 # in terms of theoritically for now. Many of the fields and respective are clear now after examples being shown for each field in BSI TR-03183:2.1.0
NOTE: It requires review.

@viveksahu26
Copy link
Collaborator Author

Hey @robin-s-007, have a looks at the fields of BSI:v2.0.0 and corresponding fields in SPDX/CDX for clarity. And then, we can we can sync it with our core logic implementation part.

@viveksahu26
Copy link
Collaborator Author

viveksahu26 commented Jan 8, 2026

Hey @fvsamson, would love to hear your feedback into this. Since, the examples of each fields and their references in BSI TR-03183:2.0.0 are not shown, as well as even in BSI TR-03183:2.1.0, the fields ref for SPDX:2.3 are not shown, so possibly it could create confusion in mapping field especially wrt SPDX, so, your feedback would be really helpful here.

For more specifically, I need help for "confusion--clarification-needed": https://github.com/viveksahu26/sbomqs/blob/fix/bsi_2_0_issues/docs/reference/bsi-v2.0.0.md#confusion--clarification-needed-bsi-v200

@viveksahu26 viveksahu26 changed the title add bsi-v2.0.0 guide update bsi-v2.0.0 fields values Jan 12, 2026
@fvsamson
Copy link
Contributor

@viveksahu26, thank you very much for bringing this up. As I am currently quite busy with other stuff, I would like to directly involve our SBOM specifications (i.e. CDX & SPDX) expert @ThomSei.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants