Open benibela opened 4 years ago
My first instinct was to agree with you, but I think it's correct.
Consider <svg:a xmlns:svg="zz"><svg:b svg:att="3"><svg:c/></svg:b></svg:a>
. In the final result the a
element won't have a namespace node for the svg
namespace, because it doesn't need one. The b
element will have such a namespace node, because it has an attribute in the svg namespace. The c
element will have such a namespace node, inherited from its parent element: or in the language of this paragraph, retained because an ancestor has an attribute in the svg
namespace.
(It helps to know something of the people who wrote the spec. This is almost certainly drafted by Henry Zongaro. Henry writes very precisely and rarely gets such things wrong. He also writes very concisely: he rarely says anything twice, and rarely adds any kind of gloss or note to say "yes I really meant that"; he demands that his readers pay very careful attention to every word).
XSLT and XQuery Serialization 3.1 says in 6 XHTML Output Method
Should that not be "a descendant", since ancestors are not affected by namespace nodes?