Pick up any XBRL document and the first thing you will see is colons. Hundreds of them. `ifrs-full:Revenue`, `bw2-titel9:Assets`, `us-gaap:OperatingIncomeLoss`, `xbrli:item`. That syntax is doing real work; it is the way XBRL says exactly which concept it means out of the millions in the world.
A QName is a qualified name in the W3C Namespaces in XML 1.0 sense: a prefix, a colon, and a local part. The prefix is bound to a namespace URI by an `xmlns:prefix="URI"` declaration somewhere in scope. Two prefixes bound to the same URI are interchangeable. The lexical form `p1:Revenue` is identical to `p2:Revenue` if both prefixes resolve to the same URI; XML processors compare expanded names, which are pairs of (URI, local name), not the lexical prefix.
That is more than a curiosity. It means renaming a prefix is harmless; switching the URI bound to a prefix is not. A taxonomy upgrade that kept your prefix but changed your URI just broke every reference. A prefix used but never declared makes the document not even namespace-well-formed; XBRL semantic checks have not started yet because XML namespace processing has already failed.
The Open Information Model uses these expanded names as the keys of identity. A QName-typed value (a fact reference, a tuple member, a typed-dimension target) survives serialisation to xBRL-XML, xBRL-JSON, or xBRL-CSV because the expanded name is what carries across, not the prefix.
NCName (non-colonized name) is the cousin you meet on attribute values. Every XBRL id (`f-Revenue-2025`, `c-Group-2025`, `u-eur`) is an NCName: a valid XML name with no colon and a leading letter or underscore. The id is opaque structural plumbing, not a QName, and it does not carry a namespace.
The substantive trap is namespace selection in jurisdictional taxonomies. Each concept in a taxonomy lives in exactly one namespace. The Dutch stack is a textbook case: `bw2-titel9` for legal-form core concepts, `rj` for the extended Dutch reporting concepts, `kvk` for chamber metadata. `rj:Assets` and `bw2-titel9:Assets` are not synonyms; only one of them exists. Pick the wrong namespace and the calculation tree silently drops an arc, the validator might shrug, and the filing is wrong.
Every concept is identified by a QName: a prefix plus a local part. The prefix is bound to a namespace URI by an xmlns declaration in scope.
Two prefixes bound to the same namespace URI refer to the same expanded name. Validators compare expanded names, not lexical prefixes.
If a prefix is used but never declared, the document is not even namespace-well-formed; XBRL validation has not started yet.
An expanded name (the value-space form) is the pair of namespace URI and local name. This is what consumers compare. The xs:QName datatype carries this value.
In XBRL Open Information Model, QName-typed values are resolved through a prefix map, which is how the same fact survives serialisation to xBRL-XML, xBRL-JSON, and xBRL-CSV.
Each concept lives in exactly one namespace per taxonomy. Picking a jurisdiction-extension namespace (rj:) when the core concept exists in another (bw2-titel9:) silently breaks the calculation tree.
<xs:element name="Revenue"
id="ifrs-full_Revenue"
type="xbrli:monetaryItemType"
xbrli:periodType="duration"
xbrli:balance="credit"
substitutionGroup="xbrli:item"
nillable="true"
abstract="false"/>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.