The definition linkbase is the one most reviewers skip until something breaks. It does not order rows like presentation does, and it does not assert sums like calculation does. Instead, it carries the deeper wiring of the report: which dimensions slice which primary items, which member belongs to which domain, and (for ESEF filers) which extension concept anchors to which base concept in the IFRS taxonomy.
The arcroles here are different in flavour. Some come from XBRL Dimensions: the all and notAll arcroles on has-hypercube arcs, plus hypercube-dimension, dimension-domain, domain-member, and dimension-default. Others come from ESEF, most importantly the wider-narrower arcrole used for anchoring under Reporting Manual section 1.4.1 and RTS Annex IV section 9(b). All of them live on link:definitionArc elements, and reading them means tracking the arcrole on each arc rather than assuming a uniform meaning.
Two attributes on the has-hypercube arc deserve named attention. xbrldt:contextElement chooses where the dimensional members appear in an instance context, either inside xbrli:segment or inside xbrli:scenario. The choice has consequences: ESEF Reporting Manual section 2.1.3 forbids segment outright, so an ESEF linkbase that declares contextElement equal to segment has already booked a finding before a single fact is written. xbrldt:closed equals true tightens the hypercube further: the context container must contain only the listed dimensions, nothing else. Open hypercubes tolerate extra dimensions that are not declared on the cube; closed hypercubes do not.
Default members are where the linkbase quietly cooperates with the instance. A dimension-default arc names the member assumed when the explicit dimension is absent from a context. Default members are implicit. Emit one explicitly and you trip xbrldie:DefaultValueUsedInInstanceError, the most common dimensional error in the wild. Declare two defaults for the same dimension and you raise xbrldte:TooManyDefaultMembersError instead, which is a DTS-level problem rather than an instance one.
When debugging, treat the definition linkbase as the source of dimensional truth, not the instance. The instance is just executing whatever shape the linkbase has wired.
Definition arcs carry XDT-specific arcroles: all (has-hypercube positive), notAll (has-hypercube negative), hypercube-dimension, dimension-domain, domain-member, dimension-default.
ESEF anchoring lives in the definition linkbase. wider-narrower arcs link extension concepts to base concepts (Reporting Manual 1.4.1; RTS Annex IV section 9(b)).
xbrldt:contextElement on the all and notAll arcs picks segment or scenario for the dimensional context container.
Closed hypercubes (xbrldt:closed='true') restrict reporting to exactly the listed dimension members. notAll arcs exclude sub-cubes.
Default members are implicit. A dimension-default arc names a member that is assumed when the explicit dimension is absent in the context.
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.