- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 11 Dec 2009 13:33:04 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8477 Summary: [XSLT 2.0] lang attribute of xsl:sort and xsl:number Product: XPath / XQuery / XSLT Version: Recommendation Platform: PC OS/Version: Windows NT Status: NEW Severity: normal Priority: P2 Component: XSLT 2.0 AssignedTo: mike@saxonica.com ReportedBy: mike@saxonica.com QAContact: public-qt-comments@w3.org For both xsl:sort and xsl:number we make two statements about the lang attribute: (a) we give the format in the syntax template as lang? = { nmtoken } (b) we say that the range of permitted values is the same as for xml:lang, with a reference to the XML specification These are inconsistent: the xml:lang attribute allows a zero-length string, whereas nmtoken does not. Also, the reference to xml:lang could be taken as implying that the language must be present in the various lists of registered languages, rather than merely conforming to the correct syntax. I would suggest that (i) we change the syntax template to lang? = { xs:language? } (ii) rather than referring to xml:lang, we say that the value must either be a zero-length string or a string in the value space of xs:language. This makes it clear that the constraint is purely syntactic. (iii) we specify that the zero length string has the same effect as omitting the lang attribute. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Friday, 11 December 2009 13:33:13 UTC