How to Validate XML: Well-Formed Checks and XSD Schemas

Two Levels of XML Validation

Well-formed means the markup rules are satisfied: tags nest correctly, attributes are quoted, entities are escaped. Valid against a schema means the document also matches an XSD (or DTD/RelaxNG) contract—required elements, types, and structure.

Partner systems often reject files that are well-formed but not schema-valid. Check both.

Step-by-Step: Well-Formed Check

Any XML parser that throws on the first error is enough for this level.

xmllint --noout orders.xml && echo "well-formed"

import xml.etree.ElementTree as ET

try:
    ET.parse("orders.xml")
    print("well-formed")
except ET.ParseError as e:
    print("not well-formed:", e)

import { XMLValidator } from "fast-xml-parser";
import fs from "node:fs";

const xml = fs.readFileSync("orders.xml", "utf8");
const result = XMLValidator.validate(xml);
if (result !== true) {
  console.error(result);
}

Step-by-Step: XSD Schema Validation

When a partner sends an .xsd file, validate against it before every upload.

xmllint --noout --schema orders.xsd orders.xml

Common Well-Formed Failures

These errors show up constantly in hand-built or CSV-generated XML.

• Unescaped & in company names and URLs.
• Mismatched or overlapping tags.
• Attribute values without quotes.
• Invalid characters in element names (spaces, leading digits).
• Multiple top-level elements without a single root.

<!-- Bad -->
<name>Ada & Charles</name>

<!-- Good -->
<name>Ada &amp; Charles</name>

Common Schema Failures

The document parses, but the partner portal still rejects it.

• Missing required elements or attributes.
• Wrong namespace on the root element.
• Unexpected extra fields not in the XSD.
• Values that fail xs:date, xs:decimal, or pattern facets.
• Wrong repeating element cardinality (minOccurs/maxOccurs).

Validate After CSV → XML

Generated XML from spreadsheets is a high-risk path. Clean headers in the Online CSV Editor, convert with CSV to XML, then run xmllint --schema before SFTP upload. If validation fails, fix the CSV columns—not the XML by hand—so the next run stays clean.

Real-World Examples

Where validation pays for itself.

Common Mistakes

Skipping validation is the most expensive shortcut.

• Only checking well-formedness when an XSD exists.
• Editing XML in Excel and re-saving as something that is no longer XML.
• Ignoring namespace URIs in the schema.
• Validating once manually and never again after the CSV changes.
• Treating "opened fine in a browser" as schema validation.

Best Practices

Make validation boring and automatic.

• Keep the XSD in version control next to feed generators.
• Validate in CI and before every production upload.
• Prefer generating XML from clean CSV over hand-editing markup.
• Log xmllint errors with line numbers for ops.
• After fixing, re-flatten with XML to CSV to confirm business values.

Why Use Convert CSV Online?

Convert CSV Online is free, browser-based, and requires no account for everyday conversions. Build XML from cleaned CSV, or flatten partner XML to CSV for human review after a schema failure. Client-side workflows work on Windows, macOS, and Linux browsers.

Conclusion

Well-formed checks catch broken markup. XSD validation catches contract mismatches. Run both before partner systems reject your file—or worse, accept a partial import.