Hi, I'm Daniel Haket.

From international finance to building with AI

My professional background is in international finance, including trade finance, operations and risk & control at ABN AMRO and Deutsche Bank. Working across borders is something I have always enjoyed: different perspectives, new relationships and the people behind a process.

Today, that international curiosity goes hand in hand with a strong drive to build. I am fascinated by what AI makes possible for an independent founder: turning an idea into something people can actually use, then making it better as they use it.

Outside work, family comes first. I love animals, have a lasting affection for Asia and enjoy meeting people from around the world. Those connections matter to me as much as the technology.

Why XSDHub exists

XSDHub focuses on a small, practical problem: making XML easier to check and understand. A syntax error, a namespace mismatch or a value that fails a schema can interrupt a much larger workflow. The tools bring the document, the schema and the validation result together in one browser workbench.

You can check XML syntax, validate against an XSD or format a document without an account. The guides explain the rules behind common errors with examples you can try yourself.

How the tools and guides are built

XSDHub is developed with AI assistance. AI helps with code, explanations and examples; a generated explanation is not, by itself, proof that a rule is correct. The guides link to primary references, including W3C specifications, so readers can check the underlying definitions.

The workbench uses libxml2 compiled to WebAssembly. The new practical guides have 17 automated checks covering valid and invalid XML/XSD pairs, namespace prefixes, occurrence boundaries, child order, escaping and CDATA. These checks use the same validation module as the tools. They cover those examples, not every possible schema or application.

I am the founder and project owner, bringing an interest in dependable workflows from my finance background. The guides are published by XSDHub and should be checked against your receiving system's own schema and requirements.

What the tools do, and where they stop

Default XML and XSD 1.0 validation runs locally on your device. Optional server modes send the inputs to XSDHub only after explicit consent. Saving a schema to an account library is a separate action that stores it on the server; Team libraries share those saved schemas with workspace members.

The current tools support UTF-8 files up to 10 MB XML and 1 MB per schema and XSD 1.0 schema projects with local imports and includes (up to 100 schemas, 10 MB total). Optional server modes add XSD 1.1 and ISO Schematron XPath 1.0, with explicit upload consent and up to 10 MB XML. DTDs remain blocked. A separate opt-in public HTTPS importer creates local schema snapshots. Pro and Team cloud projects store complete schemas and their saved versions. A successful schema check does not establish that invoice totals, business identifiers or other application rules are correct.

Other projects I build

XSDHub is one of my independent projects. You can read more about my background at AIBuilder Marketplace, explore my work on ZeroTouch Support, or visit BatteryPayback. Each project has its own purpose and subject matter.

Questions, feedback or a correction?

Email support@xsdhub.com. For an error in a guide, include the page URL, the claim you think needs changing and a source or small reproducible example if you have one. For a tool problem, describe what you expected and what happened. Remove confidential information before sharing sample XML.

Corrections are checked against the relevant source or reproduced in the tool before the affected explanation or code is changed. General enquiries sent to hello@xsdhub.com reach the same inbox.