You can note that the reader works in the scope defined by the navigator passed to its constructor, effectively providing a view over a fragment of the entire document.It's also important to observe that even when an evaluation will cause a cursor movement to the navigator in , the reader we're using will not be affected, as the constructor clones it up-front.
NET's Xml Validating Reader, but I wonder if the issues about multiple Schema files crossed with multiple or same namespaces are more general.
" - mostly because it can effectively be used to "drop" namespaces from schemas (created or imported) and by doing this mis-represent how the xmls should looked like.
Note: I guess this statement deserves a blog post by it's own, but I'm not going to go there (at least not now), I'm just interested in getting the schemas in my project correct, which would definitely, at this point, involve making sure they are all, always, qualified (and I believe they are, as I usually make the point of setting it explicitly, luckily).
I outlined some of them with regards to querying functionality in my posts about how to take advantage of XPath expression precompilation, and How to get an Xml Node List from an XPath Node Iterator (reloaded).
is a far superior way of accessing and querying data because it offers built-in support for XPath querying independently of the store, which automatically gain the feature and more importantly, because it abstracts the underlying store mechanism, which allows multiple data formats to be accessed consistently.