ML-BOM guide: Qwen-7B example in 0x24 (Considerations) mixes in Qwen3-specific facts and contradicts 0x22
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Documentación
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- huggingface, machine-learning
Línea de trabajo
Lee 0x24-Design-Model-Card-Considerations.md junto con 0x22-Design-Model-Card-Parameters.md y, después, verifica las fuentes citadas de Qwen-7B y Qwen3. Resuelve la elección del modelo del maintainer, actualiza de forma coherente los ejemplos afectados y asegúrate de que bom-ref, los datos del modelo y las afirmaciones sobre la longitud del contexto ya no se contradigan entre sí.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
The guide's running example model is Qwen-7B (Alibaba, released 2023-08-03, bom-ref: pkg:huggingface/Qwen/Qwen-7B@ef3c5c9, used throughout the guide starting in 0x20-Design-Model-Component-Metadata.md). The considerations example content in 0x24-Design-Model-Card-Considerations.md attributes several Qwen3-specific (2025) facts, features, and terminology to this Qwen-7B example — producing both external factual errors and an internal self-contradiction against the guide's own hyperparameter example in 0x22.
Internal contradiction (within the guide itself)
- 0x22:385-386 declares
cdx:ai-ml:model:hyperparameter:context_length="8192"forpkg:huggingface/Qwen/Qwen-7B@ef3c5c9. - 0x24:88 says, for the same
bom-ref: "the model supports up to 131,072 tokens using YaRN scaling, its native pre-training context is limited to 32,768 tokens."
Two different context-length claims for the same declared component, within the same guide.
Facts that belong to Qwen3, not Qwen-7B
- "Thinking Mode" (0x24:46, :87, :90, :181) — the thinking/non-thinking mode toggle was introduced with Qwen3; it doesn't exist in Qwen-7B (2023).
- YaRN scaling to 131,072 / native 32,768 context (0x24:88, :125) — this is Qwen3's documented spec (see Qwen3 Technical Report). Qwen-7B's real context length is 8,192, per its own published
config.json. - "32B or 235B models" and "Qwen-8B" as sibling models (0x24:123, :125) — these are Qwen3 sizes (dense up to 32B, MoE 30B-A3B/235B-A22B). The original Qwen (Qwen1) lineup was 1.8B/7B/14B/72B — no 32B, no 235B, no "Qwen-8B".
- "trained on 36 trillion tokens across 119 languages," attributed to "Qwen-7B" by name (0x24:160) — this is Qwen3's documented pretraining corpus size/language coverage. Qwen-7B (2023) was trained on ~2.4 trillion tokens.
- "Qwen3Guard" cited as the safety reference for the Qwen-7B example (0x24:148, :165) — Qwen3Guard (released September 2025) is a guardrail model family built on Qwen3, unrelated to Qwen-7B.
- "more parallelizable MoE models" comparison (0x24:128) — Qwen-7B is dense with no MoE sibling in its own generation.
- Typo "Qwen3 &B parameter model" (0x24:112) — literally names "Qwen3" instead of "Qwen-7B." Note Qwen3's dense lineup is 0.6B/1.7B/4B/8B/14B/32B — there is no Qwen3-7B, so this can't even be "corrected" to match a real Qwen3 size.
Why it matters
This is the guide's primary worked example for modelCard.considerations. A reader relying on it as a reference, or cross-checking it against the real Qwen-7B model card, will find internally inconsistent and externally incorrect data — undermining the guide's own point about ML-BOMs enabling reproducibility and verifiable claims (see 0x10-Introduction.md, "Reproducibility & Explainability").
Suggested fix — needs a maintainer call, hence an issue rather than a PR
Either:
- (a) Rebase the whole
considerationsexample (and thecontext_lengthhyperparameter in0x22) on Qwen3-8B, since most of the existing prose already matches that model, or - (b) Rewrite the
considerationscontent to reflect the real, historical Qwen-7B (2023) — dropping Thinking Mode / YaRN / Qwen3Guard / MoE references.
Verification sources
- https://huggingface.co/Qwen/Qwen-7B/blob/main/config.json
- https://github.com/QwenLM/Qwen/blob/main/README.md
- https://arxiv.org/pdf/2505.09388 (Qwen3 Technical Report)
- https://huggingface.co/Qwen/Qwen3-8B
- https://qwenlm.github.io/blog/qwen3/
- https://github.com/QwenLM/Qwen3Guard
This issue was drafted with assistance from Claude Sonnet 5 (model id: claude-sonnet-5), which identified and fact-checked the inconsistency described above.
- Lenguaje dominante
- CSS
- Estrellas
- 10
- Forks
- 13
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de CycloneDX/guides
-
documentation t: MBOM t: ML-BOM
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
-
fix: examples and code-fencingPosiblemente ocupada @jkowalleck la tomó hace 71 días. Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 72/100
-
[CDX2.0] guide on perspectivesAbierto
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
-
help wanted t: MBOM t: OBOM t: SBOM t: VDR+VEX
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
-
Adjust object "swimlane" element labels for MBOM (Formulation)Quizá libre de nuevo @mrutkows la tomó hace 659 días y no hay ningún pull request abierto. Abiertodocumentation
Todos los issues de CycloneDX/guides
Issues similares
-
good first issue help wanted r-docs
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
servo/rust-smallvec#824 ·
Los mantenedores suelen responder en 1 día
-
[guide] AGENTS.md claims the coverage gate, e2e and full lint run on every PR after ADR 0011 focused validationPosiblemente ocupada @hivecommons-hive la tomó hoy. Abiertoagent/guide documentation hive/claimed-by-guide stage/040-covered-by-pr
Dificultad 2/5 1-3 horas Aptitud para principiantes 81/100
cncf/endusers#2006 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 2 días
-
Add dependency list in documentsAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
Los mantenedores suelen responder en 3 días
-
feedback simulation workshop
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
githubnext/gh-aw-workshop#5157 ·
Los mantenedores suelen responder en 1 día