headers
Doug Ewell | 8 Feb 19:08
Favicon

ISO 639-3 changes

ISO 639-3/RA has released its 2011 series of changes. With this series,
the RA approved 142 changes encompassing roughly 200 code elements. 
Clearly the rate of change has not diminished in the years following the
initial release of 639-3.

In the coming days or weeks, I'll be sending proposed records and
registration forms to keep the Registry in step with this. As in years
past, I'll try to send them out in batches, organized by the type of
639-3 change (retirement, new language, update).

--
Doug Ewell | Thornton, Colorado, USA
http://www.ewellic.org | @DougEwell ­

_______________________________________________
Ietf-languages mailing list
Ietf-languages <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/ietf-languages
Permalink | Reply |
headers
John Cowan | 9 Feb 01:00

Re: ISO 639-3 changes

Doug Ewell scripsit:

> 639-3 change (retirement, new language, update).

I'd say the right order is "new language", "update", "retirement".

--

-- 
Business before pleasure, if not too bloomering long before.
        --Nicholas van Rijn
                John Cowan <cowan <at> ccil.org>
                    http://www.ccil.org/~cowan
Permalink | Reply |
headers
Doug Ewell | 9 Feb 02:41
Favicon

Re: ISO 639-3 changes

John Cowan wrote:

> Doug Ewell scripsit:
>
>> 639-3 change (retirement, new language, update).
>
> I'd say the right order is "new language", "update", "retirement".

I hadn't thought they would necessarily be sent in batches to IANA, only 
to this list.  If I remember correctly, in the past I posted 639-3-based 
records and forms to the list in batches, but I sent them to Michael for 
submission to IANA all at once.  I'm not sure whether it's best to have 
IANA do several Registry updates in a case like this, or just one.

Anyway, if they do all go to IANA at the same time, the "right order" to 
post them on the list becomes kind of moot.  The simple cases should 
probably go first, as opposed to changes that cascade over into several 
subtags.

I need to wait a few days anyway for ISO 639-3/RA to fix a couple of 
errors in the data files.

--
Doug Ewell | Thornton, Colorado, USA
http://www.ewellic.org | @DougEwell ­
Permalink | Reply |
headers
Doug Ewell | 13 Feb 23:51
Favicon

Re: ISO 639-3 changes

On Thu Feb 9 02:41:46 CET 2012, I wrote:

> I need to wait a few days anyway for ISO 639-3/RA to fix a couple of
> errors in the data files.

After working through most of the Summary of Outcomes document and the
data files (*.tab), and discovering a significant number of errors and
inconsistencies, I propose that we wait until a revised set of data
files is available from ISO 639-3/RA before making changes to the
Language Subtag Registry.  This may take a few additional weeks,
according to the RA.

The risk in going forward now is that changes will be made to the
Registry that are not reflected in 639-3, and some incorrect changes may
be made that are not reversible.  For instance, we cannot delete a
language subtag that was created in error; we can only deprecate it.

Picking out the non-problematic code elements and applying them to the
Registry, while leaving the problematic ones until the fixes are in
place, would be tricky from a clerical standpoint.  I'd prefer to wait
for a clean and correct data set.

I will finish going through the current batch of data to try to unearth
any additional problems, so they can be corrected in the next release.

Apologies to anyone who has been waiting to use one of the new or
changed subtags.

--
Doug Ewell | Thornton, Colorado, USA
(Continue reading)

Permalink | Reply |

Gmane