Re: [Ltru] RFC 4646 production "grandfathered" considered harmful

[Addison Phillips <addison at yahoo-inc.com>]

Martin Duerst wrote:
> [chair hat on]
> I have seen at least four people approving the idea to list
> grandfathered/irregular tags explicitly, and nobody opposed.
> I think that in principle, we seem to have consensus to go this
> way, although some details may need to be worked out (see below).
> If anybody disagrees with this assessment, please state so soon.

[editor hat on]

I'll prepare an updated ABNF shortly.

> [chair hat off]
> I clearly thing that it is a bad idea to include somebody's name
> in a nonterminal of an ABNF. This is true both in general and also
> in this specific case. When Michael proposed and approved the
> tags listed below, they were not in any way illegal or irregular.

[contributor hat on]

I agree. I think that proposal was made tongue-in-cheek. I intend to 
start with the production "irregular" shown below

Addison

> > grandfathered = irregular 
> >
> >            / 1*3ALPHA 1*2("-" (2*8alphanum)) ; registered grandfathered codes that are well-formed, but would not otherwise be valid
> >
> > irregular = "en-GB-oed" / "i-ami" / "i-bnn" / "i-default" 
> >           / "i-enochian" / "i-hak" / "i-klingon" / "i-lux" / "i-mingo"
> >           / "i-navajo" / "i-pwn" / "i-tao" / "i-tay" / "i-tsu" 
> >           / "sgn-BE-fr" / "sgn-BE-nl" / "sgn-CH-de"

--
Addison Phillips
Globalization Architect -- Yahoo! Inc.

Internationalization is an architecture.
It is not a feature.

_______________________________________________
Ltru mailing list
Ltru at ietf.org
https://www1.ietf.org/mailman/listinfo/ltru