That's not my point at all -- it is that syntax is not keeping us from doing this: <span class="q">relevance, suitability, and stability are.<br><br>Mark<br></span><br><div><span class="gmail_quote">On 8/26/07, <b class="gmail_sendername">
Doug Ewell</b> <<a href="mailto:dewell@roadrunner.com">dewell@roadrunner.com</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;">
Mark Davis <mark dot davis at icu dash project dot org> wrote:<br><br>> I agree with you that the syntax couldn't be incorporated directly,<br>> but we could work around it (not in this group, but in the LTRU
<br>> group). For example, we could say that variants of the form SUBxxxxx<br>> with a prefix containing a region code were reserved for ISO 3166-2<br>> codes. The key issues are relevance, suitability, and stability.
<br><br>We could do this in LTRU, it is true, but I sincerely hope we don't.<br>It's an ugly hack to get around the syntactical problem, and does<br>nothing to solve the stability and free-availability problems.<br>
<br>--<br>Doug Ewell · Fullerton, California, USA · RFC 4645 · UTN #14<br><a href="http://users.adelphia.net/~dewell/">http://users.adelphia.net/~dewell/</a><br><a href="http://www1.ietf.org/html.charters/ltru-charter.html">
http://www1.ietf.org/html.charters/ltru-charter.html</a><br><a href="http://www.alvestrand.no/mailman/listinfo/ietf-languages">http://www.alvestrand.no/mailman/listinfo/ietf-languages</a><br><br>_______________________________________________
<br>Ietf-languages mailing list<br><a href="mailto:Ietf-languages@alvestrand.no">Ietf-languages@alvestrand.no</a><br><a href="http://www.alvestrand.no/mailman/listinfo/ietf-languages">http://www.alvestrand.no/mailman/listinfo/ietf-languages
</a><br></blockquote></div><br><br clear="all"><br>-- <br>Mark