Transition Plan Digital Taxonomy

How it is built

One source, everything else generated and checked.

How the taxonomy is built and checkedThe Disclosure Framework and sector guidance are authored as Project Tavi taxonomy modules in JSON. A converter produces an XBRL 2.1 taxonomy package. Arelle validates the package and the sample reports, and mireport renders the sample reports as Inline XBRL, which Arelle reads back and compares fact for fact.Taskforce guidanceFramework (Oct 2023)sector guidance (Apr 2024)Taxonomy modulesJSON, Project Tavi draftthe sourceXBRL 2.1 packageXSD and linkbasesgenerated, never hand-editedauthoredconvertedArellevalidates the packageSample reportsxBRL-JSON, syntheticInline XBRLrendered by mireportRead backequal fact for fact
The taxonomy modules are the source. Everything else is generated from them and checked.

The idea

The taxonomy modules are the source. They are written as JSON in Project Tavi, XBRL International’s working draft format. The XBRL 2.1 taxonomy package is generated from them by a converter and is never edited by hand. The sample reports are generated too: each starts as an xBRL-JSON report and is rendered as Inline XBRL.

So the taxonomy already follows the draft of the next XBRL taxonomy format, and the generated 2.1 package works with today’s tools.

The checks on every build

#CheckWhat it proves
1Each source module is validated against the Project Tavi JSON SchemaThe modules are well-formed
2Each module is converted to XBRL 2.1, with any unexpected warning failing the build, and the draft’s own validator is run on each source; the ISSB filers’ extensions are converted and checked the same wayNothing is lost in conversion, and the modules pass the draft’s own checks
3Arelle validates every generated entry pointThe 2.1 taxonomy is valid XBRL
4Every sample report is regenerated from its specification and must not differ; Arelle then validates each, the annual reports against the ISSB or ESRS taxonomy, with the unit type registry and duplicate-fact detectionThe reports are what their specifications say, and valid
5The CSV and JSON samples are compared, and each annual report is compared with its company’s transition plan through the concordanceTwo formats of a report agree, and so do a plan and the annual report that tracks it
6The taxonomy package itself is checked, and the reports are shown to load through its catalogThe package is well-formed, and reports load through it
7Every explicit dimension is shown to reach its membersNo member is unreachable, which validation alone would not show
8The dashboard and its company pages are regenerated and must not differThe dashboard matches the reports
9Each sample is rendered as Inline XBRL, validated, read back and compared with its sourceThe rendered report carries every fact, fact for fact
10Every Framework item has a reference of its own, stating whether it is a shall, a may or conditional, and the lookup table is currentEvery Framework item is covered, and its force can be looked up

Tools

A build fails if any fact cannot be added to a report, or would appear nowhere in its page.