Tighten the definition of the query language binding attribute about schematron-enhancement-proposals HOT 5 OPEN

Because it makes one less thing the user has to remember. And why should XML's case sensitivity for names apply to attribute values (or data content), which have nothing to do with XML names?

I am not sure of the difference you are making getween an identifier and a name. Whether some attribute value is interpreted by its application as case-sensitive or not has nothing to do with XML rules. For example, <eg email="[[email protected]](mailto:[email protected])" /> <eg email="[email protected]" /> are the same. Bevause the application decides, not the XML rules for names. It is the same as, for example, how qnames are interpreted in content and values: is it XSD 1.0 style, is it the revised XSD style (as in xsd:assert IIRC), is it xmlns: style, is it Schematron style? is it something else suitable? Or take RFC 822 s2.0: All media type values, subtype values, and parameter names as defined are case-insensitive. However, parameter values are case-sensitive unless otherwise specified for the specific parameter. XML make no assumption or requirement that attribute values or data content are case-insensitive. Even if a DTD says an attribute value is a NAME token, that does not mean that the value is case-sensitive after XML processing in the application. (Schematron is premised on the idea that the types provided by DTDs and XSD are not good enough, and that they don't provide a standard place to explain what the values are supposed to be.) It is the same as trimming off leading and trailing whitespace. Just because an attribute value gets specified in a document with some leading space does not mean that the application cannot strip leading and trailing spaces before interpreting the value. B.t.w. The reason XML is case-insensitive for names (and many other standards too) is because there is no way to solve the Turkish "I" mapping problem (in Turkish, the lowercase of I is dotless i and the uppercase of i is dotted I. without making XML parsing locale-dependent. It is not bevause of some technical excellence in case sensitivity. Otherwise, we would have kept SGML/HTML's default. See https://en.m.wikipedia.org/wiki/Dotted_and_dotless_I

But what possible difficulty does it cause? You can write in lower case by habit and not have a problem. Unless you write something that reads Schatron stylesheets, it has zero impact.