Dtd validating parser
However, XML processors have to accept a lot on blind faith.
If we try to build a document to meet some specific XML application's specifications, it doesn't do us any good if a content generator slips in a strange element we've never seen before and the parser lets it go by with nary a whimper. It can restrict the number and type of elements a document can use and control where they go.
The Error system variable indicates the error number.
You can intercept this error using a method installed by the ON ERR CALL command.
The third parameter indicates a specific DTD or an XML schema for document parsing.
Your toolbox, naturally, gives you lots of ways to do this. Document type descriptions (DTDs) are documents written in a special markup language defined in the XML specification, though they themselves are not XML.When Saxon itself instantiates the XML parser, it will use an that causes these local copies of DTDs to be used rather than fetching public copies from the web (the W3C servers are increasingly failing to serve these requests as the volume of traffic is too high).It is possible to override this using the configuration setting , or their API equivalents.XMLDOM") xml Doc.async="false" xml Doc.validate On Parse="true" xml Doc.load("note_dtd_error.xml") document.write("Error Code: ") document.write(xml Doc.parse Error.error Code) document.write("Error Reason: ") document.write(xml Doc.parse Error.reason) document.write("Error Line: ") document.write(xml Doc.parse Error.line)var xml Doc = new Active XObject("Microsoft.well-formed is a minimal requirement for XML everywhere.