Skip to content

[WIP] harmonize actors with party model - #1100

Draft
jkowalleck wants to merge 3 commits into
2.0-devfrom
2.0-dev_role-based-parties-harmoize
Draft

jkowalleck wants to merge 3 commits into
2.0-devfrom
2.0-dev_role-based-parties-harmoize

Conversation

@jkowalleck

@jkowalleck jkowalleck commented Sep 10, 2026 •

Copy link
Copy Markdown
Member

WORK IN PROGRESS


Changed:

  • remove cyclonedx-common-2.0.schema.json#/$defs/organizationalEntity
  • remove cyclonedx-common-2.0.schema.json#/$defs/organizationalContact
  • remove cyclonedx-common-2.0.schema.json#/$defs/organizationalEntityOrContact

btw: metadata.supplier will be removed - see #1090

@jkowalleck jkowalleck changed the title [WIP] harmonixe actors with party model [WIP] harmonize actors with party model Sep 10, 2026
taleodor-claude pushed a commit to relizaio/sbom-everywhere that referenced this pull request Sep 13, 2026
The CycloneDX 2.0 column carried "Same" for SBOM Author, inheriting
`metadata.manufacturer.name` or `authors[].name` from 1.6 and 1.7.
CycloneDX/specification#1100 replaces `metadata.authors`,
`metadata.manufacturer` and `metadata.supplier` with `metadata.parties`,
so neither field survives into 2.0 and the row now names
`metadata.parties[]`. It cites note [a], which already describes the
party shape generally: roles are the only requirement, alongside one
identity block. This also makes the metadata row symmetric with
Component Producer, which already maps to `components[].parties[]`.

Note [y] introduced the relationship as `descendentOf` and then used
`descendantOf` in the following sentence. The latter is the SPDX
relationship type, so the first spelling is corrected.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
taleodor-claude pushed a commit to relizaio/sbom-everywhere that referenced this pull request Sep 13, 2026
The CycloneDX 2.0 column carried "Same" for SBOM Author, inheriting
`metadata.manufacturer.name` or `authors[].name` from 1.6 and 1.7.
CycloneDX/specification#1100 replaces `metadata.authors`,
`metadata.manufacturer` and `metadata.supplier` with `metadata.parties`,
so neither field survives into 2.0 and the row now names
`metadata.parties[]`. It cites note [a], which already describes the
party shape generally: roles are the only requirement, alongside one
identity block. This also makes the metadata row symmetric with
Component Producer, which already maps to `components[].parties[]`.

Note [y] introduced the relationship as `descendentOf` and then used
`descendantOf` in the following sentence. The latter is the SPDX
relationship type, so the first spelling is corrected.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: Claude Code (ReARM Agent) <rearm-agent-claude@reliza.io>
@jkowalleck jkowalleck added this to the 2.0 milestone Sep 14, 2026
Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
@jkowalleck
jkowalleck force-pushed the 2.0-dev_role-based-parties-harmoize branch from ba41025 to 1e62752 Compare October 5, 2026 11:44
@jkowalleck

Copy link
Copy Markdown
Member Author

actively workin on this

@jkowalleck

Copy link
Copy Markdown
Member Author

Explicit actors, as inline objects or strings

