You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(a2ml): reconcile media type to application/vnd.a2ml — unblocks IANA submission (#554)
Clears the last in-repo blocker to the **IANA media-type submission**.
## What I found
`a2ml/IANA-MEDIA-TYPE-APPLICATION.md` is a **complete, 259-line RFC 6838
vendor-tree application** for `application/vnd.a2ml` (rev 2, 2026-04-03,
*"Status: Draft — ready for submission"*). Its own checklist already
ticks *fields reviewed*, *spec links accessible*, *no naming conflict*,
and *ASAM A2L (`application/A2L`) distinction clarified*. The only
unticked items are **submit the form → monitor review → record the
assigned type**.
So the registration isn't months of work — it's **an owner action** (the
IANA web form needs applicant identity). But the repo contradicted its
own application in four places:
| name | uses | status |
|---|---|---|
| `application/vnd.a2ml` | 27 | ✅ the application doc's name |
| `text/a2ml` | 5 | ❌ incl. the **normative SPEC** |
| `application/vnd.a2ml+text` | 3 | ❌ `+text` is not a registered
structured-syntax suffix (RFC 6838 §4.2.8) |
| `application/a2ml` | 1 | ❌ standards-tree name — would need IETF
review, not the vendor tree |
A submission contradicted by its own normative spec invites
expert-review pushback, so this reconciles all four to the application
doc's name.
## Deliberately **not** touched
- `a2ml/archive/SPEC-v1.0.0.adoc` (×2) — frozen historical record; the
old name is *correct* there.
- `a2ml/RECORD-DIALECT-SPEC.adoc` §14 — it knowingly documents the
inconsistency and defers resolution to maintainers. Worth a small
editorial update **once IANA assigns the type**.
## Verification
`build-registry.sh --check` ✅ and `build-scorecards.sh --check --strict`
✅ locally. `REGISTRY.a2ml` regenerated because `SPEC.adoc` is
registry-tracked — which also clears the registry drift currently red on
main.
## ⚠️ Related risk for K9 (not fixed here)
K9's **dominant** name is `application/vnd.k9+nickel` (41 uses vs 11
bare `application/vnd.k9`). `+nickel` also does not appear in IANA's
Structured Syntax Suffix registry. **Verify before submitting K9** — if
unregistered, register bare `application/vnd.k9` and keep `+nickel` as
documentation, or pursue a separate suffix registration (slow; depends
on upstream Nickel).
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
0 commit comments