The host XHTML in an iXBRL filing is not casual web markup. ESEF and SEC EFM both impose tight rules on what the host document can contain, because regulated consumers need to parse the file deterministically and the file must remain self-contained for archiving. Treat the iXBRL host as a sealed, internally-consistent artifact, not as a regular web page that happens to ship with some extra attributes.
The most frequently broken rule is the ban on external resources. No <link rel="stylesheet" href="..."> to an external CSS file. No <script src="..."> to an external script. No xml:base attribute redirecting URI resolution. CSS must be inline (either in <style> blocks in the head or in style attributes); scripts are generally banned outright in ESEF and tightly restricted in EFM. The reason is simple: external dependencies break the moment the web changes, and a filing must remain validatable in five years' time without a working network.
The host file must also be well-formed XHTML rather than loose HTML. Every tag closes properly, attribute values are quoted, ampersands are escaped, self-closing tags use the XML form, and the document is valid against the XHTML serialisation. Bad markup breaks the parser before any XBRL rule can fire, and the resulting error is rarely a friendly XBRL message: it is usually an XML parse error somewhere far from the actual problem.
ESEF requires the .xhtml file extension on each file in the report package, plus a single output target per file. Multi-file reports use an Inline XBRL Document Set (IXDS), which treats two or more XHTML files as one logical iXBRL report.
When ix:hidden carries a fact whose value also appears visibly in the rendering, ESEF requires the visible element to carry the -esef-ix-hidden CSS style class so consumers can link the hidden numeric fact to its visible duplicate. SEC equivalent is -sec-ix-hidden. Forget the link and the consumer cannot prove the hidden value matches the visible text.
Finally, report packages routinely fail on housekeeping debris: macOS .DS_Store files, __MACOSX directories, embedded PDFs, .html files where .xhtml was expected. Clean the package before zipping; the validator is unforgiving about the shape of the bundle.
ESEF and SEC EFM both forbid external CSS, external scripts, and xml:base. Inline everything; sanitise host HTML at generation time.
iXBRL files are well-formed XHTML. Self-closing tags, properly quoted attributes, escaped ampersands. Bad HTML breaks parsing before any XBRL rule fires.
ESEF requires the file extension .xhtml and a single output target per file (or a multi-file Inline XBRL Document Set, IXDS).
Hidden facts whose values also appear visibly must be linked via the regulator-specific style class: -esef-ix-hidden for ESEF, -sec-ix-hidden for SEC.
Macintosh .DS_Store files, __MACOSX directories, embedded PDFs, and stray HTML files routinely cause report-package rejection. Clean the package before submission.
3 questions. Druk op 1 tot 4 om te kiezen, Enter om te bevestigen.
Door deze quiz af te ronden, markeer je deze sectie als voltooid.
Tip: kies met 1 tot en met 4 en bevestig met Enter.