Start in about ten minutes
- Download the package.
- Declare the namespace and tag content you have already written.
- Check it in the browser validator before you publish.
What changes once it is running
AI cites you
A claim an engine can attribute and date is one it can repeat in its own answer, with your name on it, rather than working around you for a source it can verify.
Data arrives usable, not just parsed
A consumer that receives a source, a confidence and a validity window can decide how much weight to give a claim.
Superseded figures stop circulating
Expired knowledge drops out of present-tense queries while staying on record, so “what did we believe last March, and on what basis?” is now answerable.
Unit confusion becomes impossible
A quantity arrives as a number, a unit and a tolerance rather than a string every consumer parses for itself, differently, and occasionally wrongly.
Systems decline instead of guessing
“Does not require coolant” and “no information about coolant” stay distinct. A processor must honour that distinction or reject the document.
A retracted source takes its consequences with it
Invalidating an input finds every conclusion that transitively rests on it, instead of leaving them scattered with nothing linking them back.
Automated deduplication occurs upstream
The same statement arriving from two pipelines is recognised as one, so deduplication is not re-invented at every entry point.
Nothing has to execute
A few hundred bytes per tag, read by XPath, DOM parsers, lxml or any JSON library. No runtime dependency, no effect on page speed.
Adoption can be incremental
The quality features are optional attributes, so a consumer that ignores them still parses correctly. Start with entities and facts; add provenance and validity as your pipeline learns to use them.
AI systems read your content and cannot tell a measured figure from a guess, or last year’s number from this year’s. So they hedge, paraphrase, or get it wrong.
AODM 1.2 attaches four things to every claim you publish: a
source (<aodm:source>), a
confidence (<aodm:confidence>), a
validity window (valid-from and
valid-to), and whether it was measured or inferred
(origin). On a web page they go in one data-aodm attribute
on HTML you have already written; on their own they are standalone XML or JSON
documents. No scripts, no build step, no effect on page speed.