[Defect]: relatedCryptographicAsset.type description is copied from securedBy.mechanism

Open Beginner friendly
#1,045 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
91/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
json
Domain
documentation

Research direction

Open bom-1.7.schema.json and compare the description for relatedCryptographicAsset.type with securedBy.mechanism. Update the former to describe the referenced asset type, then verify that the wording matches the issue's proposed meaning and does not alter the existing securedBy description.

Written by the indexing model from the issue text.

Description

defect

Describe the defect

In bom-1.7.schema.json, relatedCryptographicAsset.type is described as:

Specifies the mechanism by which the cryptographic asset is secured by.

This is the same sentence as securedBy.mechanism, which describes a different thing. The examples given for the field (publicKey, privateKey, algorithm) say what the referenced asset is, not how the component is protected.

The field is new in 1.7, and securedBy already existed in 1.6, so this looks like a copy when the field was added.

Additional context

A possible wording:

Specifies the type of the related cryptographic asset.

Dominant language
XSLT
Stars
551
Forks
93
Avg merge
4h 51m
Merged PRs (30d)
42

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CycloneDX/specification

All issues in CycloneDX/specification

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.