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
| # | Check | What it proves |
|---|---|---|
| 1 | Each source module is validated against the Project Tavi JSON Schema | The modules are well-formed |
| 2 | Each 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 way | Nothing is lost in conversion, and the modules pass the draft’s own checks |
| 3 | Arelle validates every generated entry point | The 2.1 taxonomy is valid XBRL |
| 4 | Every 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 detection | The reports are what their specifications say, and valid |
| 5 | The CSV and JSON samples are compared, and each annual report is compared with its company’s transition plan through the concordance | Two formats of a report agree, and so do a plan and the annual report that tracks it |
| 6 | The taxonomy package itself is checked, and the reports are shown to load through its catalog | The package is well-formed, and reports load through it |
| 7 | Every explicit dimension is shown to reach its members | No member is unreachable, which validation alone would not show |
| 8 | The dashboard and its company pages are regenerated and must not differ | The dashboard matches the reports |
| 9 | Each sample is rendered as Inline XBRL, validated, read back and compared with its source | The rendered report carries every fact, fact for fact |
| 10 | Every Framework item has a reference of its own, stating whether it is a shall, a may or conditional, and the lookup table is current | Every Framework item is covered, and its force can be looked up |
Tools
- A converter from Project Tavi to XBRL 2.1.
- Arelle, the open-source XBRL processor, for validation and for reading the Inline XBRL back.
- mireport, EFRAG’s open-source reporting tool, to render the sample reports as Inline XBRL.
A build fails if any fact cannot be added to a report, or would appear nowhere in its page.