<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=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* 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.gmailquote
{mso-style-name:gmail_quote;}
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'>For the imperfect-knowledge scenario you describe where the
process ends with an “I don’t know” conclusion, und is the appropriate tag, not
mis.<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"'> Mark Davis
[mailto:mark.davis@icu-project.org] <br>
<b>Sent:</b> Friday, April 13, 2007 1:05 PM<br>
<b>To:</b> Randy Presuhn<br>
<b>Cc:</b> ietf-languages@alvestrand.no; ltru@lists.ietf.org<br>
<b>Subject:</b> Re: [Ltru] Re: "mis" update review request<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>I agree with you about the
stability issue.<br>
<br>
I think part of the problem in communicating about this is that people may have
somewhat different usage scenarios in mind. If you think of tagging as
something that a person does with content that they originate or have control
over, then it is (probably) fairly straightforward for that person to tag as
specifically as possible. <br>
<br>
Another scenario is where you have incoming content, and you need to tag it for
use by other components. This might be done, for example, in a search engine,
where you fetch and process a page, and use that information later in doing
searches. The tag serves to communicate language between the different
components. <br>
<br>
In that case, you have far from perfect information about the content: what you
have being typically the result of some level statistical analysis, plus other
factors about the document. You need to tag with as much information as you
have, *but no more*. It is in that case where you need to have the tags that
indicate some level of imperfect knowledge about the source, such as "I
have no idea what this is", or "It looks like linguistic content, but
I don't know which language", or "it doesn't look like linguistic
content". (You may also have more detailed knowledge, like that some
document appears to have 70% English content (probability 95%) and 20% French
content (probability 65%)). <br>
<br>
Both scenarios are equally valid use cases for BCP 47 (in fact, as a percentage
of data flow on the web, I'd wager strongly that the second scenario completely
swamps the first).<br>
<br>
Mark<o:p></o:p></p>
<div>
<p class=MsoNormal><span class=gmailquote>On 4/13/07, <b>Randy Presuhn</b> <<a
href="mailto:randy_presuhn@mindspring.com">randy_presuhn@mindspring.com</a>>
wrote:</span><o:p></o:p></p>
<p class=MsoNormal>Hi -<br>
<br>
The thing that bothers me about the comment "A collection of languages
which<br>
don't belong to any other collection" is that it isn't compatible with the<br>
possibility that one or more of those languages might eventually be included <br>
in another (possibly new) collection. If that langauage were left in
the mis<br>
collection as well, the comment would be incorrect. If the language
were<br>
removed from the mis collection, stability goes out the
window. Either way, <br>
changing the comment wouldn't help the situation.<br>
<br>
However, unlike some other collections, I find it very difficult to imagine<br>
a case where "mis" would be useful in tagging
data. Without a clear use case <br>
for "mis" in constructing a language tag, perhaps we could conclude
that this<br>
whole debate is really academic, and that no action is needed.<br>
<br>
Randy<br>
<br>
<br>
_______________________________________________ <br>
Ltru mailing list<br>
<a href="mailto:Ltru@ietf.org">Ltru@ietf.org</a><br>
<a href="https://www1.ietf.org/mailman/listinfo/ltru">https://www1.ietf.org/mailman/listinfo/ltru</a><o:p></o:p></p>
</div>
<p class=MsoNormal><br>
<br clear=all>
<br>
-- <br>
Mark <o:p></o:p></p>
</div>
</body>
</html>