<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=utf-8">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:2050951503;
mso-list-template-ids:1934949780;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</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=Section1>
<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'>If a new forum on ISO-639 is in the offing it might be worth
giving it the scope of all of ISO-639 and not just part 3, though that is where
a lot of the discussion is at the moment. If 639 is a system of several parts then
inevitably discussion will involve the others; all the more with the eventual
arrival of 5 & 6 and recalibration (or reinvention?) of 2.<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'>On the other hand, I have to say that as one who only relatively
recently joined ietf-languages & ltru that I would almost prefer recasting
one of those to cover ISO-639. Or even to have a new larger language coding list
be mandated to replace the set (hopefully that is not too heretical). *<b>Another</b>*
list to follow is, well, yet another list to follow. And inevitably it will be
cc’d on many messages to one or more of the other lists anyway. <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'>Just thought… <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'>Don<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>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<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>Mark Davis<br>
<b>Sent:</b> Tuesday, February 13, 2007 1:24 PM<br>
<b>To:</b> Doug Ewell<br>
<b>Cc:</b> ietf-languages@iana.org; ltru@ietf.org<br>
<b>Subject:</b> Re: Macrolanguages, countries & orthographies<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<p class=MsoNormal>I wonder if there is, or is going to be, a public forum to
discuss ISO<br>
639-3 and its structure and policies. This list really isn't it; we <br>
take what the external standards give us, and synthesize and arrange.<br>
We don't directly influence what the external standards do, though there<br>
are list members who can do so indirectly.<o:p></o:p></p>
</blockquote>
<div>
<p class=MsoNormal><br>
That would be very useful. We are very dependent on the interpretation of the
codes. In particular, there is a key item that we need a response for, and that
is the temporal scope of ISO language codes. For example, we have french broken
up into fr, frm, and fro, plus various creoles. So tagging old French
data with fr is incorrect, and requesting a variant subtag to apply to fr to
indicate French of say (1100-1200) is out of scope and will be legitimately
rejected. <br>
<br>
For most other languages, on the other hand, <i>we do not have that granularity</i>.
So that means what a document that is tagged with cs (Czech) represents is
completely unspecified. We do not know what the !#$@ to do with a request. We
are faced with an unknown situation which the ISO committee doesn't respond to.
<br>
<br>
<span style='color:#1F497D'>. . .</span> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>