I believe that none of the current CONTEXTO characters are really required to be CONTEXTO, and all should be simply PVALID. Here are my recommendations in detail: A. HYPHENThe rule on HYPHEN is unnecessary, since it is a requirement of the DNS system anyway; this is completely redundant. So remove from Tables:
Note that in Protocol we have:
4.2.3.1. Consecutive Hyphens
The Unicode string MUST NOT contain "--" (two consecutive hyphens) in
the third and fourth character positions. The corresponding Lookup restriction is missing from Protocol and should be added. B. ARABIC-INDIC DIGITSThe rule on these overlaps with Bidi, and would be simpler and more appropriately moved there, since these are all only of concern with Bidi processing. So remove:
5. If an EN is present, no AN may be present, and vice versa.
To: 5.
If an EN is present, no AN or EXTENDED ARABIC-INDIC digit
(U+0660..U+0669) may be present. If an AN is present, no EXTENDED
ARABIC-INDIC digit (U+0660..U+0669) may be present.
C. Other CONTEXTORemove the other CONTEXTO cases. These consist of only the following 6 characters, and there is no particular problem with making them all simply PVALID in the Exceptions table.
|