The first time most accountants meet a hypercube, they are debugging a segment-disclosure error and the validator just says "primary item dimensionally invalid" without further explanation. It feels like a wall. It is not. XBRL Dimensions, "XDT" for short, is the substrate of every regulated taxonomy on the planet: IFRS, US-GAAP, SBR, EBA DPM. Once the vocabulary clicks, segment errors stop being mystery and start being routine debugging.
A hypercube is an abstract concept declared in the xbrldt:hypercubeItem substitution group. Its job is to bundle a set of dimensions that together define the admissible space of contexts for one or more primary items. Think of the primary item, say segment revenue, as a value that needs three coordinates to be meaningful: which entity, which period, and on which axes (geography, business segment, product line). The hypercube names those axes.
Each dimension is itself an abstract concept, declared in xbrldt:dimensionItem. There are two flavours. Explicit dimensions have a closed list of taxonomy-defined member QNames, like a finite enumeration. Typed dimensions are open-ended; their values are arbitrary XML element values whose type is declared at the dimension itself. Most financial-statement taxonomies stick to explicit; supervisory frameworks like EBA DPM lean heavily on typed dimensions for things like counterparty identifiers.
A note on vocabulary that confuses newcomers daily. Major taxonomies (IFRS, US-GAAP, SRT, DEI) use "Axis" as a label suffix, so you will read concept names like StatementBusinessSegmentsAxis. The XDT spec itself never uses the word "axis"; it uses "dimension". Treat them as synonyms operationally: an axis is an explicit dimension, dressed in a label convention.
Hypercubes attach to primary items through has-hypercube arcs in the definition linkbase, with the all arcrole for "must apply" and notAll for "must not apply". Inside the cube, hypercube-dimension arcs link the cube to its dimensions, dimension-domain arcs to each dimension's root domain, and domain-member arcs (recursive) to the members. The dimensional content of an actual fact then lives in xbrli:segment or xbrli:scenario per the cube's contextElement attribute. ESEF forbids segment, so under the Reporting Manual every dimensional member sits inside scenario.
A hypercube is an abstract concept in xbrldt:hypercubeItem substitution group. It bundles a set of dimensions that together define the admissible space of contexts for one or more primary items.
A dimension (xbrldt:dimensionItem) defines an axis. Two flavours: explicit (members are taxonomy-defined QNames) and typed (members are arbitrary XML element values).
The convention 'Axis' as a label suffix (used by IFRS, US-GAAP, SRT, DEI taxonomies) means 'explicit dimension'. XDT itself uses 'dimension', not 'axis'.
Hypercubes attach to primary items via has-hypercube arcs (all and notAll arcroles) in the definition linkbase. all means the primary item must report against the hypercube; notAll excludes a sub-cube.
Each hypercube-dimension arc connects the hypercube to a dimension. dimension-domain connects the dimension to its domain root; domain-member connects the domain to its members (recursive).
Dimensional context lives in xbrli:segment or xbrli:scenario per the xbrldt:contextElement attribute on the has-hypercube arc. ESEF allows scenario only.
<xbrli:scenario>
<xbrldi:explicitMember dimension="us-gaap:StatementBusinessSegmentsAxis">
acme:AviationSegmentMember
</xbrldi:explicitMember>
</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.