XSD Subset Validator

FREE

More actions

Found something we could improve?

Practical usage guide

A practical workflow for XSD Subset Validator

Validate XML against the supported deterministic XSD subset; unsupported features and unresolved references fail closed.

1. Prepare

Paste or upload a representative input and run the validation before using it in an interface, test or transport.

2. Review

Resolve each reported error from the first failure onward, then run the validation again until the input is clean.

3. Apply

Validate the result against the interface contract and target CPI runtime before transporting or sharing it.

Verification before operational use

Use a representative case with the inputs needed to reproduce it.
Confirm the result in the authorized target environment when runtime versions, namespaces, extensions, permissions or system configuration can change the outcome.
Record the source, assumptions, tool settings and expected result so another reviewer can reproduce the check and distinguish verified facts from recommendations.

Where XSD Subset Validator fits in a delivery workflow

Best-fit use cases

Check an XML document against a supported XSD subset before a SOAP or CPI test: root and root namespace, element order and occurrences, required attributes, basic types and enumerations.

Representative example

Try this XSD: <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"><xs:element name="Order"><xs:complexType><xs:sequence><xs:element name="id" type="xs:integer"/></xs:sequence></xs:complexType></xs:element></xs:schema> XML <Order><id>7</id></Order> passes this check. Replace 7 with A to get a type error at /Order/id.

What to verify next

This is not a complete XSD validator: imports, includes, choice, all and extensions are unsupported. An unsupported schema prevents the check; it does not prove that the XML is invalid. Confirm the result with a full validator using the target schema version.