- From: <bugzilla@jessica.w3.org>
- Date: Thu, 27 Mar 2014 00:13:53 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25149 --- Comment #6 from C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com> --- (In reply to Michael Kay from comment #3) > Correction. I think I was mistaken that the code is inconsistent with the > prose. I forgot about the rules for namespace inheritance. [...] OK, but now that the issue has come up, you have to explain it to me and we should get it in writing (either in the text of the spec or in a comment in the source explaining why everything is OK). I had overlooked that part of the prose, and no matter how the ambiguity is resolved, it was not obvious to me at first glance how either the original 3.0 or the revised 2.0 stylesheet avoid losing the namespace declaration for the 'svg' namespace, in your example. A few minutes (or more) of leafing through the serialization spec and the XSLT spec make me conjecture that the reason no code is needed for the case described is the rule in 5.7.3 of XSLT 2.0 (5.8.3 of XSLT 3.0) that says, essentially, that the namespace node for svg cannot be dropped here, because the svg:x attribute is copied out without changing its name. If some other rationale explains your conclusion, please record it. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 27 March 2014 00:13:54 UTC