Roadmap
What is next
Ordered by what is actually being worked on, not by quarter. Each item says why it is on the list, which is the part a roadmap usually leaves out.
No dates on purpose
A roadmap with dates is wrong within a month and then quietly stops being updated, which is less useful than one that is honest about ordering. What shipped, and when, is in the changelog — most recently "Per-user workspaces".Building now
XPath reference
Every XPath 1.0 function, axis and operator, each with a worked example you can run against a real document rather than a claimed output.
Why: The XPath tester made this possible: the pages can show what libxml2 actually returns instead of asserting it. The namespace trap alone — where //loc matches nothing in any sitemap — is worth a page people can try.
Decided, not started
XSD datatype reference
The built-in types and constraining facets, each with a valid and an invalid literal, and the exact message our validator emits for the invalid one.
Why: Schema errors are already the corpus people arrive at holding a message. Datatypes are where most of those messages come from, and there is nowhere on the web that shows the message alongside the rule.
A directory of public XML endpoints
A curated index of real, public XML: government open data, standards bodies, package indexes, transit feeds — each with its structure extracted, and monitored so dead entries delist themselves.
Why: It is the 'dir' in the name, and it has never existed. It is also the only part of this site that would be genuinely hard to copy: the value is in the curation and the fact that it stays true.
Still a question
Element reference
Per-format element pages — <loc>, <lastmod>, <guid>, <itunes:duration> — with cardinality, constraints, and the errors each one causes.
Why: The search volume is the highest of anything on the list. The risk is equally high: a hundred pages that each say very little is the classic way a reference section becomes worthless. It ships only if every page can carry a real constraint and a tested example.
Scheduled monitoring for guest workspaces
Let a workspace without an account run scheduled re-checks.
Why: It is the most-asked-for thing that we have deliberately not done. An anonymous workspace can be lost without warning, and a monitor that outlives the only way to see its alerts is a worse experience than not having one.
Something you need that is not here? Tell us what breaks for you
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.