70 likes | 298 Views
COREP. Taxonomy model. template taxonomy. dimension taxonomies. SA Capital Requirements. SAEX. RW. EC. ET. all possible items for this template. COREP. Taxonomy model. central bank specific taxonomy. centralbank. items selected by the central bank within a tuple.
E N D
COREP Taxonomy model template taxonomy dimension taxonomies SA Capital Requirements SAEX RW EC ET • all possible items for this template
COREP Taxonomy model central bank specific taxonomy centralbank • items selected by the central bank within a tuple template taxonomy dimension taxonomies SA Capital Requirements SAEX RW EC ET • all possible items for this template
COREP Taxonomy model <context id="context-1"> <entity> <identifier scheme="www.sample.com">entity-1</identifier> <segment> <dims:dimensionalMetaData> <dims:dimensionMember dimensionRef="id_et"> et:TotalByExposureType</dims:dimensionMember> <dims:dimensionMember dimensionRef="id_ec"> ec:Institutions</dims:dimensionMember> <dims:dimensionMember dimensionRef="id_rw"> rw:TwentyPercent</dims:dimensionMember> <dims:dimensionMember dimensionRef="id_saex"> saex:PastDue</dims:dimensionMember> </dims:dimensionalMetaData> </segment> … <t-sa-cr:ExposureValue contextRef="context-1" unitRef="unit-1" precision="19">22000</t-sa-cr:ExposureValue> centralbank dimension taxonomies SA Capital Requirements SAEX RW EC ET
COREP Pros (1/2) • easy to build and implement • very flexible (each template could be connected with every dimension) • easy to maintain because of the division in several taxonomies • the calculation linkbase can be used for all taxonomies • slim taxonomy because of using the context to build up the multi- dimensions
COREP Pros (2/2) • the connections between the template taxonomy and the dimensions are built up in the instance document • the taxonomy can be extended by central banks • the COREP taxonomy will be a reference for the new functionality of multi- dimensions in XBRL • new for XBRL but valid according the specification 2.1
COREP Cons (1/2) • a calculation is only possible in one context with software that exist today • no XBRL validation of the dimensions in the context till new software appears • actual validations are implemented using xml schema only • no limitation of the dimensions in the templates is possible all templates can be connected with all dimensions
COREP Cons (2/2) • multi-dimensions in XBRL are not specified yet and should be discussed in the XBRL specification or domain group • with the actual version of the dimensions the instance documents show the connections between templates and their possible dimensions