XBRL inherits the substitution-group mechanism from XML Schema and uses it as a role marker. The substitution group of a concept tells you what kind of element it is: a regular fact-bearing primary item, a tuple grouping ordered children, a hypercube anchoring a dimensional structure, or a dimension axis itself. Read the substitution group first; type and balance are details on top.
`xbrli:item` is the substitution group for primary items: the concepts that actually carry fact values in an instance. If a concept is going to be the target of a fact in your filing, its substitution group has to be `xbrli:item` (or a sub-group that derives from it). The vast majority of concepts in any modern taxonomy are items.
`xbrli:tuple` is the substitution group for tuples, which are ordered groupings of child facts under one parent element. Tuples were the way early XBRL taxonomies expressed "these facts go together". They have largely been replaced by dimensions, which scale better, render more naturally, and integrate cleanly with hypercubes. A few legacy areas of the Dutch `Nederlandse Taxonomie` still rely on tuples for grouping; modern IFRS and US-GAAP taxonomies do not author new ones.
`xbrldt:hypercubeItem` and `xbrldt:dimensionItem` are abstract structural roles defined by the XBRL Dimensions specification. A hypercube concept declares the existence of a dimensional cube; a dimension concept declares an axis of that cube. Neither is fact-bearing. If you see a concept with `substitutionGroup="xbrldt:hypercubeItem"` showing up in an `ix:nonFraction`, something has gone wrong: the file is trying to tag a fact value against a structural element that cannot legally carry one.
Substitution-group violations fail at schema validation, which runs before any XBRL semantic checks. That is bad news because the filing never reaches the regulator's profile validator at all, and good news because the failure is loud and immediate. The fix is to use a concept whose substitution group is `xbrli:item` (or one of its derivatives), and to leave hypercubes and dimensions to the linkbases that wire them together.
An XBRL concept's substitution group decides what role it plays. xbrli:item is the regular fact-bearing concept. xbrli:tuple groups child facts under one parent.
xbrldt:hypercubeItem and xbrldt:dimensionItem are abstract roles for dimensional infrastructure. Primary items must be in xbrli:item.
Tuples are mostly out of fashion; modern taxonomies prefer dimensions. Some legacy taxonomies (older NL Taxonomie) still rely on tuples for grouping.
If you see a concept used as if it were a primary item but its substitution group is xbrldt:hypercubeItem, the concept is not a fact-bearing element and the filing has misused it.
Substitution groups are checked at schema-validation time, before any XBRL semantics. Errors here fail your file before the regulator's validator runs.
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.