Which XML Validation Standards Does XML ValidatorBuddy Support?

Updated

XML ValidatorBuddy supports three validation standards: XSD (XML Schema Definition), DTD (Document Type Definition), and Schematron rule checks. You can apply them to a single file, a folder, or a repeatable batch, and you can run the checks in the Windows desktop app, from a command line or CI runner via ValBuddy, through a Web API, or from an AI coding agent. The right choice depends on what you need to enforce: structure and data types (XSD), legacy document structure (DTD), or conditional business rules (Schematron).

The three standards at a glance

Standard What it validates Typical use
XSD Element/attribute structure, order, data types, and constraints defined in a schema Modern XML interfaces, data exchange formats, API payloads
DTD Document structure declared in a DTD Legacy systems and older document formats that still rely on DTDs
Schematron Conditional rules expressed as assertions ("if X then Y must hold") Business rules that a grammar alone can't express, such as cross-field dependencies

XSD and DTD describe what a document may contain. Schematron describes what a document must mean in context — which is why the tool treats it as a separate check rather than a replacement for schema validation.

How the checks fit into a workflow

The product is built around a "validate, understand, fix, run again" loop. In practice that means:

  1. Assign the rules. Point the document at its XSD, DTD, or Schematron ruleset.
  2. Run the check. Validation results appear beside the XML and the assigned schema, so you can see the document, its schema context, and the findings together.
  3. Locate the failure. Findings stay connected to the source: move from a readable message to the affected line, correct the data, and re-run.
  4. Scale it up. The same checks apply to one file, a whole folder, or a batch you can repeat — with text and grid views for reviewing batch results.

For large XML files, the desktop app provides streaming and dedicated views so validation doesn't require loading everything into an editor at once.

Choosing where to run validation

The standards are the same across access paths; the difference is how much automation you need.

  • Windows desktop app — best when you need to inspect and debug interactively, with schema-aware context while editing.
  • ValBuddy CLI / CI — best for repeatable checks in a developer shell, scheduled task, or Windows CI runner. Ready-to-run commands avoid re-selecting dependencies or writing validation glue code for each run.
  • Web API — a shared service contract for focused operations: well-formedness checks, formatting XML, and verifying the documented safe signature profile.
  • AI agents — deterministic ValBuddy tools give an agent the diagnostics it needs without loading unnecessary context into the model.

Practical notes before you start

  • Pick the standard by intent, not habit. If your rules involve relationships between fields, XSD alone won't express them; add Schematron assertions on top of the schema check.
  • Keep schema context attached. The tool's value comes from showing findings next to the schema that produced them — assign the schema explicitly rather than validating blind.
  • Batch results need review, not just a pass/fail count. Use the grid view to triage which files failed and why before fixing them one by one.
  • A free trial is available if you want to test the standards against your own documents before committing; pricing details are not specified in the available product information, so check the site directly for current terms.