feat(crypto): support standardized algorithm identifiers

[qkaiser]

Description

CycloneDX 1.7 distinguishes schema-defined families and curves while older consumers still depend on free-form curve metadata.

Derive the accepted cases from the bundled schema and gate standardized serialization to the new view. Preserve the legacy value through comparison and rendering, then exercise strict schema output and downgrade behavior.

AI Tool Disclosure

• My contribution does not include any AI-generated content
• My contribution includes AI-generated content, as disclosed below:
  • AI Tools: codex
  • LLMs and versions: gpt-5.6-sol xhigh
  • Prompts: see below

LLM prompt

## Complete CycloneDX 1.7 cryptography models
Summary
Extend cyclonedx.model.crypto to model and round-trip every requested CycloneDX 1.7 CBOM field in JSON and XML. Preserve all existing 1.6 APIs and deprecated reference fields; the already-implemented key-wrap primitive and 1.7 protocol types require verification rather than duplication.
Public API and model changes

Add schema-backed CryptoAlgorithmFamily and CryptoEllipticCurve enums. Extend AlgorithmProperties with algorithm_family and elliptic_curve, emitted only for 1.7; retain deprecated curve.

Serialization behavior

Gate new fields and structured models to SchemaVersion1Dot7, with exact CycloneDX JSON names, XML element names, ordering, nested arrays, and date/hash mappings.
Add union serialization helpers for certificate states and extensions so JSON and XML deserialize into the correct predefined/custom model.
Include every new property in comparison, hashing, sorting, and representation behavior where applicable.

Test plan

Add enum completeness tests against the bundled 1.7 schemas, including algorithm families, elliptic curves, certificate states/extensions, key-wrap, and protocol types.
Add model tests for construction, equality, hashing, sorting, union discrimination, and mixed-IKEv2 rejection.
Expand representative crypto BOM fixtures and JSON/XML snapshots with every new field.
Validate 1.7 output against strict bundled schemas and test JSON/XML round-trip deserialization.
Verify 1.6 output remains schema-valid, retains legacy fields, omits 1.7-only fields, and preserves protocol-type downgrade behavior.
Run the full unittest suite plus mypy and flake8.

Assumptions

Existing deprecated CycloneDX fields are not removed or automatically translated into preferred 1.7 relationships.
Schema arrays follow the library convention of deterministic SortedSet storage.

Affirmation

• My code follows the CONTRIBUTING.md guidelines

[read-the-docs-community]

Documentation build overview

📚 CycloneDX Python Library | 🛠️ Build #33579738 | 📁 Comparing fd0ec25 against latest (cf392e0)

  🔍 Preview build  

2 files changed

± genindex.html
± autoapi/cyclonedx/model/crypto/index.html

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 5 complexity · 0 duplication

Metric	Results
Complexity	5
Duplication	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[CAOShurong]

I independently tested this exact head and the standardized identifiers behave consistently across the supported views.

Verification performed:

• 344 focused enum/model tests passed;
• the full suite passed (7,305 tests);
• flake8 and mypy passed;
• sdist and wheel builds passed;
• a clean wheel install produced schema-valid CycloneDX 1.7 JSON and XML, round-tripped the new fields, and omitted them while retaining the legacy curve on a 1.6 downgrade.

I did not find a correctness regression in the reviewed scope. Review prepared with OpenAI Codex assistance; I verified the commands, outputs, and conclusion.

[jkowalleck]

we could add the data fields, but i would not want to have them values implemented as enums here.

the enum values are not part of CycloneDX spec itself, but are part of an extra schema https://github.com/CycloneDX/specification/blob/master/schema/cryptography-defs.schema.json
This schema moves in a differnet pace than the CycloneDX, and i dont want to have an external enum chasing reality.