<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:Cambria;
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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Lucida Sans Unicode";
panose-1:2 11 6 2 3 5 4 2 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";}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:24.0pt;
font-family:"Times New Roman","serif";
font-weight:bold;}
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";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Cambria","serif";
color:#365F91;
font-weight:bold;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
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'>Two cents: I have a real use case for tagging content with YU
today. Motion pictures have a Country of Origin, which may be a country that no
longer exists. Country of Origin indicates the country where the producer filed
the origin certificate so it should indicate the country that existed at the
time the certificate was filed. <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'>I realize that this use case is not related to language, but in
this case suggesting CS would not be appropriate. I almost wonder if countries
should be considered "deprecated" in the traditional sense. They may
no longer be current countries of the world, but that doesn't mean that people
aren't going to continue to use these tags in appropriate ways for historical
content. If I were to represent our data properly in ISO 3166-1, I need a tag
for Bophuthatswana, which existed so briefly, it never had an ISO tag. <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'>I support removing the preferred value.<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'>Regards,<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'>Karen Broome<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>
<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>Phillips,
Addison<br>
<b>Sent:</b> Saturday, February 28, 2009 8:56 AM<br>
<b>To:</b> CE Whitehead; ietf-languages@iana.org<br>
<b>Subject:</b> RE: Proposal to remove Preferred-Value field for region YU in
LTRU<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>It is always possible to add a comment.<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'>As for the issue of countries that separate, there is no reason
that I can see to address it further in any draft, past or future, of BCP 47.
When new countries are formed, they are always formed from all or part of an
old region (even Antarctica has a code). UN M.49 and ISO 3166-1 assign any new
regions codes, which we use as subtags. There are quite detailed and clear
rules in the current RFC for how this is to be done.<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'>The P-V pointer is mainly useful for regions when a region
changes its name (and associated code) but not its borders or “identity”. This
*<b>is</b>* what happened when the then Yugoslavia changed its identity, hence
the P-V. But since CS is defunct and since YU itself had a “larger” meaning
(which is more familiar than the later meaning and is not part of remote
history), it seems reasonable to make it revert to its older meaning by
removing the P-V. Tag canonicalization will not suffer as a result, which is
reasonable.<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'>Addison<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>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Lucida Sans Unicode","sans-serif";
color:#1F497D'>Addison Phillips<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Lucida Sans Unicode","sans-serif";
color:#1F497D'>Globalization Architect -- Lab126<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Lucida Sans Unicode","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Lucida Sans Unicode","sans-serif";
color:#1F497D'>Internationalization is not a feature.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Lucida Sans Unicode","sans-serif";
color:#1F497D'>It is an architecture.<o:p></o:p></span></p>
</div>
<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>CE Whitehead<br>
<b>Sent:</b> Saturday, February 28, 2009 7:36 AM<br>
<b>To:</b> ietf-languages@iana.org<br>
<b>Subject:</b> Proposal to remove Preferred-Value field for region YU in LTRU<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'><br>
Hi. Considering the current rule, which Doug has reminded of, that we
need to have a subtag's preferred value point to whatever it points to points
to,<br>
instead of forcing readers/implementations to follow a chain, at this point I
support removing the preferred-value and adding a comment as soon as it becomes
possible to add a comment.<o:p></o:p></span></p>
<h1><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Tex Texin
</span><span style='font-family:"Verdana","sans-serif"'><a
href="mailto:ietf-languages@alvestrand.no?Subject=Proposal%20to%20remove%20Preferred-Value%20field%20for%20region%20YU%20in%20LTRU&In-Reply-To=3D93119FB2F84366B464232A9BC52C9C@DGBP7M81"
title="Proposal to remove Preferred-Value field for region YU in LTRU"><span
style='font-size:10.0pt'>textexin at xencraft.com </span></a><br>
</span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Fri
Feb 27 21:55:22 CET 2009 </span><span style='font-family:"Verdana","sans-serif"'><o:p></o:p></span></h1>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><o:p> </o:p></span></p>
<pre>> 8) Separate topic- The number of countries in the world seems to grow. This suggests to me that regions being subdivided is not going to be a rare event. Perhaps there should be a mechanism to indicate subtags that have later been split, so instead of one preferred value, there is a way to indicate that a tag has been deprecated in favor of two or more possible values.<o:p></o:p></pre><pre><span
style='font-family:"Verdana","sans-serif"'>However, I do think Tex's point is good here; the issue of countries that separate should be addressed in the next draft of RFC 4646, but I agree we cannot address this at this time.</span><o:p></o:p></pre><pre><span
style='font-family:"Verdana","sans-serif"'>Hopefully a comment will be sufficient for the interim.</span><o:p></o:p></pre><pre><span
style='font-family:"Verdana","sans-serif"'>--C. E. Whitehead</span><o:p></o:p></pre><pre><span
style='font-family:"Verdana","sans-serif"'><a
href="mailto:cewcathar@hotmail.com">cewcathar@hotmail.com</a><span
class=MsoHyperlink><o:p></o:p></span></span></pre><pre>> tex<o:p></o:p></pre><pre
style='margin-bottom:12.0pt'><o:p> </o:p></pre></div>
</div>
</body>
</html>