Tools to validate xml against xsd

However, if you don't mind spending a little money, a standalone tool can come in extremely handy. For the record, not all standalone tools cost money. XMLStarlet is another good option. Regardless of what type of validation tool you decide to use, there is a big distinction between validating documents against DTDs and validating them against XSDs.

Although some tools support both types of schemas, many tools do not. You should therefore consider what type of schema you plan on using when assessing the different tools out there.

Of course, this validation tool falls into the category of web-based tools. Figure 8. Similar to most web-based validation tools, there are two approaches available for validating documents with the XML Validation web page:. Depending on your circumstances, the latter option is probably the simplest because you will likely be developing XML documents locally. As I mentioned earlier, sometimes validators have problems with local schemas, so the easier route in terms of having the validator run smoothly is to stick your document s and schema on a computer that is accessible on the Internet via a URI.

That way you are guaranteeing that the validator can find the document and its schema, both of which are required for validation. If you're able to post your schema to the Web so that it is available online, you can still use the XML Validation web page to validate local XML documents.

After specifying the document to the XML Validation web page and clicking the Validate button, any errors found during validation will be displayed in your web browser see Figure 8. Fortunately, the XML Validation web page caught the problem and alerted me. After repairing the problem and initiating the validation process again, everything turns out fine see Figure 8. You'll have to register the product in order to run it but registration is entirely free and you can choose not to receive email solicitations during registration.

It's still important to have the XSD properly associated with the documents, as you learned how to do in the previous lesson. In Visual Studio or in Visual Studio. Reopen Product. Visual Studio or Visual Studio. NET displays a new file named Module1. At the beginning of this file, add two Imports statements, as follows:. In Module1 before the start of the Main subroutine , declare a boolean variable named isValid, as follows:.

Set this property to DTD, as follows:. If any validation errors occur, the validating reader generates a validation event. Add the following code to register a validation event handler you will implement the MyValidationEventHandler subroutine in step 8 of this section :.

Add the following code to read and validate the XML document. If any validation errors occur, MyValidationEventHandler will be called to handle the error. This subroutine will set isValid to False see step 8 of this section. You can check the status of isValid after validation to see whether the document is valid or invalid.

The application should report that the XML document is valid. Run the application again. Validation event Element 'Product' has incomplete content. Expected 'ProductName'. Document is invalid. Declare a default namespace, urn:MyNamespace , in the document. Open Product. NET, open Module1.