#13 closed editorial (fixed)
Updated reference for language tags
Reported by: | mnot@… | Owned by: | julian.reschke@… |
---|---|---|---|
Priority: | urgent | Milestone: | 08 |
Component: | p3-payload | Severity: | Active WG Document |
Keywords: | Cc: |
Description
RFC 1766, which is referenced by RFC 2616 section 3.10 as the source for its definition of language tags has a BNF has been updated by RFC3066 (a BCP).
RFC 3066 defines these as:
Language-Tag = Primary-subtag *( "-" Subtag ) Primary-subtag = 1*8ALPHA Subtag = 1*8(ALPHA / DIGIT)
HTTP/1.1 RFC 2616 defines these as:
language-tag = primary-tag *( "-" subtag ) primary-tag = 1*8ALPHA subtag = 1*8ALPHA
In the meantime, RFC3066 has been obsoleted by RFC4646, and the original grammar production defining subtags seems to be gone:
Language-Tag = langtag / privateuse ; private use tag / grandfathered ; grandfathered registrations langtag = (language ["-" script] ["-" region] *("-" variant) *("-" extension) ["-" privateuse]) language = (2*3ALPHA [ extlang ]) ; shortest ISO 639 code / 4ALPHA ; reserved for future use / 5*8ALPHA ; registered language subtag extlang = *3("-" 3ALPHA) ; reserved for future use script = 4ALPHA ; ISO 15924 code region = 2ALPHA ; ISO 3166 code / 3DIGIT ; UN M.49 code variant = 5*8alphanum ; registered variants / (DIGIT 3alphanum) extension = singleton 1*("-" (2*8alphanum)) singleton = %x41-57 / %x59-5A / %x61-77 / %x79-7A / DIGIT ; "a"-"w" / "y"-"z" / "A"-"W" / "Y"-"Z" / "0"-"9" ; Single letters: x/X is reserved for private use privateuse = ("x"/"X") 1*("-" (1*8alphanum)) grandfathered = 1*3ALPHA 1*2("-" (2*8alphanum)) ; grandfathered registration ; Note: i is the only singleton ; that starts a grandfathered tag alphanum = (ALPHA / DIGIT) ; letters and numbers
So shouldn't RFC2616 (Section 3.10) stop defining these things, and just normatively refer to RFC4626 for the definition of "Language-Tag"?
Attachments (4)
Change History (24)
comment:1 Changed 15 years ago by fielding@…
- version set to 00
comment:2 Changed 15 years ago by mnot@…
- version changed from 00 to d00
comment:3 Changed 15 years ago by mnot@…
- Milestone set to 01
comment:4 Changed 15 years ago by mnot@…
- Component set to messaging
comment:5 Changed 15 years ago by fielding@…
- Milestone changed from 01 to 02
comment:6 Changed 15 years ago by mnot@…
- Milestone changed from 02 to 03
comment:7 Changed 15 years ago by julian.reschke@…
- Component changed from p1-messaging to p3-payload
- Owner set to julian.reschke@…
comment:8 Changed 15 years ago by julian.reschke@…
I propose to go ahead with the change independantly of the ABNF migration; we already have applied other changes to the BNF; and, after all, everything is under source control for later checks.
comment:9 Changed 15 years ago by julian.reschke@…
- Milestone changed from 03 to 04
comment:10 Changed 14 years ago by julian.reschke@…
- Milestone changed from 04 to unassigned
comment:11 Changed 14 years ago by julian.reschke@…
Proposal: delay until RFC4646bis is published (see http://tools.ietf.org/html/draft-ietf-ltru-4646bis-17)
comment:12 Changed 14 years ago by julian.reschke@…
draft-ietf-ltru-4646bis is now in state Publication Requested (https://datatracker.ietf.org/idtracker/draft-ietf-ltru-4646bis/)
comment:13 Changed 14 years ago by julian.reschke@…
draft-ietf-ltru-4646bis has been approved and now is in the RFC Editor's publication queue: http://www.rfc-editor.org/queue.html#draft-ietf-ltru-4646bis
Changed 14 years ago by julian.reschke@…
Proposed patch updated so it can be applied to current draft
comment:14 Changed 14 years ago by julian.reschke@…
- Milestone changed from unassigned to 08
comment:15 Changed 14 years ago by julian.reschke@…
- Resolution set to fixed
- Status changed from new to closed
comment:16 Changed 14 years ago by julian.reschke@…
- Resolution fixed deleted
- Status changed from closed to reopened
comment:17 Changed 14 years ago by mnot@…
- Priority set to urgent
comment:18 Changed 13 years ago by julian.reschke@…
From [690]:
draft-ietf-ltru-4646bis-23 has been published as RFC5646 (see #13)
comment:19 Changed 13 years ago by julian.reschke@…
- Resolution set to fixed
- Severity set to Candidate WG Document
- Status changed from reopened to closed
comment:20 Changed 11 years ago by mnot@…
- Severity changed from Candidate WG Document to Active WG Document
postpone until ABNF update.