European XBRL Taxonomy Architecture V2.0

From XBRLWiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 08:00, 11 June 2013 (edit)
Iboixo (Talk | contribs)
(Filing indicators)
← Previous diff
Revision as of 08:02, 11 June 2013 (edit)
Iboixo (Talk | contribs)
(Supporting concepts)
Next diff →
Line 187: Line 187:
|} |}
 +== Taxonomy architecture Description ==
== Public elements == == Public elements ==

Revision as of 08:02, 11 June 2013

CEN WS XBRL Experts: Thierry Declerck (DFKI), Roland Hommes (Rhocon), Katrin Heinze (Deutsche Bundesbank)

Contents

Foreword

Introduction

The purpose of this document is to present and explain the European XBRL Taxonomy Architecture (EXTA) defined by European supervisory authorities. In particular, it explains the scope (coverage of information requirements), modularization in files, manner of defining concepts and relations and other important design aspects. It is fully compatible with the Data Point Methodology approach. As DPMs are semantic models being created by supervisory experts, they are not formalized from a technical point of view. XBRL as formal language can fill this gap. XBRL as data format is standardized and can therefore be used to enable automated processes. XBRL taxonomies are metadata specifications that provide a formal description of the data requirements to be used as data format in the European reporting process. The document intends also to provide a description for IT experts about the linkage between a DPM as source and the XBRL taxonomy as target of a transformation process.

These pages are hosting the guidelines to an European XBRL Taxonomy Architecture (EXTA).

  • European: this project is funded by the EU commission to support the standardisation process for supervisory reporting in Europe, but there is no restriction in applying it anywhere else;
  • XBRL: this format has been chosen by the supervisory authorities EBA and EIOPA for the electronic data exchange between national banking supervisors and the European authorities;
  • Taxonomy Architecture: this architecture has been created to limit the wide variety of options to define an XBRL taxonomy; different European XBRL taxonomies for similar purposes cause incompatability and would lead to increased implementation costs for all adopters in the EU market.

Objective

The objective of the EXTA is to define a set of architecture guidelines that transforms an European DPM without a loss in quality in an XBRL format. The taxonomy architecture provides a set of rules for this transformation to enable the creation of consistent and predictable XBRL meta data definitions in an automated process. EXTA supports a modular structure to enable the extensibility of these taxonomies as well as to ease their maintenance. As EXTA is a formal representation of a DPM it contains several structural concepts which has no correspondance in other known XBRL architectures.

Target audience

