Print

Print


> From: ISO 639 Joint Advisory Committee [mailto:[log in to unmask]] On
> Behalf Of Håvard Hjulstad

> I think that this will have to be an important part of the maintenance
> of 639-2 (and other defined subsets of 639) in the future. All this
> needs to be put into place when 639-5 is finished. I think we can live
> with an "imperfect" solution in the meantime.

One of the ISO 639 customers with an ISO 639 implementation is IETF (IETF Language Tags), and the working group working on revising that spec to incorporate 639-3 asked me if I could get this matter resolved within the JAC. They have referenced 639-2 in the past, and need to continue to do so because the 639-2 collections have been supported. (There is the option to change to 639-5 in the future, but that is outside the plan of current work.) The instability caused by "(Other)" for some 639-2 collections is of concern for them, so they'd like to see that change in 639-2 sooner than later. (If it were done now, that would allow them to cover the stability issues in this version.)



Peter