<span class="Apple-style-span" style="font-family: Garamond; "><div style="margin-top: 0px; margin-bottom: 0px; "><h3 style="font-size: 12pt; "><font size="2">BackwardCompatible Maintanence</font></h3><h3 style="font-size: 12pt; ">
<span style="font-weight: normal; "><font size="2">Changes to BackwardCompatible are a completely different beast than adjustments to PVALID and DISALLOWED. The latter we can hope to never happen. But changes to BackwardCompatible MUST be done to preserve backwards compatibility, it is not an option! And we know that there is a non-zero likelyhood that this will happen with each Unicode version (every year or so).</font></span></h3>
<h3 style="font-size: 12pt; "><span style="font-weight: normal; "><font size="2">The BackwardCompatible list, like the Context Rules Registry, should be under the aegis of IANA, with precise and strict instructions to add exactly (all and only) those characters necessary to preserve backwards compatibility with each new version of Unicode. This is not a new concept: BCP 47 (RFC 4646) has a section describing exactly what to do with each new version of a source ISO standard. The textual changes to do this are small, and I can supply suggested text.</font></span></h3>
</div><div style="margin-top: 0px; margin-bottom: 0px; "><b>Minor</b></div><div style="margin-top: 0px; margin-bottom: 0px; "><br></div><div style="margin-top: 0px; margin-bottom: 0px; ">This document uses different reference names for the same documents, eg [TR15]. All of the IDNA2008 documents should use the same notation for common references.</div>
<div><br></div></span>Mark<br>