Re: [Ltru] Fwd: draft-davis-t-langtag-ext

[Kent Karlsson <[e-mail]>]

Den 2011-07-10 16:47, skrev "Debbie Garside" <[e-mail]>:

> Hi Addison
> 
> I'm not sure that I see where the "overhead" is.  Can you elaborate?
> 
> BCP47 states:
> 
> IANA will maintain a registry of allocated single-character
>    (singleton) subtags.  This registry MUST use the record-jar format
>    described by the ABNF in Section 3.1.1.  Upon publication of an
>    extension as an RFC, the maintaining authority defined in the RFC
>    MUST forward this registration form to <[e-mail]>, who MUST
>    forward the request to <[e-mail]>.  The maintaining authority of
>    the extension MUST maintain the accuracy of the record by sending an
>    updated full copy of the record to <[e-mail]> with the subject
>    line "LANGUAGE TAG EXTENSION UPDATE" whenever content changes.  Only
>    the 'Comments', 'Contact_Email', 'Mailing_List', and 'URL' fields MAY
>    be modified in these updates.

That is for registering that there at all are certain approved extensions.
It provides *no* data about the subtags "under" any extension.

> This IMHO is the overhead.  Given that we already have ietf-languages as a
> discussion list, and all the rules and regulations for application and
> registration of subtags, why create another "private" process? CLDR-TC would
> have to create transparent rules and regs anyway.

The IANA language subtag registry has no way of registering what goes
"under" an extension. Only things preceding any extension (and separately
a list of approved singletons for extensions). Changing this would mean
revising BCP 47. That would be a major hurdle.

> Keeping everything in one place/list has got to be easier for the end user.  I
> still cannot see any real reason for taking this out of IETF other than BCP47
> allows for it.  

As Addison mentioned, one can have a separate registry for an extension that
is held by IANA. But that would mean defining lots of details on exactly
goes into the registry, its format, procedures for approval, etc. That is
NOT covered by BCP 47.

> I can see the proposed -t extension mechanism being widely used by a number of
> organisations, 

I can agree with that part.

    /Kent K

> unlike the -u extension which was specifically designed for
> integrating CLDR data within a subtag.  I don't think we can compare the two
> processes.  
> 
> Best wishes
> 
> Debbie