<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I was looking through some of the change requests, and was thrilled at what I saw: a process of refinement in understanding of the world’s languages with input from a variety of sources and all publicly documented. I’m sure it’s not unlike what has long happened with Ethnologue, though I wonder if standardization in ISO 639 hasn’t increased public awareness of the catalogue (e.g., the Mong input seems to have been arisen because of ISO 639-3), and there wasn’t a mechanism with Ethnologue to publicly document input. And a lot of the input is providing great documentation. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>This is wonderful! Thanks for all you’ve done on this.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Peter<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> ietf-languages-bounces@alvestrand.no [mailto:ietf-languages-bounces@alvestrand.no] <b>On Behalf Of </b>ISO639-3@sil.org<br><b>Sent:</b> Friday, November 13, 2009 7:13 AM<br><b>To:</b> ietf-languages@iana.org<br><b>Subject:</b> Re: Reminder: ISO 639-3 changes are coming<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><br><span style='font-size:10.0pt;font-family:"Arial","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 <a href="mailto:iso639-3@sil.org">iso639-3@sil.org</a>, 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 <a href="http://www.sil.org/iso639-3/chg_requests.asp">http://www.sil.org/iso639-3/chg_requests.asp</a></span> <br><span style='font-size:10.0pt;font-family:"Arial","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.</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Thank you in advance for your input.</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Joan Spanne<br>ISO 639-3/RA<br>SIL International<br>7500 W Camp Wisdom Rd<br>Dallas, TX 75236<br><a href="mailto:ISO639-3@sil.org">ISO639-3@sil.org</a></span> <br><br><o:p></o:p></p><table class=MsoNormalTable border=0 cellpadding=0 width="100%" style='width:100.0%'><tr><td width="40%" valign=top style='width:40.0%;padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal><b><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>"Doug Ewell" <<a href="mailto:doug@ewellic.org">doug@ewellic.org</a>></span></b><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'> </span><br><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Sent by: <a href="mailto:ietf-languages-bounces@alvestrand.no">ietf-languages-bounces@alvestrand.no</a></span> <o:p></o:p></p><p><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>2009-11-12 11:13 PM</span> <o:p></o:p></p></td><td width="59%" valign=top style='width:59.0%;padding:.75pt .75pt .75pt .75pt'><table class=MsoNormalTable border=0 cellpadding=0 width="100%" style='width:100.0%'><tr><td valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal align=right style='text-align:right'><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>To</span><o:p></o:p></p></td><td valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'><<a href="mailto:ietf-languages@iana.org">ietf-languages@iana.org</a>></span> <o:p></o:p></p></td></tr><tr><td valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal align=right style='text-align:right'><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>cc</span><o:p></o:p></p></td><td valign=top style='padding:.75pt .75pt .75pt .75pt'></td></tr><tr><td valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal align=right style='text-align:right'><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Subject</span><o:p></o:p></p></td><td valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Reminder: ISO 639-3 changes are coming</span><o:p></o:p></p></td></tr></table><p class=MsoNormal><o:p> </o:p></p><table class=MsoNormalTable border=0 cellpadding=0><tr><td valign=top style='padding:.75pt .75pt .75pt .75pt'></td><td valign=top style='padding:.75pt .75pt .75pt .75pt'></td></tr></table></td></tr></table><p class=MsoNormal style='margin-bottom:12.0pt'><br><br><br><tt><span style='font-size:10.0pt'>This is just a reminder -- inspired by a false-alarm WatchThatPage </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>message I got today -- that ISO 639-3/RA will be reviewing the 2009 </tt><br><tt>batch of change requests through December 15, and will issue a report, </tt><br><tt>probably in January, listing all the changes they have approved.</tt><br><br><tt>This will be the first time that the annual round of ISO 639-3 changes </tt><br><tt>will directly affect the IANA Language Subtag Registry. In past years, </tt><br><tt>as part of the effort to keep draft-4645bis up to date, I kept track of </tt><br><tt>these changes myself. Now, they will be a full part of the </tt><br><tt>ietf-languages change control process. Each 639-3 change that affects </tt><br><tt>the Registry will require its own proposed record and registration form, </tt><br><tt>posted to this list for a two-week review period, and will have to be </tt><br><tt>submitted individually to IANA. This is the process outlined in RFC </tt><br><tt>5646 and approved by the IETF and IESG.</tt><br><br><tt>Last year the RA approved 150 changes; the year before, 383. This year, </tt><br><tt>there are 143 pending change requests to be considered. That does not </tt><br><tt>mean the RA will necessarily approve them all, or that each approved </tt><br><tt>request will map 1-to-1 with a change in the Registry, but it would not </tt><br><tt>be unrealistic to assume 100 or more changes.</tt><br><br><tt>I just want to make sure that everyone is aware this workload is coming, </tt><br><tt>probably about two months from now, and that we don't treat it as some </tt><br><tt>sort of sudden, unexpected anomaly and propose ad-hoc rule changes to </tt><br><tt>work around it. It is the way of our future, once a year.</tt><br><br><tt>--</tt><br><tt>Doug Ewell | Thornton, Colorado, USA | <a href="http://www.ewellic.org">http://www.ewellic.org</a></tt><br><tt>RFC 5645, 4645, UTN #14 | ietf-languages @ <a href="http://is.gd/2kf0s">http://is.gd/2kf0s</a> ­</tt><br><br><tt>_______________________________________________</tt><br><tt>Ietf-languages mailing list</tt><br><tt><a href="mailto:Ietf-languages@alvestrand.no">Ietf-languages@alvestrand.no</a></tt><br><tt><a href="http://www.alvestrand.no/mailman/listinfo/ietf-languages">http://www.alvestrand.no/mailman/listinfo/ietf-languages</a></tt></span><o:p></o:p></p></div></body></html>