Skip to content

fix(ML-BOM): normalize terminology (ML-BOM, CycloneDX, Hugging Face) - #122

Open
andife wants to merge 1 commit into
CycloneDX:mainfrom
andife:fix/ml-bom-terminology
Open

andife wants to merge 1 commit into
CycloneDX:mainfrom
andife:fix/ml-bom-terminology

Conversation

@andife

@andife andife commented Nov 8, 2026

Copy link
Copy Markdown
Contributor

Summary

Terminology consistency pass over the ML-BOM guide:

  • MLBOM -> ML-BOM (0x20): the guide uses ML-BOM everywhere else (e.g. 0x10-Introduction, 0x15-Core-Concepts); the intro sentence in 0x20 also defined the dual form '(MLBOM or ML-BOM)', now simplified to '(ML-BOM)'.
  • 'the Cyclone model card' -> 'the CycloneDX model card' in the intros of 0x22, 0x23 and 0x24.
  • Huggingface -> Hugging Face (10 occurrences across 0x15, 0x20, 0x90, 0x91): the official vendor styling, already used in ~28 other places in the guide. Lowercase purl values (pkg:huggingface/...), purl type references in URLs, and huggingface.co links are intentionally left unchanged.

No content changes beyond spelling/styling.

- 'MLBOM' -> 'ML-BOM', matching usage throughout the guide.
- 'the Cyclone model card' -> 'the CycloneDX model card' in three
  chapter intros.
- 'Huggingface' -> 'Hugging Face' (official styling, used in the
  majority of the guide). purl values (pkg:huggingface/...) and URLs
  are intentionally unchanged.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: Andreas Fehlner <fehlner@arcor.de>
@andife
andife requested a review from a team as a code owner November 8, 2026 07:48
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.

1 participant