Re: RE: Namespace incompatibility b/n XPath 2.0 Data M

> > I was just thinking that when the XPath Data Model is
> > implemented in XPath 2.0 the
> > above solution will have to be rewritten.
> >
> > This is because according to the model namespace nodes will
> > no longer be copied to
> > all descendent nodes. Another (minor) potential trap is that
> > in XPath 2.0 a namespace node has no parent.
> 
> This is a misunderstanding of the proposed change to the model.
> 
> Under the proposed change, an element node will still have (on its namespace
> axis) a namespace node for every namespace that is in scope for that
> element. 

Mike,

Thank you very much for the explanation -- this is what I expected.

However, this means that in the model the definition of the namespace::* and of the
"namespace" axis in general, has been changed.

The current definition, according to the XPath spec (http://www.w3.org/TR/xpath) is
as follows:

"the namespace axis contains the namespace nodes of the context node"

and further in the spec...

"Elements never share namespace nodes: if one element node is not the same node as
another element node, then none of the namespace nodes of the one element node will
be the same node as the namespace nodes of another element node."

The XPath 2.0 Data Model document doesn't mention that there is a change in the
above definition. Any misunderstanding would have been avoided, if this had been
explained in the document. For example, the document could say:

"The meaning of the 'namespace' axes has been changed from XPath 1.0 in order to
reflect the fact that a namespace node belonging to an element is not copied to all
of its descendent element nodes".

Cheers,
Dimitre Novatchev.


__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger. http://im.yahoo.com

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list