cyclonedx-metadata-2.0.schema.json#/$defs/metadata/properties/manufacturer
cyclonedx-metadata-2.0.schema.json#/$defs/metadata/properties/authors
cyclonedx-annotation-2.0.schema.json#/$defs/annotation/properties/annotator
cyclonedx-annotation-2.0.schema.json#/$defs/annotation/properties/annotator/properties/organization
cyclonedx-annotation-2.0.schema.json#/$defs/annotation/properties/annotator/properties/individual
cyclonedx-common-2.0.schema.json#/$defs/commit/properties/author
cyclonedx-common-2.0.schema.json#/$defs/commit/properties/committer
cyclonedx-declaration-2.0.schema.json#/$defs/declarations/properties/assessors/items/properties/organization
cyclonedx-declaration-2.0.schema.json#/$defs/declarations/properties/assessors/items/properties/thirdParty
cyclonedx-declaration-2.0.schema.json#/$defs/declarations/properties/targets/properties/organizations
cyclonedx-declaration-2.0.schema.json#/$defs/declarations/properties/evidence/items/properties/author
cyclonedx-declaration-2.0.schema.json#/$defs/declarations/properties/evidence/items/properties/reviewer
cyclonedx-declaration-2.0.schema.json#/$defs/declarations/properties/affirmation/properties/signatories/items/properties/organization
cyclonedx-license-2.0.schema.json#/$defs/licensing/properties/licensor
cyclonedx-license-2.0.schema.json#/$defs/licensing/properties/licensee
cyclonedx-license-2.0.schema.json#/$defs/licensing/properties/purchaser
cyclonedx-patent-2.0.schema.json#/$defs/patent/properties/patentAssignee
cyclonedx-patent-2.0.schema.json#/$defs/patentAssertions/items/properties/asserter
cyclonedx-vulnerability-2.0.schema.json#/$defs/vulnerability/properties/credits/properties/organizations
cyclonedx-vulnerability-2.0.schema.json#/$defs/vulnerability/properties/credits/properties/individuals
cyclonedx-evidence-2.0.schema.json#/$defs/occurrence/properties/systemOwner
cyclonedx-standard-2.0.schema.json#/$defs/standard/properties/owner
cyclonedx-blueprint-2.0.schema.json#/$defs/dataStore/properties/vendor

Actors referenced by id (refLinkType)

cyclonedx-declaration-2.0.schema.json#/$defs/declarations/properties/attestations/items/properties/assessor
cyclonedx-behavior-2.0.schema.json#/$defs/behaviorInstance/properties/actors
cyclonedx-behavior-2.0.schema.json#/$defs/behaviorNode/properties/actors
cyclonedx-threat-2.0.schema.json#/$defs/threatScenario/properties/actor
cyclonedx-threat-2.0.schema.json#/$defs/attackPath/properties/actor
cyclonedx-usecase-2.0.schema.json#/$defs/useCase/properties/actors
cyclonedx-usecase-2.0.schema.json#/$defs/step/properties/actor
cyclonedx-blueprint-2.0.schema.json#/$defs/asset/properties/partyRef
cyclonedx-component-2.0.schema.json#/$defs/identifier/properties/party

Actors using party (partyChoice or party) These are the ones you said to skip. I'm listing them only in case you want them.

cyclonedx-blueprint-2.0.schema.json#/$defs/metadata/properties/authors
cyclonedx-blueprint-2.0.schema.json#/$defs/metadata/properties/reviewer
cyclonedx-blueprint-2.0.schema.json#/$defs/metadata/properties/approver
cyclonedx-blueprint-2.0.schema.json#/$defs/dataSet/properties/owners
cyclonedx-blueprint-2.0.schema.json#/$defs/actor/properties/party
cyclonedx-blueprint-2.0.schema.json#/$defs/assumption/properties/owner
cyclonedx-blueprint-2.0.schema.json#/$defs/ownership
cyclonedx-business-objective-2.0.schema.json#/$defs/businessObjective/properties/owner
cyclonedx-component-2.0.schema.json#/$defs/energyProvider/properties/provider
cyclonedx-control-2.0.schema.json#/$defs/control/properties/owner
cyclonedx-data-2.0.schema.json#/$defs/subject/properties/party
cyclonedx-evidence-2.0.schema.json#/$defs/partyAttribution/properties/party
cyclonedx-risk-2.0.schema.json#/$defs/risk/properties/owner
cyclonedx-risk-2.0.schema.json#/$defs/riskResponse/properties/owner
cyclonedx-risk-2.0.schema.json#/$defs/assessment/properties/assessors
cyclonedx-risk-2.0.schema.json#/$defs/riskAppetite/properties/party
cyclonedx-risk-2.0.schema.json#/$defs/riskAppetite/properties/owner

Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>

This branch has not been deployed

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant