Re: ArchForms and LPDs

For background, for readers who don't know what normalization is: consider A with an angstrom diacritical:  a legacy character set may use two one character to represent A and one character to represent combining the angstrom, or it may use one. Unicode supports both forms ( U+0041 U+0301 i.e. NFD,  and U+0058 i.e. NFC) , and they are invisible to the eye and disruptive for simple collating and string matching. 

First, to confirm the status quo: as I understand it:

• XML 1.0 (5th) says non-normatively to use NFC for 1. names: element names, attribute names, entity names, name tokens in attribute values as best practise.

• XML 1.1 "defines a set of constraints called "full normalization" on XML documents, which document creators SHOULD adhere to, and document processors SHOULD verify. Using fully normalized documents ensures that identity comparisons of names, attribute values, and character content can be made correctly by simple binary comparison of Unicode strings."  This uses NFC.
  

(My proposal for my system is that normalization of names (to NFC) is a server-side responsibility, which clients may check for: or they may build name normalization in themselves too. This only applies to tokens that are not in double quotes, not to strings or literals.   (I will update the documentation on www.schematron.com  for RAN: Random Access Notation with this. )