<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;}
-->
</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'>Cherry picking whether or not to include an entity from a source
standard is one thing, and something LTRU had consensus on avoiding.<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'>Cherry picking on decisions regarding deprecation is, IMO, quite
a different matter.<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>
<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"'>
gerard.meijssen@gmail.com [mailto:gerard.meijssen@gmail.com] <b>On Behalf Of </b>Gerard
Meijssen<br>
<b>Sent:</b> Sunday, July 12, 2009 1:04 AM<br>
<b>To:</b> Peter Constable<br>
<b>Cc:</b> ietf-languages@iana.org<br>
<b>Subject:</b> Re: Anomaly in upcoming registry<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>Hoi,<br>
Cherry picking standards seems to me a way that will confuse people. When a
work like this depends on standards, you make it impossible for people to
understand how and why this is true. It would also allow people to make their
own choices. They can do so because by removing the standard from the standard,
this work is either a standard in its own right and consequently it deserves no
more credibility then that it gives to other standards it says it relies on.<br>
Thanks,<br>
GerardM<o:p></o:p></p>
<div>
<p class=MsoNormal>2009/7/9 Peter Constable <<a
href="mailto:petercon@microsoft.com">petercon@microsoft.com</a>><o:p></o:p></p>
<p class=MsoNormal>In this case I agree with the conclusion -- we don't want to
collapse these.<br>
<br>
On the other hand, I'm not completely in agreement with your premise that this
is solely ISO 639's call and that we have no say. We could choose to collapse
these even if ISO 639 doesn't if we think that is the right thing to do for
consumers of the LST registry. If ISO 639 chose to collapse these, we could
choose to leave them as is if we think that is the right thing to do for
consumers of the LST registry.<br>
<br>
There are times when we simply want to follow what ISO does and not
"second guess"; there are also times when we don't want to be subject
to everything ISO may do -- such provisions are even baked into BCP 47.<br>
<br>
IMO, if we think that sh not be deprecated for consumers of the LST registry,
then we should go ahead and make that decision, regardless of whatever ISO
639-1 or ISO 639-3 may do.<br>
<span style='color:#888888'><br>
<br>
<br>
Peter</span><o:p></o:p></p>
<div>
<p class=MsoNormal><br>
<br>
-----Original Message-----<br>
From: <a href="mailto:ietf-languages-bounces@alvestrand.no">ietf-languages-bounces@alvestrand.no</a>
[mailto:<a href="mailto:ietf-languages-bounces@alvestrand.no">ietf-languages-bounces@alvestrand.no</a>]
On Behalf Of Doug Ewell<br>
Sent: Wednesday, July 08, 2009 10:52 PM<br>
To: <a href="mailto:ietf-languages@iana.org">ietf-languages@iana.org</a><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>Subject: Re: Anomaly in
upcoming registry<o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal>Randy Presuhn <randy underscore presuhn at mindspring dot
com> wrote:<br>
<br>
> Where I *don't* want this discussion to go is down the path of whether<br>
> any of the languages formerly known as Serbo-Croatian should be<br>
> collapsed, as Romanian and Moldovan (rightly) were.<br>
<br>
Agreed. It's not our call, it's ISO 639's call.<br>
<br>
--<br>
Doug Ewell * Thornton, Colorado, USA * RFC 4645 *
UTN #14<br>
<a href="http://www.ewellic.org" target="_blank">http://www.ewellic.org</a><br>
<a href="http://www1.ietf.org/html.charters/ltru-charter.html" target="_blank">http://www1.ietf.org/html.charters/ltru-charter.html</a><br>
<a href="http://www.alvestrand.no/mailman/listinfo/ietf-languages"
target="_blank">http://www.alvestrand.no/mailman/listinfo/ietf-languages</a>
ˆ<br>
<br>
_______________________________________________<br>
Ietf-languages mailing list<br>
<a href="mailto:Ietf-languages@alvestrand.no">Ietf-languages@alvestrand.no</a><br>
<a href="http://www.alvestrand.no/mailman/listinfo/ietf-languages"
target="_blank">http://www.alvestrand.no/mailman/listinfo/ietf-languages</a><br>
_______________________________________________<br>
Ietf-languages mailing list<br>
<a href="mailto:Ietf-languages@alvestrand.no">Ietf-languages@alvestrand.no</a><br>
<a href="http://www.alvestrand.no/mailman/listinfo/ietf-languages"
target="_blank">http://www.alvestrand.no/mailman/listinfo/ietf-languages</a><o:p></o:p></p>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>