29866 2016-09-23 13:19:37 +0000 [XSLT30] EQName type in XSD for XSLT 3.0 is too lenient 2016-09-28 20:33:55 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XSLT 3.0 Candidate Recommendation PC Windows NT RESOLVED FIXED P2 normal --- 1 abel.braaksma mike public-qt-comments oldest_to_newest 127515 0 abel.braaksma 2016-09-23 13:19:37 +0000 After a long discussion today with Charles Foster we concluded that the base type for all EQNames, aptly named xsl:EQName, allows for illegal names. The current definition is: <xs:union memberTypes="xs:NCName xs:QName"> <xs:simpleType> <xs:restriction base="xs:token"> <xs:pattern value="Q\{.*\}\i\c*"/> </xs:restriction> </xs:simpleType> </xs:union> this allows for "Q{x}a:b:c", which is illegal. Or even "Q{x}:::y:::". A possible solution is to disallow the ":", but using a subtraction class: <xs:union memberTypes="xs:NCName xs:QName"> <xs:simpleType> <xs:restriction base="xs:token"> <xs:pattern value="Q\{.*\}[\i-[:]][\c-[:]]*"/> </xs:restriction> </xs:simpleType> </xs:union> I've tested this definition and it seems correct. 127516 1 abel.braaksma 2016-09-23 13:22:45 +0000 As an aside, an EQName of the form "Q{x{}" is illegal too (according to XPath), but valid according to this type. This can be enforced by changing this further to: <xs:pattern value="Q\{[^{}]*\}[\i-[:]][\c-[:]]*"/> 127585 2 mike 2016-09-28 20:33:55 +0000 Thank you, this correction has been applied.