<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'>Notes in line:<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"'>
mark.edward.davis@gmail.com [mailto:mark.edward.davis@gmail.com] <b>On Behalf
Of </b>Mark Davis<br>
<b>Sent:</b> Monday, August 04, 2008 4:04 PM<br>
<b>To:</b> Broome, Karen<br>
<b>Cc:</b> Phillips, Addison; Kent Karlsson; ietf-languages@alvestrand.no<br>
<b>Subject:</b> Re: LANGUAGE SUBTAG REGISTRATION FORM: pinyin<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'>I think you see some Dark
Conspiracy where there is none. My strong intention, shared I'm sure by others
on this list like John, is to add the prefixes zh-cmn and cmn, once those are
available.<span style='color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Karen: Not a dark conspiracy,
but a strong difference of opinion perhaps based on the use cases we represent:
identification of content in tightly defined industry protocols vs. fuzzy retrieval
of historical content across a wide variety of industries and content creators.
Of course, this RFC needs to serve us both.<br>
</span><br>
zh-guoyu cannot be added as a prefix, since zh-guoyu-pinyin would be illegal.<br>
zh-cmn also cannot be added as a prefix, under RFC4646<span style='color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Karen: Point taken. I wasn't
suggesting that zh-cmn be added under RFC 4646 for this variant tag, but you're
right about Guoyu.</span><br>
<br>
Remember, prefixes are a guide for good usage, to indicate that other values
would be *inappropriate*. zh-cmn-Latn-pinyin makes sense, as does
zh-Latn-pinyin. But da-pinyin *doesn't*. It is cases like the latter than the
prefixes are designed to discourage.<span style='color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Karen: Right. I think "zh-pinyin"
is bad usage. Like other "zh" tags, this tag has multiple meanings
and could be easily misinterpreted. <o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>And zh is not deprecated in
RFC4646, nor is it deprecated in the current text of RFC4646bis, nor can I
forsee that it would ever be deprecated.<span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Karen: Mark, I don't think you
have as much agreement here as you think you do -- even those that don't
support deprecation now may support deprecation in the future when they are
dealing with the more balanced percentages of Cantonese and Mandarin found in
audio contexts and seeing these variants expressed in a wide variety of ways.
In not deprecating it, we are giving this tag a special privilege not given to
other tags: allowing more than one preferred variant. Every exception to the
rule makes this work harder and harder to explain to those who are trying to
use it.<o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>We should consider
deprecating "zh" in the future because best practice in all tagging
is to use unambiguous tags. Deprecation does not mean that this tag cannot be
used; it means that it is not preferred and there is a newer, better tag that
should be used instead. I do not think using "zh" continues to be a
wise choice for content creators who want to make sure their tags are
interpreted correctly downstream. <o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Of course, search engines
will need to be aware of this tag for a long time to come, but I believe we are
failing to do our job if we do not warn content creators that today's Internet
is an audiovisual experience and in this context, "zh" is bad choice
for a tag. The percentages you see in the public text you analyzed would not
hold true for private audio uses your bots can't possibly find. <o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Regards,<o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Karen Broome<o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>