<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;}
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";}
span.EmailStyle18
{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'>If you deprecate X in the example below and not Y, can you give
me an example of the IANA Registry Record for this scenario?<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<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:07 PM<br>
<b>To:</b> Broome, Karen<br>
<b>Cc:</b> Frank Ellermann; 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'>There is no structure in 4646
or 4646bis for deprecating a prefix X for a subtag Y. However, the same effect
would be achieved by just deprecating X, so I don't think we need such
structure.<br>
<br clear=all>
Mark<br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal>On Mon, Aug 4, 2008 at 3:57 PM, Broome, Karen <<a
href="mailto:Karen_Broome@spe.sony.com">Karen_Broome@spe.sony.com</a>>
wrote:<o:p></o:p></p>
<div>
<div>
<p><span style='font-size:11.0pt;color:#1F497D'>Hmm. But deprecation occurs on
the entire record. Is there a way to indicate that a single prefix is
deprecated but not the tag? If we can add prefixes later, we ought to be able
to deprecate them too. But I'm not sure how we'd do this in the current
structure.</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'>Karen</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<div style='border:none;border-left:solid windowtext 1.5pt;padding:0in 0in 0in 4.0pt;
border-color:-moz-use-text-color -moz-use-text-color -moz-use-text-color blue'>
<div>
<div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;
border-color:-moz-use-text-color -moz-use-text-color'>
<p><b><span style='font-size:10.0pt'>From:</span></b><span style='font-size:
10.0pt'> <a href="mailto:ietf-languages-bounces@alvestrand.no" target="_blank">ietf-languages-bounces@alvestrand.no</a>
[mailto:<a href="mailto:ietf-languages-bounces@alvestrand.no" target="_blank">ietf-languages-bounces@alvestrand.no</a>]
<b>On Behalf Of </b>Mark Davis<br>
<b>Sent:</b> Monday, August 04, 2008 3:53 PM<br>
<b>To:</b> Frank Ellermann<o:p></o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt'><br>
<b>Cc:</b> <a href="mailto:ietf-languages@alvestrand.no" target="_blank">ietf-languages@alvestrand.no</a><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><b><span style='font-size:10.0pt'>Subject:</span></b><span
style='font-size:10.0pt'> Re: LANGUAGE SUBTAG REGISTRATION FORM: pinyin<o:p></o:p></span></p>
</div>
</div>
</div>
<p> <o:p></o:p></p>
<div>
<p style='margin-bottom:12.0pt'>No. According to the RFC, we can add other
prefixes later.<br>
<br clear=all>
Mark<o:p></o:p></p>
<div>
<div>
<div>
<p>On Mon, Aug 4, 2008 at 12:21 PM, Frank Ellermann <<a
href="mailto:nobody@xyzzy.claranet.de" target="_blank">nobody@xyzzy.claranet.de</a>>
wrote:<o:p></o:p></p>
<div>
<p style='margin-bottom:12.0pt'>Randy Presuhn wrote:<br>
<br>
> "why didn't they use '-pinyin'?"<o:p></o:p></p>
</div>
<p>Just a theoretical thought, if we take -pinyin with prefix<br>
zh-Latn- now there's no way to get rid of the prefix later.<br>
<br>
So if folks later want "pinyin" with prefix cmn-Latn- and<br>
others, but without zh-Latn-, they'd be forced to invent<br>
a new variant, say -pinyin2, and that would allow them to<br>
deprecate -pinyin in favour of -pinyin2.<br>
<br>
If that is exactly what you want (later, when cmn exists),<br>
you could use -pinyin1 now, and deprecate it in favour of<br>
the later "real" -pinyin with the "real" prefix cmn-Latn-<br>
instead of the slightly "unreal" zh-Latn-pinyin1 possible<br>
today.<br>
<span style='color:#888888'><br>
Frank</span><o:p></o:p></p>
<div>
<div>
<p><br>
_______________________________________________<br>
Ietf-languages mailing list<br>
<a href="mailto:Ietf-languages@alvestrand.no" target="_blank">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> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>