EXTA is targetted at taxonomy authors. Initially organisations like EBA, EIOPA, ESMA, ECB etc. As a spin-off of these taxonomies, local (national) initiatives will emerge, hosted by National Supervisory Agencies (NSA's). To meet local legislation the European taxonomies may need to be extended with local requirements. The EXTA is also aimed at supporting these national extensions according to the same guiding principles. The main advantage being a consistent framework of XBRL taxonomies which enables a cost efficient implementation in software solutions.

Consistent taxonomies throughout Europe also creates the opportunity for cross-EU harmonisation of terminology and, in a later stage, consistent reported facts that are more easily analyzed since the underlying structure is the same and terms used are complementary to each other.

A consequence of a consistent taxonomy framework is that software developers can choose to support only the architectural guidelines of EXTA. Although this limits their software in supporting full fledged XBRL taxonomies it eases implementation costs.

This document is aimed at users of the Bundesbank taxonomies, in particular editors of the taxonomy or producers of instance documents (by applying mappings to internal systems or assigning XBRL tags with values in any other manner) as well as developers of the IT solutions facilitating reporting in the XBRL format or analysis of XBRL data.

Relationship to other work

The reader of this EXTA is expected to be familiar with the principles of data modelling and have a thorough understanding of the XBRL family of specifications to evaluate the impact of the rules set to the XBRL taxonomy that needs to be created.

Scope

The EXTA has been defined for the creation of XBRL Taxonomies in the context of European supervisory reporting. XBRL taxonomie following this architecture are published by an European supervisory authority to reflect the data requirements based on a DPM in a machine-readable form.

Normative references

The eXtensible Business Reporting Language (XBRL), see | XBRL Standard

The Extensible Markup Language (XML), see | XML Standard

Terms and definitions

Concept 
A concept is an XML element defined in the substitutionGroup xbrli:item or xbrli:tuple.
Data Point Model (DPM) 
A DataPointModel defines structures of data describing the characteristics of the information exchanged in the context of supervisory reporting processes.
Dimension 
A Dimension is a data set to one characteristic area which is composed of individual and non-overlapping data elements. In XBRL terms a dimension is an abstract concept in the substitutionGroup xbrldt:dimensionItem.
Domain 
A Domain is a classification system to categorize items that share a common semantic identity. A domain is an abstract concept and is the parent in a domain-member relationship. E.g. all individual countries can be members in a domain 'Countries'.
Family 
Families are groups of Dimensions relevant for presentation or querying purposes. In XBRL terms a family is an abstract concept in the substitutionGroup xbrli:item with the @type set to 'model:familyType'.
Framework 
A Framework is a business term common to a group of business users that consists of reporting regulations for a domain specific scope of information, like COREP, FINREP or Solvency II. Frameworks are public elements represented using XBRL abstract items with @type set to 'model:frameworkType' in schema 'fws.xsd'.
Item 
An item is an abstract XML element in the substitutionGroup xbrli:item that can be used to carry facts or to represent business measurements. The item is defined by XBRL International as a placeholder for creating concepts.
(Domain) Member 
A domain-member is discrete and countable. These Members can be explicitly defined in a domain. A member is an abstract concept in the substitutionGroup xbrli:item and is the child in a domain-member relationship.
Metric 
A metric represent the nature of the data with a fixed and unchangeable meaning. Metrics are strongly related to the underlying data type. Mostly they are numeric and quantitatively measurable but they can be also reflect boolean or date values. A metric also known in XBRL terms as primary is a non abstract concept in the substitutionGroup xbrli:item that is defined based on the unique combination of a (XML) type and xbrli:periodType.
Namespace 
The unique string in the form of an URI that is the @targetNamespace content of (a set of) XML schema file(s).
Owner 
The owner represents an European institution that defines concepts. The owner's namespace is a URI used to establish the namespace of the concepts defined by that owner.
Perspective 
Perspectives are extended linkroles that have a child node <link:usedOn>link:presentationLink</link:usedOn> AND contain only parent-child relationships in which families are the parent and dimensions are the child.
Public elements 
Public elements of DPMs are represented as concepts in XBRL taxonomies. They are identified by a code in a certain scope. They MAY include additional information such as readable labels, definitions and legal references in different languages.
SubstitutionGroup 
An XML attribute to classify a complexType of simpleType element so its construction can be re-used by other elements.
TableGroup 
A TableGroup is a set of Tables that represents a business template. In XBRL terms tableGroups are public elements represented using XBRL abstract items with @type set to 'model:tableGroupType'.
Taxonomy 
Taxonomies are defined as part of the DPM. It represents a version of the framework; kind like a 'name' for the set of definitions used in the framework that are not part of the dictionary. There is a virtual link with the XBRL term 'taxonomy' which is a set of concepts with their relationships and definitions. The XBRL taxonomy has much wider definition than the EXTA one. Taxonomies are public elements represented using XBRL abstract items with @type set to 'model:taxonomyType' in schema 'tax.xsd'.

European XBRL Taxonomy Architecture

Supporting concepts

Taxonomy levels and owners

Taxonomy concepts could be defined on one of the three levels:

  1. cross sector concepts and breakdowns (to be shared between different institutions e.g. banking, insurance and securities supervision),
  2. concepts from information requirements of an European supervisory authority,
  3. concepts defined by a NSA.

Level one are cross sector concepts that shall be eventually defined and agreed by a joint group of experts involved in setting up information requirements for different sectors such as banking, insurance and reporting of other commercial and non-profit companies. It is expected, that these concepts will mainly include the list of countries and currencies as defined by the ISO codes and subsequently extended by for example economy sectors, classes of financial instruments, accounting portfolios, time intervals, etc. This task will be most likely conducted by reconciliation between the dictionaries of business concepts defined by the EBA, EIOPA and other interested parties. Cross sector concepts will be published in the Eurofiling on-line resources as a set of XBRL schema and linkbase files that can be referenced from level two or level three dictionaries.

Level two are the concepts of an European supervisory authoriy. They represent the information requirements of COREP, FINREP, Solvency II and other scope defined on the European level. They may refer to and extend level one (cross-sector) concepts.

Level three are the concepts of national supervisors. They reflect information requirements set by a national legislation and specific banking regulations.

The idea of levels for concepts definitions has been addressed in the XBRL taxonomy model by introducing the notion of the owner. The owner represents an institution that defines concepts of the model. The owner is closely related to the idea of extensibility in XBRL. The main properties of the owner are:

  • owner’s namespace {ons},
  • owner’s prefix {opre}, and
  • official location {oloc}.

The owner namespace {ons} is a URI used to establish the namespace of the concepts defined by that owner. This URI is generally built by adding xbrl to the internet domain of the institution that the owner represents. In case of the Bundesbank, the domain is extended by stat and sprv components to distinguish between statistical and supervisory datasets. The prefix {opre} is used as the basis to establish namespace prefixes in taxonomy files and for some short representations of the concepts by QNames using shorter prefixes (instead of long namespaces) plus the local name.

Official location {oloc} is a URL used to specify the location where taxonomy files associated to that owner are to be published. Different owners must have different official locations, even owners with the same internet domain/same namespace. The official location is generally built by adding three parts to the internet domain of the institution:

  • representation of the geographical area covered by the institution (e.g. eu in case of the cross sector or the EBA concepts or es for the national specific concepts applied in a sample Europea country),
  • indication of the scope of information requirement (e.g. fr for general financial reporting)
  • fixed xbrl component identifying the type of standard used to express information requirements.

The following table presents examples of owners and applied namespaces, prefixes and official locations of taxonomy files.

Owner Namespace Prefix Official location
Cross-sector http://www.eurofiling.info/xbrl eu http://www.eurofiling.info/eu/fr/xbrl
EBA http://www.eba.europa.eu/xbrl eba http://www.eba.europa.eu/eu/fr/xbrl
Banca d’Esmirna http://www.bde.se/xbrl se http://www.bde.se/se/fr/xbrl

Copyright: text used as a header in every taxonomy file published by its owner.

Filing indicators

Filing indicators serve the purpose of communicating the scope of the reported data based on templates. The main purposes of filing indicators are:

  • provide hints to applications using the taxonomy, on which templates/forms are included in the filing and for example shall be displayed to users,
  • trigger execution of business rules (value assertions) to be run on a filing to check its correctness depending on the reported scope of data.

In technical terms, filing indicators are facts included as part of an instance document where the filer estates which templates/forms are being reported. Each template/form is represented as an instance fact of the item “table” under the “fIndicators” tuple element. These elements are defined in the namespace http://www.eurofiling.info/xbrl/ext/filing-indicators. The official location of this schema file is http://www.eurofiling.info/eu/fr/xbrl/ext/filing-indicators.xsd. This schema file is imported in every taxonomy module.

Throughout this document, the prefix find will be used to make reference to this schema namespace.

The following instance excerpt represents a filing with information about templates/forms with codes CA1 and MKRSAEQU:

<find:fIndicators>
   <find:table contextRef=”ctx”>CA1</find:table>
   <find:table contextRef=”ctx”>MKRSAEQU</find:table>
</find:fIndicators>

The following instance excerpt represents a filing with information about tables with code 100 and 200:

<find:fIndicators>
   <find:table contextRef=”ctx”>100</find:table>
   <find:table contextRef=”ctx”>200</find:table>
 </find:fIndicators>

Context to which facts representing find:table element refer must identify the reporting entity and use the instant date which is the end date of the reporting period.

Table codes to be used on find:table facts are the ones identified by {template code} component of the documentation label of tabel:table resource (see 6.4.5.3 Tables). If a template results in multiple tables (as a result of its original arrangement in multiple physical tables or due to normalization process) it is identified by find:table fact only once.

Filing indicators are facts included as part of an instance document where the filer estates which tables are being reported. Each table is represented as an instance fact of the item “table” under the “fIndicators” element. These elements are defined in the namespace http://www.eurofiling.info/xbrl/ext/filing-indicators. The official location of this schema file is http://www.eurofiling.info/eu/fr/xbrl/ext/filing-indicators.xsd. Throughout this document, the prefix “find” will be used to make reference to this schema namespace.

This approach enables a clear separation between business facts (under the xbrli:xbrl element) and additional data required in the reporting process. Moreover, it does not require the addition of filing indicators to the dictionary of concepts, as filing indicators are defined in a generic way in its own schema.

Filing indicators include a Boolean attribute named “find:filed” with default value “true”. Tables not filed can be omitted from the list of filing indicators or have an entry with the “find:filed” attribute equal to “false”. The latter is especially useful if a footnote explaining the reasons for not filing a table want to be included.

Model supporting schema

The XBRL representation of the model makes use of some schema definitions in the namespace http://www.eurofiling.info/xbrl/ext/model. The official location of this schema file is http://www.eurofiling.info/eu/fr/xbrl/ext/model.xsd. Throughout this document, the prefix “model” will be used to make reference to this schema namespace.

Namespaces

The following table shows the prefixes used throughout this document as an abbreviated reference to namespaces:

Prefix Namespace
xbrli http://www.xbrl.org/2003/instance
xbrldt http://xbrl.org/2005/xbrldt
link http://www.xbrl.org/2003/linkbase
xl http://www.xbrl.org/2003/XLink
gen http://xbrl.org/2008/generic
iso4217 http://www.xbrl.org/2003/iso4217
nonnum http://www.xbrl.org/dtr/type/non-numeric
num http://www.xbrl.org/dtr/type/numeric
model http://www.eurofiling.info/xbrl/ext/model
find http://www.eurofiling.info/xbrl/ext/filing-indicators
pvar http://www.eurofiling.info/xbrl/ext/pivot-variable
iaf http://www.eurofiling.info/xbrl/functions/interval-arithmetics
variable http://xbrl.org/2008/variable

Taxonomy architecture Description

Public elements

Public elements are all concepts based on a DPM that are identified by a code in a certain scope and may include some additional information such as readable labels, definitions and legal references in different languages.

Public elements include two attributes to reflect their creation date (model:creationDate) and the date when they was last modified (model:modificationDate).

Language specific information of public elements is represented using the following label resources: XBRL 2.1 labels (link:label) for xbrli:items (or derived) public elements,

  • generic labels (label:label) for public elements represented as XLink resources or other construct (e.g. link:roleTypes).
  • The default (standard) role (http://www.xbrl.org/2003/role/link) is used for the extended links containing the label resources.

The role types used as roles for generic and standard label resources are presented in the following table.

Property Generic label role Standard label role
Name http://www.xbrl.org/2008/role/label http://www.xbrl.org/2003/role/label
Definition http://www.xbrl.org/2008/role/verboseLabel http://www.xbrl.org/2003/role/verboseLabel
Legal references http://www.xbrl.org/2008/role/documentation http://www.xbrl.org/2003/role/documentation

The labels of the concepts of a schema or a linkbase file are represented jointly in a separate label linkbase file distinguished by language, in the same folder as its corresponding schema or linkbase file. Each language is stored in a separate label linkbase file. The naming convention for these label linkbase files is:

  • {main-file}-lab-{lang}.xml

where {main-file} corresponds to the name of the schema or linkbase file where the concept is defined (without extension) and {lang} component represents the ISO 639-1 code of the language (lowercase).

In addition to this, some concepts of the dictionary may contain a special linkbase to represent codes needed for different purposes. In particular, the codes given to the columns and rows of tables or codes assigned to the data points are represented using this mechanism. The name of these linkbase files constructed as follows:

  • {main-file}-lab-{lang}-codes.xml or {main-file}-lab-codes.xml

In case of the later, the distinction between codes appearing in different language versions is determined basing on xml:lang attribute on label resources. The labels for these codes are represented as resources with a custom role. The role defined in the model.xsd schema for resources representing codes of rows or columns is http://www.eurofiling.info/xbrl/role/rc-code.

Dictionary of concepts

The core concepts of the dictionary are metrics, dimensions, domains and domain members. Secondary concepts are families and perspectives (auxiliary concepts meant to group dimensions for presentation purposes). All the concepts in the dictionary are public elements.

To cope with changes in the reporting, in addition to the properties and language specific information of public elements, dictionary elements include two optional attributes that establish its currency period: the starting date of the period interval (model:fromDate attribute) and its end date (model:toDate attribute). If the model:fromDate attribute is not included, then the concept is assumed to be valid for any period prior to the model:toDate attribute. If the model:toDate attribute is not included, then the concept is assumed to be valid for any period after the model:fromDate attribute. If neither model:fromDate nor model:toDate attributes are included, then the concept is assumed to be current for any period of time. The first versions of the dictionary will not include these attributes. As new versions are released and some concepts become obsolete and replaced by others, these attributes will be updated. These attributes don’t have any impact on the reporting process itself; they are meant to simplify the management of the concepts of the dictionary.

All files in the dictionary of concepts are placed under the folder dict in the official location of its owner (see Table 3). Its namespace is obtained by adding a suffix that depends on the type of element to the namespace of the owner. The prefix to represent that namespace is obtained by adding a predefined suffix to the prefix of its owner (as presented in Table 4) where {oloc} represents the official location of taxonomy files of the owner of the concepts, {ons} its base namespace, {opre} the prefix of its base namespace, and {dc}/{DC} the code of a domain in lower and capital case.

Dictionary concept Official location Target namespace Namespace prefix
Metrics {oloc}/dict/met/met.xsd {ons}/dict/met {opre}_met
Dimensions {oloc}/dict/dim/dim.xsd {ons}/dict/dim {opre}_dim
Explicit domains {oloc}/dict/dom/exp.xsd {ons}/dict/exp {opre}_exp
Typed domains {oloc}/dict/dom/typ.xsd {ons}/dict/typ {opre}_typ
Explicit domain members {oloc}/dict/dom/{dc}/mem.xsd {ons}/dict/dom/{DC} {opre}_{DC}

Examples of location, target namespace and its prefix for dictionary concepts of the taxonomy are listed below:

Dictionary concept Official location Target namespace Namespace prefix
Cross-sector metrics http://www.eurofiling.info/xbrl/dict/met http://www.eurofiling.info/eu/fr/xbrl/dict/met/met.xsd eu_met
Cross-sector dimensions http://www.eurofiling.info/xbrl/dict/dim http://www.eurofiling.info/eu/fr/xbrl/dict/dim/dim.xsd eu_dim
EBA explicit domains http://www.eba.europa.eu/xbrl/dict/exp http://www.eba.europa.eu/eu/fr/xbrl/dict/dom/exp.xsd eba_exp
EBA typed domains http://www.eba.europa.eu/xbrl/dict/typ http://www.eba.europa.eu/eu/fr/xbrl/dict/dom/typ.xsd eba_typ
SE explicit domain members example (domain CP) http://www.bde.se/xbrl/dict/dom/CP http://www.bde.se/se/fr/xbrl/dict/dom/CP se_CP
EBA families http://www.eba.europa.eu/xbrl/dict/fam http://www.eba.europa.eu/eu/fr/xbrl/dict/dim/fam.xsd eba_fam
EBA perspectives http://www.eba.europa.eu/xbrl/dict/pers http://www.eba.europa.eu/eu/fr/xbrl/dict/dim/pers.xsd eba_pers

Metrics

Metrics define the nature of the measure to be performed. Metrics determine the data type, the period type (instant / duration) plus additional semantics of their corresponding data points. Metrics are represented in XBRL as primary items and defined in schema files named met.xsd that reference label linkbase files. A local name of metrics is composed of three components:

  1. a letter that represents the data type in lower case (for available options see the table below),
  2. a letter that represents the period type: i for instant and d for duration,
  3. a number that corresponds to the numeric code in the model (no zero padding or predetermined length).
Model data type XBRL data type Local name codification letter Reporting unit
Monetary (currency) xbrli:monetaryItemType m Adequate currency using ISO 4217 codification (e.g.: iso4217:EUR)
Percent num:percentItemType p xbrli:pure
Decimal xbrli:decimalItemType p xbrli:pure
Integer xbrli:integerItemType i xbrli:pure
Date xbrli:dateItemType d not applicable
Boolean xbrli:booleanItemType b not applicable
Text xbrli:stringItemType s not applicable
Explicit domain xbrli:qnameItemType e not applicable
Typed domain typed domain corresponding data type, e.g. xbrli:stringItemType if a typed domain is xs:string

In case of domain based data types, an additional attribute (model:domain) is included to identify the qualified name of the explicit or typed domain (e.g. model:domain="eba:GA").

The id of the element (necessary for XLink locators) is composed as:

{opre}_{name}

where {opre} represents the prefix of the base namespace of the owner of the base item and {name} represents the name described above.

The following table contains a few examples of metrics declared in a taxonomy.

Owner Data / period type Code Name Id Namespace Prefix
Cross-sector Boolean / duration 3 bd3 eu_bd3 http://www.eurofiling.info/xbrl/dict/met eu_met
Cross-sector Monetary / duration 7 md7 eu_md7 http://www.eurofiling.info/xbrl/dict/met eu_met
EBA Monetary / instant 7 mi7 eu_mi7 http://www.eba.europa.eu/xbrl/dict/met eba_met
EBA Text / instant 7 si7 eu_si7 http://www.eba.europa.eu/xbrl/dict/met eba_met
BdE Boolean / duration 3 bd3 se_bd3 http://www.bde.se/xbrl/dict/met se_met
BdE Monetary / duration 7 md7 se_md7 http://www.bde.se/xbrl/dict/met se_met

Metrics can be arranged in hierarchies. Hierarchies are represented using XBRL extended link roles whose role type URI is built according to the following pattern:

{ons}/role/dict/mem/{hierarchy-code}

where {ons} represents the namespace of the owner and {hierarchy-code} the numeric code of the hierarchy. Value of id attribute of these roles is composed following the pattern:

{opre}_{code}

Examples of extended link roles used for hierarchies of metrics are presented in the table below:


As a DPM is the source of a transformation process with an XBRL taxonomy as its target graph transformations are being used to describe how the structure of a DPM, represented as class diagram in UML, is mapped to an UML class diagram visualising the underlying XBRL structure. To express the model transformation the UML source model of the DPM as well as the UML target model for representing the XBRL structure is given. Between the two graphs an abstract transformation syntax is used to describe the transformation rules from the source to the target model. The graph transformation intends to ease the understanding of the correlation between data structures reflected in Data Point Models and how these objects and structures can be matched to an XBRL data format. The graph transformation is limited to an essential part of the whole process. UML class diagrams reflecting the XBRL specification structure are visualized in the Aspect Model 2.0 of XBRL International.

The transformation process starts from the DPM UML graph on the left hand side marked in blue to the UML class diagram using red squares to visualize the XBRL structure. The black arrows between both UML class diagrams are not part of the general UML language but customized extensions which are used to describe the graph transformation. The square between two black arrows contains an abbreviation what is being mapped. We distinguish eight different types of mappings rules between the two graphs:

  • C2C - transformation from an UML class in the DPM meta model in an UML class representing an XBRL concept,
  • A2A - transformation from an attributevof a DPM meta class to an attribute of an XBRL element,
  • A2R - transformation from an attribute of a DPM meta class to a XBRL resource as part of an XBRL linkbase,
  • A2E - transformation from an attribute of a DPM meta class to its XML element representation in XBRL,
  • C2RS - transformation of an UML class of the DPM meta model to an UML class representing an Relationship which is located in an XBRL linkbase,
  • RS2RS - transformation of an UML class of the DPM meta model representing an Relationship to an UML class representing an Relationship which is located in an XBRL linkbase,
  • C2Arc - transformation of an UML class of the DPM meta model to an XBRL arc combining two XBRL elements, in the given examples resources,
  • C2E - transformation of an UML class of the DPM meta model to a table linkbase specific XBRL element which links to an XBRL concept.

Image:Metrics.jpg

The graph above shows how the meta class DimensionedElement of the DPM meta model is mapped to an XBRL concept with its corresponding XBRL attributes according to the EXTA definitions. Dimensioned Elements are known as metrics in the EXTA (synonym in XBRL: Primary item). Dimensioned Elements are part of the Dictionary so they inherit the attributes defined by the abstract concept of a Dictionary element. The abstract Dictionary element is subordinated element of the abstract meta class representing a Public element so the Dimensioned Element inherits also the attributes defined by this superordinated element. In XBRL terms a metric in EXTA must include at least the attribute model:creationDate of the custom attributes.

Personal tools