<br><br><div class="gmail_quote">2009/7/1 Mark Davis ⌛ <span dir="ltr"><<a href="mailto:mark@macchiato.com">mark@macchiato.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Well, I agree that "loss of information" can sound drastic, but I was just repeating John's words.</blockquote><div><br>Unfortunately, this is exactly what it is.Let understand, Unicode is slightly entropic because sometimes you can print the same thing with different Unicode codepoints. This is a small problem. This can be corrected through tables. <br>
<br>The real problem is to make IDNA itself an entropic process. This means to make it a non end to end process (end to end process strives to be information neutral). Mapping at protocol level prevents any metadata to be exchanged to carry the information that has been lost in the mapping process. The necssary presentation layer does not exist in the basic internet protocol pile.<br>
<br>This is why mapping can only be carried at a place where a complementary process can send the necessary negentropy to restore the initial entry.The Internet does not supporting it: IDNA has been designed has been assigned the job. It can then be carried at application layer, but it must be carried both way, adding entropy first and restoring the correspoding negentropy.<br>
<br>This is why the Charter says that mapping must not occur at protocol level.<br><br>As a result it means that your propositions should be totally orthogonal to IDNA and IETF. They belong to the user application and can be used today. They may also be incorporated into the usage pseudo-network layer (stabilized common usage applications). Your best bet to make sure the Internet supports IDNA correctly is that you can freely change your specification and everything will continue to run smooth;This is network neutrality. <br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Perhaps less scary is just to say that case mapping (whether upper, lower, or folding) is not a reversible transformation: "McDonald", once transformed to "MCDONALD" or "mcdonald" cannot be restored without additional information. In that respect, it is similar to width transformations or others under discussion here, except that as I pointed out, it typically loses <i>more</i> semantic information than the others do.</blockquote>
<div><br>Far more scarry. McDonald is a registered trade mark. MCDONALD and mconald are probably not subject to the same constraints. This shows that billions of $ are at stake.<br><br>Elisabeth Blanconil<br><br> <br></div>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><font color="#888888">
<br clear="all">Mark<br>
<br><br></font><div class="gmail_quote"><div><div></div><div class="h5">On Tue, Jun 30, 2009 at 18:36, Elisabeth Blanconil <span dir="ltr"><<a href="mailto:eblanconil@gmail.com" target="_blank">eblanconil@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="h5">
<div class="gmail_quote">2009/6/30 "Martin J. Dürst" <span dir="ltr"><<a href="mailto:duerst@it.aoyama.ac.jp" target="_blank">duerst@it.aoyama.ac.jp</a>></span><div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
A case mapping is also a 'loss of information', but one that people clearly
want.</div></blockquote></div><div><br>Could we not phrase this differently ? Case mapping may be considered only if it does not represent a loss of information. Otherwise should we not name it "case and entropy mapping" to explain users where entropy occurs.<br>
<br>Elisabeth Blanconil<br><br><br><br><br> <br></div></div><br>
<br></div></div><div class="im">_______________________________________________<br>
Idna-update mailing list<br>
<a href="mailto:Idna-update@alvestrand.no" target="_blank">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>
<br></div></blockquote></div><br>
</blockquote></div><br>