RE: Processing XML 1.1 documents with XML Schema 1.0 processor
> In that case, I could choose between xs1.0:token and xs1.1:token by > assigning the right namespace URIs to these prefixes. > It seems to me that XML Schema Part 2 describes types such as Name and NCName by intent rather than by extent: that is, it says that they are designed to hold XML names, rather than that they permit a given set of characters. Even the patterns that define them in the S2S use the metacharacters \i and \c which are defined by reference to the XML specification. In the case of character classes mapped to Unicode properties, the spec is explicit that if Unicode changes, the definition of the character classes changes too. Therefore, it doesn't seem an unreasonable extrapolation to say that \i and \c should evolve in meaning as the base spec evolves. With all these things, I think one has to ask what is the approach that causes the least amount of pain to the average user. Asking everyone to change a namespace URI so that a few users can identify clearly whether or not their patterns are intended to match Ethiopian letters isn't a net win. Michael Kay http://www.saxonica.com/
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format