Subject: Re: More namespace fun? From: David Carlisle <davidc@xxxxxxxxx> Date: Fri, 10 Mar 2000 15:16:35 GMT |
> So, for instance the para tag has > a whole host of namespaces 'attached' to it. Yes namespace nodes clone themselves down the input tree. An element has in its namesapce axis a namespace node for _every_ namespace declaration that is in scope. You don't need to go looking up the tree to find out what namespaces you have available at this point. The information is just there. > I know this is a contrived example, but > what earthly use is this information? It's like wandering in to the british library and saying `Why do you need all these books?'. Information is always useful. > I also note that the namespaces are provided > in document order, Like attributes, namespaces are provided in whatever order the parser cares to provide them. You should not rely on it. Actually there _is_ a reason for namespace nodes. Imagine that the input tree had xpath expressions. so there is a <xxxx href="aaa/b:ggg[c:y]"> you can grab hold of that attribute with @href but if you want to make use of it _as an xpath expression_ you need to know what namespace is attatched to the prefix b: at this point in the input document. Note unlike normal matching on attributes and elements it is the _prefixes_ b: and c: that matter here. David XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: More namespace fun?, Pawson, David | Thread | RE: More namespace fun?, Kay Michael |
RE: Ignore childs, Richard Lander | Date | xt limits patterns for extension fu, Tom Myers |
Month |