Re: <a href="http://tools.ietf.org/html/draft-ietf-idnabis-mappings">http://tools.ietf.org/html/draft-ietf-idnabis-mappings</a><br><br>I agree with other comments in this thread; and with all due respect to the effort put into writing the draft, I don't think it accomplishes much. The core is:<br>
<pre class="newpage"> The general algorithm that an application (or the input method<br> provided by an operating system) should use is relatively<br> straightforward and generally follows <a href="http://tools.ietf.org/html/draft-ietf-idnabis-mappings-00#section-5">section 5</a> of<br>
[<a href="http://tools.ietf.org/html/draft-ietf-idnabis-mappings-00#ref-I-D.ietf-idnabis-protocol" title=""Internationalized Domain Names in Applications (IDNA): Protocol"">I-D.ietf-idnabis-protocol</a>]:<br>
<br>...<br><br> These are the minimal mappings that an application SHOULD do. </pre>The user of SHOULD rather than must means that, for example, one still wouldn't know what a IDNAbis-conformant browser would do with href="<a href="http://xn--bersetzung-8db.de">http://Übersetzung.de</a>". Would it interpret it as <a href="http://xn--bersetzung-8db.de">übersetzung.de</a> or just fail? By having no firm requirements, it leaves the issue open, and we are no better off than if this document weren't there.<br>
<br clear="all">Mark<br>
<br><br><div class="gmail_quote">On Wed, May 27, 2009 at 12:57, Paul Hoffman <span dir="ltr"><<a href="mailto:phoffman@imc.org">phoffman@imc.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'm glad that we have a document to work from, but this document seems upside-down. The long, stuffy "architectural principles" should be an appendix, and it should be clearly labelled as "non-normative" and/or "informational". There is no way that this WG will agree on such architectural principles except by attrition (which we are getting good at, unfortunately).<br>
<br>
Similarly, putting the actual algorithm as an appendix just seems wrong.<br>
<br>
On a technical level, the algorithm is wrong in that there are characters that are legal in IDNAbis that will not make it through the algorithm. We *need* to come to agreement on the mapping of those, and we need to do so sooner rather than later.<br>
<div><div></div><div class="h5">_______________________________________________<br>
Idna-update mailing list<br>
<a href="mailto:Idna-update@alvestrand.no">Idna-update@alvestrand.no</a><br>
<a href="http://www.alvestrand.no/mailman/listinfo/idna-update" target="_blank">http://www.alvestrand.no/mailman/listinfo/idna-update</a><br>
</div></div></blockquote></div><br>