"Passin, Tom" <tpassin(_at_)mitretek(_dot_)org> wrote in message
news:5D3C2276FD64424297729EB733ED1F7601D1C12D(_at_)email1(_dot_)mitretek(_dot_)org(_dot_)(_dot_)(_dot_)
[Robert P. J. Day]
if this is correct so far, then xpathtester is not going to
work on this
well at all since it apparently doesn't have the feature
you're mentioning
that's built into XPath Visualizer (being able to deduce the namespace
just from the XML, right?)
Right - I tried on my copy of xpathtester and could not persuade it to
learn the namespace. Dimitre's tool works fine, though.
Sometimes I'm wondering if this "cleverness" of the tool was really the
right decision -- one can get accustomed to being served and could forget to
specify the namespace in his/her stylesheet.
While the Xpath Visualizer spoils the user in this, the main purpose was to
allow as many features of XPath (and some of XSLT) to be made available, as
possible. As we see in the example with xpathtester, the other alternative
does not give the user the possibility to practice certain types of XPath
expressions with namespaces.
=====
Cheers,
Dimitre Novatchev.
http://fxsl.sourceforge.net/ -- the home of FXSL
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list