<span>We could restrict the table to changing only with versions of Unicode that add characters. Those periods would vary from about one to two years. For some recent history, that would have been:<br><br></span><span>Unicode
3.2: March, 2002<br>
</span><span>Unicode 4.0: April, 2003<br></span><span>Unicode 4.1: March, 2005<br></span><span>Unicode 5.0: July, 2006<br>Unicode 5.1: ~Q1, 2008<br><br></span><span>And the property would only add characters, never remove them.
<br><br>Mark<br></span><a name="Unicode_3_2_0"><br></a><a name="Unicode_4_1_0"></a><div><span class="gmail_quote">On 1/31/07, <b class="gmail_sendername">Harald Tveit Alvestrand</b> <<a href="mailto:harald@alvestrand.no">
harald@alvestrand.no</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br>--On 14. desember 2006 18:24 -0800 Kenneth Whistler <
<a href="mailto:kenw@sybase.com">kenw@sybase.com</a>> wrote:<br><br>> The *table* itself should unambiguously be defined as<br>> the list of characters appropriate for inclusion in<br>> IDNA. IDNAInclusion.txt
(or whatever name you like).<br><br>And how often do you believe this table would change?<br><br>Once a month?<br>Once a year?<br>Once a decade?<br><br>I think I disagree violently with you, but that is because I understand you
<br>as saying that the table would change "once a decade". If it changes once a<br>month, the "unambiguous" table is a thin illusion papered over a tri-state<br>model.<br><br> Harald<br><br>
<br>_______________________________________________<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">
http://www.alvestrand.no/mailman/listinfo/idna-update</a><br></blockquote></div><br><br clear="all"><br>-- <br>Mark