- From: <bugzilla@jessica.w3.org>
- Date: Thu, 22 Oct 2015 21:10:45 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29231 --- Comment #2 from Michael Kay <mike@saxonica.com> --- I think the test results are correct. The logic is as follows: The <out> element has two namespace nodes: xsl=http://www.w3.org/2009/XSL/Transform, and f=http://impincl32/ns. The xsl:namespace-alias creates a mapping from the literal namespace URI http://impincl32/ns to the target namespace URI http://www.w3.org/2009/XSL/Transform. The spec states: <quote> When a literal result element is processed, its namespace nodes are handled as follows: * A namespace node whose string value is a literal namespace URI is not copied to the result tree. * A namespace node whose string value is a target namespace URI is copied to the result tree, whether or not the URI identifies an excluded namespace. </quote> So the namespace node f=http://impincl32/ns is not copied to the result tree (under the first rule), but the namespace node xsl=http://www.w3.org/2009/XSL/Transform is copied (under the second rule). -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 22 October 2015 21:10:47 UTC