Re^2: Strange XML parser behaviour using MSXML2 Version 4.0 or not...?

If this problem is to be solved using XML::LibXML, it sounds like a parser-limitation, right? Using another parser is not an option unfortunately. And libXML will have its own problems as well, though it will surface another unfortunate moment.. ;-)
To be honest I don't know exactly what you mean by 'Qualified name', so although this question might not be Perl-ish, I don't know where else to look. Given the fact that Mr. Gate's XML DOMDocument.4.0 API must be used, What would the (unqualified) XPath expression look like?
Or is that an impossibility?
Thanx in advance,
John

Comment on Re^2: Strange XML parser behaviour using MSXML2 Version 4.0 or not...?

Replies are listed 'Best First'.
Re^3: Strange XML parser behaviour using MSXML2 Version 4.0 or not...? by gellyfish (Monsignor) on Mar 16, 2005 at 11:11 UTC
The behaviour is by design in MSXML2 and is clearly documented on MSDN here and here and here - if you have a problem with an MS API MSDN should be the first place that you will be looking. For more information on XML in general and the notion of "Qualified Name" in particular please refer to the W3 DOcumentation /J\	[reply]