Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Namespace In Regards to Reading XML With MSXML

Namespace In Regards to Reading XML With MSXML

Namespace In Regards to Reading XML With MSXML

After doing the last thing I asked about with XML, I decided to try reading the files back in (as a learning exercise). I got that done successfully with my own output, and a handful of others using SelectNodes() to reach the specific data of interest.

But I ran into a little issue with one file evidently not generated by the reference consumer program I was using to test my writes, where SelectNodes() doesn't return data. Comparison-wise, it's almost exactly the same, except for a reference like this in a couple of the main nodes.

<main-node xmlns="<URL reference>">

I figured out this was a namespace reference (invalid URL btw) and read quite a bit about them in a few references. But from what I can tell, the file doesn't contain any explicit references to the name space or even has the base part defined. Of course, part of the folly of looking at web references is not finding anything too similar to what you see in front of you.

Anyhow, opening the file in a text editor and removing the xmlns references and saving the file resulted in the program being able to read the data successfully.

So what do I need to do to be able to read XML files regardless of the presence of references like this?

RE: Namespace In Regards to Reading XML With MSXML


Consider this XML document:


<?xml version="1.0" encoding="UTF-8"?>
    <part>no explicitly declared namespace</part>
  <elm xmlns="info:whatever" xmlns:ns2="info:this_does_not_have_to_be_a_URL">
    <part>some namespace</part>
    <ns2:part>this does not share the namespace of its parent</ns2:part>

How does one fetch the contents from the part elements spread through the document without editing the document?

Our XPath expression may look only into the local name of the element, disregarding its namespace. For instance
  • selectNodes("//part").length returns 1, because there is only one part element with an empty namespace
  • and that's why selectNodes("//part").item(0).text returns "no explicitly declared namespace"
  • selectNodes("//*[local-name() = 'part']").length returns 3, because there are three part elements, no matter of which namespace
  • and so selectNodes("//*[local-name() = 'part']").item(2).text may return "this does not share the namespace of its parent"
Of course, this is a bit clumsy, and it will get worse when you have to look into the tree of nodes. For instance, to get the contents of the second part one should have to selectNodes("//*[local-name() = 'elm']/*[local-name() = 'part']").item(1).text. To get a node of a particular name and namespace this way, one would have to check for the namespace also using other XPath function, as in selectNodes("//*[local-name() = 'elm' and namespace-uri() = 'info:whatever']/*[local-name() = 'part' and namespace-uri = 'info:this_does_not_have_to_be_a_URL']").item(0).text.

But let's assume there is a reason for the namespace to be declared and present in the document, as normally there is. To avoid the mess above and to deal properly with namespaced documents, we must declare their identifiers in the MSXML SelectionNamespaces property and associate a prefix to each one of them.

.setProperty("SelectionNamespaces", "xmlns:n1='info:whatever' xmlns:n2='info:this_does_not_have_to_be_a_URL'")

After this, we can select the different (kind of) part elements by using the prefix that was set in the property (and not whatever prefixes, if any, used in the XML document).
  • .selectNodes("//n1:elm/n1:part").item(0).text returns "some namespace"
  • .selectNodes("//n1:elm/n2:part").item(0).text returns "this does not share the namespace of its parent"
  • .selectNodes("//elm/part").item(0).text continues to return "no explicitly declared namespace"
So, summing up, the way to deal with namespaces in XML using MSXML is by setting the SelectionNamespaces property.

RE: Namespace In Regards to Reading XML With MSXML

Thanks, that helped. Got my program reading any and all files now.

RE: Namespace In Regards to Reading XML With MSXML

Quote (Glenn9999)

namespace reference (invalid URL btw)

It is probably best to consider a namespace as a unique, case-sensitive string. While the XML specification says that a namespace is a URI, the treatment of the character string (case sensitivity, no % escaping) has the practical effect of reducing a namespace to a fancy string. The most recent namespace specification has several deprecations, so it is a work in progress.

I try to use valid URIs but often see odd stuff...

Tom Morrison

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close