Xml parser validating vs non validating advantages
Validating parsers perform more rigorous checks, such as making sure the document conforms to the rules laid out by its document type definition (DTD).Validating parsers also can use information from the DTD to provide extra capabilities, such as entity substitution and attribute defaulting.It's like asking, "I want to buy a car and I want to make sure the wheels will stay on. The developer of the browsing application will almost certainly have made the decision for you, and you can probably override it only with difficulty (and perhaps intellectual pain).
Quick Tip: Both the XPath and XQuery Match assertions make use of the Saxon XPath / XQuery processor which supports most of the latest standards in this area.) But maybe for one reason or another you really do need to select a standalone parser. And within the well-formedness category, you may need some additional but optional features which are required only of a validating parser.Do you want the parser to supply an attribute's default value if the document author hasn't done so? In such cases, you can eliminate whole sub-categories of non-validating parsers from consideration.If the application you're working on is end-to-end Microsoft-specific, there's no practical advantage (all other things being equal) to considering a parser other than the one built into One final thing to bear in mind when you embark on a search for the "best parser," whatever that means for you: You'll need to limit your search very quickly or go crazy.Back in 1998, within a few months of the XML 1.0 Recommendation's release, one observer reported on XML-DEV that he'd found over 200 parsers (after hitting 200, he gave up counting).