<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle">P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body fPStyle="1" ocsi="0">
<div style="FONT-FAMILY: Tahoma; DIRECTION: ltr; COLOR: #000000; FONT-SIZE: 13px">
<div>I'm stating my opinion of recent on-list discussion. That doesn't mean that I'm right or that wording will change (though it sounds like I hope it would, but I haven't looked at the latest copy recently.)</div>
<div> </div>
<div>-Shawn</div>
<div style="FONT-FAMILY: Times New Roman; COLOR: #000000; FONT-SIZE: 16px">
<hr tabindex="-1">
<div style="DIRECTION: ltr" id="divRpF267739"><font color="#000000" size="2" face="Tahoma"><b>From:</b> Wil Tan [wil@cloudregistry.net]<br>
<b>Sent:</b> Sunday, July 26, 2009 12:06 AM<br>
<b>To:</b> Shawn Steele<br>
<b>Cc:</b> IDNA update work<br>
<b>Subject:</b> Re: Two-step mapping<br>
</font><br>
</div>
<div></div>
<div>Shawn,
<div><br>
</div>
<div>By that, you mean this wording will likely go away?</div>
<div>Thanks.</div>
<div><br>
</div>
<div>=wil<br>
<br>
<div class="gmail_quote">On Sun, Jul 26, 2009 at 4:18 PM, Shawn Steele <span dir="ltr">
<<a href="mailto:Shawn.Steele@microsoft.com" target="_blank">Shawn.Steele@microsoft.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div>
<div style="FONT-FAMILY: Tahoma; DIRECTION: ltr; COLOR: #000000; FONT-SIZE: 13px">
<div>I believe the WG was moving in the direction of a consistent mapping.</div>
<div> </div>
<div>- Shawn</div>
<div style="FONT-FAMILY: Times New Roman; COLOR: #000000; FONT-SIZE: 16px">
<hr>
<div style="DIRECTION: ltr"><font color="#000000" size="2" face="Tahoma"><b>From:</b>
<a href="mailto:idna-update-bounces@alvestrand.no" target="_blank">idna-update-bounces@alvestrand.no</a> [<a href="mailto:idna-update-bounces@alvestrand.no" target="_blank">idna-update-bounces@alvestrand.no</a>] on behalf of Wil Tan [<a href="mailto:wil@cloudregistry.net" target="_blank">wil@cloudregistry.net</a>]<br>
<b>Sent:</b> Saturday, July 25, 2009 10:21 PM<br>
<b>To:</b> IDNA update work<br>
<b>Subject:</b> Two-step mapping<br>
</font><br>
</div>
<div>
<div></div>
<div class="h5">
<div></div>
<div>The architectural principles section, in the 2nd last paragraph says:<br>
<br>
<blockquote style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0px; MARGIN: 0px 0px 0px 40px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px; BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0px">
The present version of IDNA (...) does not provide explicit mapping instructions. Instead, it assumes that the application (perhaps via an operating system input method) will do whatever mapping it requires to convert input into Unicode code points. This has
the advantage of giving flexibility to the application to choose a mapping that is suitable for its user given specific user requirements, and <i>avoids the two-step mapping</i> of the original protocol.</blockquote>
<br>
In practice, if the application were to do any mapping, it is likely to perform a two-step mapping anyway:
<div><br>
</div>
<div>1. As earlier paragraph suggests, the first step of getting the input as Unicode code points is likely the function of the input method or operating system event loop.</div>
<div>2. The application then performs its local mappings.</div>
<div><br>
</div>
<div>Perhaps it's better to say ".. the application to choose a mapping that is suitable for its user given specific user requirements, and perform it prior to using it in the registration or lookup steps of the protocol"? Or maybe I'm missing an important
point.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>=wil</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
</div>
</div>
</div>
</div>
</body>
</html>