Use case
Document archives
Prove the document did not change
The problem
An archive's job is to be able to say what a document said, and when. Two files that differ only in attribute order or indentation are the same document; two that differ in one character of content are not. Telling those apart by eye, or by a text diff, does not scale and does not hold up.
What you get
- Equivalence is a checkable property rather than an opinion
- A change to a published record has a date, a diff and a before
How XMLDir helps
- Canonicalize with C14N 1.0, 1.1 or exclusive before comparing or hashing
- Compare structurally, so a reserialization is not mistaken for an edit
- Validate TEI, JATS and DocBook against the RELAX NG grammars they actually ship
- Keep immutable versions with a searchable record of every change between them
Other use cases
Sitemap operations
Keep sitemap.xml healthy at scale
Vendor integrations
Catch contract drift before it breaks orders
XML to data workflows
Turn XML into clean, repeatable pipelines
Sample payload vault
A searchable memory for tricky XML
CI validation gates
Fail the build, not the customer
Regulated messaging
Schema-valid is necessary, not sufficient
Localization pipelines
Catch what translation quietly changed
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.