Most reviewers learn the explicit-versus-typed distinction the hard way: by trying to pick the right one for a counterparty list that grows every quarter. Explicit dimensions look comfortable when a static list seems plausible (three operating segments, four geographies, eight share classes). Typed dimensions look exotic and intimidating. Then the counterparty list lands and the choice is forced.
Explicit dimensions are closed enumerations. The taxonomy declares the dimension, then declares each permitted member as a QName, and wires them together through dimension-domain and domain-member arcs in the definition linkbase. An instance reports a member by emitting xbrldi:explicitMember whose content is the member's QName. If the QName does not match a declared domain member, the validator rejects the fact: it is not in the dimension's domain. Explicit fits natural taxonomies of finite, named things, the kind a standards body or filer can enumerate up front.
Typed dimensions are the open-ended case. Instead of naming members in advance, the dimension declaration carries an xbrldt:typedDomainRef attribute pointing at a global element declaration. That referenced element defines the type and structure of the typed value: a string, a date, a more complex element with attributes. An instance reports a typed value by wrapping it in xbrldi:typedMember, and the fact's identity now depends on the literal value. Counterparty IDs, contract numbers, instrument identifiers, lease IDs: anything where the set of admissible values cannot reasonably be enumerated up front.
EBA DPM uses typed dimensions extensively because supervisory reporting deals with millions of unique counterparty and exposure identifiers across a population of banks. ESEF and most jurisdictional financial-statement taxonomies stay almost entirely explicit because the segments and reportable categories are bounded. A single hypercube can mix the two: nothing forbids one explicit dimension and one typed dimension on the same cube. The XDT rules apply per dimension.
The trap with typed dimensions is value equality. Two facts that differ only by case or whitespace in their typed members are treated as different facts because XML equality is character-precise. Typed values must be normalised before tagging, or auditors will read silent duplicates as distinct counterparties.
Explicit dimensions have a closed list of taxonomy-defined members. The fact reports a member via xbrldi:explicitMember whose content is the member's QName.
Typed dimensions are open-ended. The dimension declaration carries xbrldt:typedDomainRef pointing at a global element declaration; the fact reports the value via xbrldi:typedMember.
Use explicit when the set of valid axis values is finite and known (segments, share classes). Use typed when values are open-ended (counterparty IDs, contract IDs).
Typed dimensions are common in supervisory reporting (EBA DPM uses typed dimensions for counterparty IDs). Most financial-statement taxonomies stick to explicit.
Mixing explicit and typed in one hypercube is permitted; the rules apply per dimension.
<xbrli:scenario>
<xbrldi:typedMember dimension="eba:CounterpartyId">
<eba:ct_id_value>LEI:529900T8BM49AURSDO55</eba:ct_id_value>
</xbrldi:typedMember>
</xbrli:scenario>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.