Cart
[Home] [By Thread] [By Date] [Recent Entries]
Evan Lenz wrote: > More significant than an analogy with programming practice is how XPath and > XSLT model namespaces. For every in-scope namespace binding at a given > element, there is a namespace node. This has two immediate practical > implications: 1) performance may degrade as the number of namespace nodes > proliferates, and 2) any copy of that element into the result tree will > include all of its namespace nodes. I think that any sensible Infoset implementation wouldn't actually allocate storage for each namespace node. Instead, it would synthesize a list of namespace nodes from the in-scope namespace declaration nodes on demand. --Joe English jenglish@f...
|
