- From: <bugzilla@jessica.w3.org>
- Date: Mon, 06 Jan 2014 11:25:02 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24113 --- Comment #4 from Abel Braaksma <abel.braaksma@xs4all.nl> --- Apologies for being unclear, but it is not that the error is not there, it is that the XTDE0865 and XTDE0835 cover different situations, and it is that different situation (the xmlns namespace) that is covered by this test. Error XTDE0835 (in REC): It is a non-recoverable dynamic error if the effective value of the namespace attribute [of the xsl:element instruction] is not in the lexical space of the xs:anyURI data type. Error XTDE0865 (in REC): It is a non-recoverable dynamic error if the effective value of the namespace attribute [of the xsl:attribute instruction] is not in the lexical space of the xs:anyURI data type. Error XTDE0835 (in Erratum): It is a non-recoverable dynamic error if the string value of the new namespace node is not valid in the lexical space of the data type xs:anyURI, or if it is the string http://www.w3.org/2000/xmlns/. It is the additional "or if it is the string http://www.w3.org/2000/xmlns/" that causes the ambiguity, as that part is not included for XTDE0865. Note also the difference in wording, the Erratum talks of "namespace node" for XTDE0835, but the REC talks about "namespace attribute". Not a big difference though. In XSLT 3, both errors use the wording "namespace attribute". Looking further, this same ambiguity applies to error XTDE0905 (creating namespace nodes): XSLT 2.0, nor erratum, mentions the exception for the xmlns namespace, while XSLT 3.0 does mention it. There's currently no test that creates the xmlns namespace with the xsl:namespace instruction. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 6 January 2014 11:25:06 UTC