<br><font size=2 face="sans-serif">Thank you, Doug, for preparing the way
by sending this reminder. I am using the occasion to invite participants
in this list to comment on any pending request, by sending your comment
to iso639-3@sil.org, so that they may be included in the public records
for the relevant change requests. Please include the change request
number in the subject line of the message. All the requests are listed
at http://www.sil.org/iso639-3/chg_requests.asp</font>
<br><font size=2 face="sans-serif">I see no problem with also copying any
comment to this list, if appropriate, though I leave the guidance on that
to the list moderators. Certainly a few of the change requests have already
been topics of discussion on this list in the past.</font>
<br>
<br><font size=2 face="sans-serif">Thank you in advance for your input.</font>
<br>
<br><font size=2 face="sans-serif">Joan Spanne<br>
ISO 639-3/RA<br>
SIL International<br>
7500 W Camp Wisdom Rd<br>
Dallas, TX 75236<br>
ISO639-3@sil.org</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>"Doug Ewell"
<doug@ewellic.org></b> </font>
<br><font size=1 face="sans-serif">Sent by: ietf-languages-bounces@alvestrand.no</font>
<p><font size=1 face="sans-serif">2009-11-12 11:13 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif"><ietf-languages@iana.org></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Reminder: ISO 639-3 changes are coming</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>This is just a reminder -- inspired by a false-alarm
WatchThatPage <br>
message I got today -- that ISO 639-3/RA will be reviewing the 2009 <br>
batch of change requests through December 15, and will issue a report,
<br>
probably in January, listing all the changes they have approved.<br>
<br>
This will be the first time that the annual round of ISO 639-3 changes
<br>
will directly affect the IANA Language Subtag Registry. In past years,
<br>
as part of the effort to keep draft-4645bis up to date, I kept track of
<br>
these changes myself. Now, they will be a full part of the <br>
ietf-languages change control process. Each 639-3 change that affects
<br>
the Registry will require its own proposed record and registration form,
<br>
posted to this list for a two-week review period, and will have to be <br>
submitted individually to IANA. This is the process outlined in RFC
<br>
5646 and approved by the IETF and IESG.<br>
<br>
Last year the RA approved 150 changes; the year before, 383. This
year, <br>
there are 143 pending change requests to be considered. That does
not <br>
mean the RA will necessarily approve them all, or that each approved <br>
request will map 1-to-1 with a change in the Registry, but it would not
<br>
be unrealistic to assume 100 or more changes.<br>
<br>
I just want to make sure that everyone is aware this workload is coming,
<br>
probably about two months from now, and that we don't treat it as some
<br>
sort of sudden, unexpected anomaly and propose ad-hoc rule changes to <br>
work around it. It is the way of our future, once a year.<br>
<br>
--<br>
Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org<br>
RFC 5645, 4645, UTN #14 | ietf-languages @ http://is.gd/2kf0s
<br>
<br>
_______________________________________________<br>
Ietf-languages mailing list<br>
Ietf-languages@alvestrand.no<br>
http://www.alvestrand.no/mailman/listinfo/ietf-languages<br>
</font></tt>
<br>