ISO 639-3 changes, part 1
Phillips, Addison
addison at amazon.com
Mon Feb 1 05:52:07 CET 2010
There is no rule otherwise. Any individual change has its own minimum timeline. The only reason to batch them for IANA would be to reduce churn.
Addison Phillips
Globalization Architect -- Lab126
Internationalization is not a feature.
It is an architecture.
> -----Original Message-----
> From: ietf-languages-bounces at alvestrand.no [mailto:ietf-languages-
> bounces at alvestrand.no] On Behalf Of John Cowan
> Sent: Friday, January 29, 2010 11:13 PM
> To: Doug Ewell
> Cc: ietf-languages at iana.org
> Subject: Re: ISO 639-3 changes, part 1
>
> Doug Ewell scripsit:
>
> > The date 2010-03-01 in these records is an approximation, based
> on how
> > long it might take to get through these and 70+ other changes.
>
> Why can't these be sent to IANA by themselves as soon as the errors
> are
> corrected and the time has expired? I see no reason why all the
> changes
> should be collected together before IANA gets any of them -- a
> pipeline
> process seems more sensible to me.
>
> --
> Do what you will, John Cowan
> this Life's a Fiction cowan at ccil.org
> And is made up of http://www.ccil.org/~cowan
> Contradiction. --William Blake
> _______________________________________________
> Ietf-languages mailing list
> Ietf-languages at alvestrand.no
> http://www.alvestrand.no/mailman/listinfo/ietf-languages
More information about the Ietf-languages
mailing list