Skip to main content

Search 412 pages — tools, formats, elements, namespaces, directory, comparisons, XPath, datatypes, glossary, parse errors, schema errors, use cases, guides, blog and product.

Reference

The XML reference

341 entries across 11 sets, every example checked against the same parser the workspace runs — so a page that claims a document produces an error fails the build when it stops being true.

  • Glossary

    58 terms

    The words the specifications assume you already know — CDATA, QName, PCDATA, canonicalization — each defined in a sentence, demonstrated against a real parser, and linked to where it bites.

    For example CDATA section

  • Root element, namespace URIs, media type, and the constraints that cause real failures — sitemaps, RSS, Atom, SOAP, XSD, WSDL and more.

    For example XML sitemap

  • Elements

    49 elements

    Per-element rules for sitemaps, feeds, SOAP, and XSD: what may sit inside what, how many are allowed, and executable broken and fixed documents.

    For example <lastmod>

  • Namespaces

    33 namespace URIs

    Look up a namespace URI, its conventional prefix, the specification behind it, and the formats that declare it.

    For example sitemaps.org 0.9

  • XPath 1.0

    40 functions, axes and operators

    Every entry carries examples that were run on libxml2 and had their output compared, including the namespace trap that makes the obvious expression return nothing.

    For example normalize-space()

  • XSD datatypes

    39 types and facets

    What validates and what does not, with every literal put through the schema validator — because most schema failures are lexical rather than semantic.

    For example xs:dateTime

  • Public endpoints

    31 live XML documents

    Real XML you can fetch right now, from standards bodies to transit APIs. Every entry was fetched before it was listed and is re-checked daily, so link rot reports itself instead of accumulating.

    For example Earthquakes, past hour

  • Comparisons

    9 side-by-side answers

    XML or JSON, RSS or Atom, XSD or RELAX NG — the differences that matter, demonstrated by running both sides, and an honest account of where the other one wins.

    For example XML vs JSON

  • Parse errors

    29 well-formedness errors

    Keyed by the message your parser actually printed, and cross-referenced to how libxml2, Xerces, expat and .NET each word the same defect.

    For example Premature end of data

  • Schema errors

    10 validation errors

    The failures that only appear once an XSD is applied — a document can be perfectly well-formed and still fail every one of these.

    For example Element is not expected

  • Free tools

    19 tools

    Validate, explore and convert XML in the browser. They parse in memory, store nothing, and fetch nothing — no sign-in.

    For example XML validator

How these pages are kept honest

Examples are parsed, not proofread

Every format example on this site is run through the real parser on each test run. If it stops being well-formed, or stops detecting as the format it claims, the build fails.

Error text is quoted, not paraphrased

Each error page states the message our own validator emits, and the test asserts the broken snippet still produces exactly that. A parser upgrade that reworded it breaks the test, not your afternoon.

Counts come from the data

The numbers above are read from the corpora at build time. Nothing on this page can claim more coverage than actually exists.

Everything here is free and needs no account. The validation API returns the same verdicts as JSON or SARIF.

Get started

Bring order to the XML your team can't afford to ignore.

Create a free account and get a private workspace to search, validate, diff, and monitor your XML feeds, sitemaps, schemas, and vendor integrations.