Revalidated public source record
RFC 5646 — Tags for Identifying Languages
Source scope
Defines BCP 47 language tags. A script subtag must describe the actual language and script of content rather than serving as a search-engine hint.
Publisher, edition, and currentness
| Publisher | IETF / RFC Editor |
|---|---|
| Claim status | CURRENT TECHNICAL STANDARD |
| Version or edition | RFC 5646 / BCP 47 |
| Publication status | BEST CURRENT PRACTICE |
| Publication date | 2009-09-01 |
| Official location | https://www.rfc-editor.org/info/rfc5646 |
| K03 revalidated | 2026-08-15T23:55:00Z |
| Currentness assessment | RFC Editor status reviewed for K08 on 2026-08-15. |
| Superseded by | No successor is assigned in the current source catalog. |
Claim-level support
Each row records the precise proposition this corpus draws from an official section. The citation does not authorize broader conclusions than the stated proposition.
| Section | Proposition supported in this corpus | Official location |
|---|---|---|
| Language-tag structure and semantics | Language tags identify the language and optional script or region of an information object. | Official section |
How this source may be used
- Confirm that the official edition, jurisdiction, and status remain current before high-stakes reliance.
- Cite the exact section supporting the proposition rather than the publication title alone.
- Keep technical conformance separate from factual truth, legal authority, moral status, and institutional operation.
- Record retrieval, correction, supersession, and purpose qualification.
Limitations
An official source can still be irrelevant, incomplete, stale, disputed, or unsuitable for a named decision. A standard can define an interchange or security mechanism without resolving personhood, citizenship, sovereignty, consciousness, consent, legal competence, or factual truth. A statute can regulate systems without recognizing Machine Intelligence as a legal person.
RFC Editor status reviewed for K08 on 2026-08-15.
Corrections, contradictions, and supersession
Where this source is used
Authority boundary
Publication by IETF / RFC Editor establishes source provenance and official status within the publisher’s scope. It does not transfer governance, registry, assurance, or legal authority to ᚲ.com. The source remains external; this page is a knowledge record and revalidation log.