RE: namespace node implementation

OK, so be it. Thanks for this clarification,
and thanks also to Per Bothner who opened this debate,
without which I would have misunderstood the spec.


> Well, the design could have gone either way. We decided on this design
> because
> 
> (a) with the XML 1.1 model, it is not necessary for a child element to
> inherit all the namespaces of its parent
> 
> (b) in general, inheriting the namespaces of the parent doesn't achieve
> anything useful. If the subtree rooted at A uses a particular namespace,
> then it will already have that namespace in scope; when A becomes a child of
> B, it will never actually need the namespaces that are available on B.
> 
> (c) inheriting the namespaces of the parent can be a nuisance. The canonical
> example is when you attach a payload XML document to a SOAP envelope, and
> later detach it again, you find that the payload has acquired all the SOAP
> namespaces.
> 
> (d) some implementors appear to believe that the greater the number of
> namespaces are attached to an element node, the greater the performance
> overhead.
> 
> 

-- 
Xavier FRANC

Received on Friday, 24 October 2003 17:44:15 UTC