European Data Point Methodology
From XBRLWiki
| Revision as of 07:49, 8 March 2013 (edit) Hommes (Talk | contribs) (→Terms and definitions) ← Previous diff |
Revision as of 07:55, 8 March 2013 (edit) Hommes (Talk | contribs) (→Dictionary Element) Next diff → |
||
| Line 91: | Line 91: | ||
| ===Dictionary Element=== | ===Dictionary Element=== | ||
| - | Dictionary Elements are abstract elements that build the basis of the core concepts of a data point model like dimensioned elements, dimensions, domains and domain members. They are derived from public elements and may define a currency period to enable a filtering of obsolete elements by applications. The currency period is defined by two optional attributes ''validFrom'' and ''validTo'' which should ease the maintenance of elements of the data point model in the course of time. | + | Dictionary Elements is an abstract class of elements that build the basis of the core concepts of a data point model like dimensioned elements, dimensions, domains and domain members. They are derived from public elements and may define a currency period to enable a filtering of obsolete elements by applications. The currency period is defined by two optional attributes ''validFrom'' and ''validTo'' which should ease the maintenance of elements of the data point model in the course of time. |
| <span style="background-color:yellow">[[Talk:European_Data_Point_Methodology#Comment-06|Comment-06]]</span><br/> | <span style="background-color:yellow">[[Talk:European_Data_Point_Methodology#Comment-06|Comment-06]]</span><br/> | ||
Revision as of 07:55, 8 March 2013
CEN Workshop Agreement
Status: Working Group Working Draft
Editing rules
Editorial comments should be highlighted as follows: A comment
Text or rules in discussion (white): Some text
Text or rules already aligned (green): Some text
Text or rules to be deleted (red): Some text
Text to be delivered (blue): Some text
Contents |
Foreword
Some text
Introduction
Data Point Modeling is a data oriented methodical procedure to create semantic and multidimensional models that reflect the reporting requirements of European supervisors. Reporting requirements are defined by regulations and represented in tables. First Data Point Models were developed in 2009 to describe the data in a redundancy-free, consistent and unambiguous way.
A Data Point Model reflects semantic and multidimensional aspects of data modeling. Semantic models are used to ease the communication between domain experts and IT specialists. Whereas formal models are defined for technical purposes semantic models are defined from a viewpoint of a domain user. They can contain definitions, documentations and explanations. Domain experts decide which objects are relevant and which relations exists between the objects of the model. Semantic models are independent of any physical implementation.
The characteristic of multidimensional models is the division of data in quantitative and qualitative aspects. Parameters that are meas-ured in figures (also known as metrics) are quantitative aspects that often build the basis of data analyses. Qualitative aspects provide a closer description for these parameters. Data objects based on multidimensional models are referred to as facts. Fact attributes are the quantitative aspects of a fact and dimensions are the synonym of the qualitative aspects of a fact.
Data Point Models should enhance the understanding of the data requirements for the reporting entities by providing information to cor-relations that exceed the information given only by table structures. The main challenge in data modeling is the identification of implicit information given in tables and its transformation in an explicit and logical model. As Data Points Models are semantic models they are created by banking specialists who are highly skilled in understanding supervisory reporting frameworks.
The document intends to support the communication between supervisory experts and IT experts by introducing the concept of data point modeling and its underlying terms. Data Point Models remain as semantic models at first technologically-neutral but they are used by IT specialists (1) for generating data formats for the reporting process or (2) for designing multidimensional database structures for the analysis of supervisory data.
This guidance is in the form of notes in association with the pertaining requirements clause and uses the terms “MUST” (strong recommendation), “SHOULD” (recommendation) and “MAY” (possibility). Organizations wishing to implement this CWA (CEN Workshop Agreement) would be expected to consider all recommendations where the terms "MUST" and “SHOULD” are used.
Objective
A Data Point Model consists of objects that reflect the supervisory data and its relations among each other that can be communicated and understood by computers. The objects of a data point model described in this document facilitate the ease of understanding of the data structure for technicians and reflects the rules to be met when using a data point model as basis for the generation of a data format or as basis for analysis purposes.
Target Audience
This document is being created to support Information Technology (IT) experts in the transfer of content from regulatory reporting to IT systems. It assumes that the reader has a working knowledge of the XBRL 2.1 and the XBRL Dimensions 1.0 Specifications as Data Point Models are being used as basis for generating XBRL taxonomies. Furthermore basic knowledge about Business Intelligence is assumed to understand the rules to be followed when designing multidimensional database structure for data warehouses.
Relationship to Other Work
Some text
Scope
The Data Point Methodology has been defined for the creation of data point models in the context of European supervisory reporting. Data Point Models are published by an European supervisory authority. To reflect the defined structures in a machine-readable form they can be accompanied by an XBRL taxonomy.
Normative references
Some text
Terms and definitions
There are no formal definitions that are taken from other documents. Comment-04
Data Point Meta model
The data point meta model provides (1) the components for the construction of a formal model that describes sets of data points relevant to European supervisory reporting frameworks, (2) rules on how to combine these components and (3) the meaning (semantic) of the components and relations. Similar to a model construction kit for toys it provides the modelling principles with all characteristics available for use by the modeller. A UML class diagram is used to provide the syntax and semantic to define the meta model for data points by showing the relevant classes and their attributes.
Structural Perspective
Data Point Model
A Data Point Model (DPM) defines structures of data describing the characteristics of the information exchanged in the context of supervisory reporting processes. A DPM consists of a dictionary of business concepts and their properties which are represented in tables. It identifies the content of each data point by its granular components with a semantic meaning and its relation to other data points.
From an IT perspective a DPM can be interpreted by IT applications which enable (1) a generation of data formats for the reporting process or (2) the design of multidimensional database structures for the analysis of supervisory data, i.e., in data warehouses.
References:
| meta class | multiplicity | description |
|---|---|---|
| Public Element | one or more | References the collection of Public Elements owned by a Data Point Model. |
Public Element
A public element is a generalization of a concept of the model. It is identified by a code and consists of an appropriate label. Public elements have two additional attributes giving information about the date of creation and modification. Each public element is owned by an institution or an organization. The owner needs to be made explicit in the data point model. Public elements are abstract and need to be specified by its concrete sub classes like frameworks, tables etc.
References:
| meta class | multiplicity | description |
|---|---|---|
| Data Point Model | one or more | References the Data Point Model owning the collection of Public Elements. |
Dictionary Element
Dictionary Elements is an abstract class of elements that build the basis of the core concepts of a data point model like dimensioned elements, dimensions, domains and domain members. They are derived from public elements and may define a currency period to enable a filtering of obsolete elements by applications. The currency period is defined by two optional attributes validFrom and validTo which should ease the maintenance of elements of the data point model in the course of time.
Superclass: Public Element
Dimension
A dimension is a data set to one characteristic area which is composed of individual and non-overlapping data elements. In the context of a data point model dimensions are used to group information in a meaningful way. Dimensions are used to define "by" conditions and provide structured information to describe a data point in detail. A dimension can refer to a enumerable domain with a definite number of elements or an innumerable domain where the members are defined by a data type and some additional constraints.
Superclass: Dictionary Element
References:
| meta class | multiplicity | description |
|---|---|---|
| Domain | exactly one | References the Domain associated with a Dimension. |
Domain
A Domain is a classification system to categorize items that share a common semantic identity. A domain provides therefore an unambiguous collection of items in a value range. The items of a domain can have a definite, and therefore countable, number of items, or an infinite number of elements that follow a specific pattern.
Superclass: Dictionary Element
References:
| meta class | multiplicity | description |
|---|---|---|
| Dimension | exactly one | References the Dimension associated with a Domain. |
Enumerable Domain
An enumerable domain is a subclass of domain that specifies a definite number of members.
Superclass: Domain
Contained elements: Member Set
References:
| meta class | multiplicity | description |
|---|---|---|
| Member Set | exactly one | References the set of members owned by a Enumerable Domain. |
Non-enumerable Domain
A non-enumerable domain is a subclass of domain that specifies an undefined number of members in the domain. The non-enumerable domain defines syntactic constraints on the values of the members, i.e. a data type or a specific pattern.
Superclass: Domain
Member
A member is the actual value that is given to a dimension. Members are grouped in domains. Members in a domain share certain semantic identity.
Superclass: Dictionary element
Defined Member
A defined member is discrete and countable. A number of these members can be explicitly listed in an enumeration.
Superclass: Member
Non-defined Member
A non-defined member is defined by syntactic constraints on a possible value, not the value itself.
Superclass: Member
Dimensioned Element
Dimensioned elements represent the nature of the data with a fixed and unchangeable meaning. Dimensioned elements are strongly related to the underlying data type. Mostly they are numeric and quantitatively measurable to be used for calculations and aggregations but they can be also reflect boolean or date values. A dimensioned element is the essential part of a data point that can also refer to zero or more dimensions with its according set of members.
- The attribute dataType establishes the set of possible values of the facts reported according to that metric: monetary information, percentages, dates, texts…
- The attribute periodType defines whether the property / amount to be measured corresponds to a specific moment in time (instant type) or whether its nature requires it to be obtained by taking measures during an interval of time (duration type).
Superclass: Dictionary Element
Dimension
Whereas the Dimensioned Element represents the quantitative aspects, the qualitative aspects are described by dimensions. The values given to dimensions are called members.
Contained elements: Family
References:
| meta class | multiplicity | description |
|---|---|---|
| Data Point Model | zero or more | References the collection of Dimensions owned by a Data Point Model. |
Family
Families are groups of dimensions only relevant for presentation purposes.
Superclass:Dimension Set
Versioning Perspective
A Data Point Model combines the reporting regulations for several specific scopes of information (solvency information, financial information…) summarized in one or more Frameworks. The name of a Framework is stable in time but the business templates referring to a framework change according to amended reporting requirements in the course of time. A taxonomy represents a set of reporting requirements which are enforced by normative or legal acts for a period of time. The currency period starts with the entry into force of the law. In general a new taxonomy version replaces the previous one and the currency period of the old one ends before the new version becomes valid. A taxonomy consists Dictionary Elements that are valid for the currency period given by the taxonomy. Dictionary Elements which validTo date ended before the currency period start are not part of the taxonomy. Over the course of time several taxonomy versions exists which refer to one Framework.
In order to reduce the cost of maintenance, tables from previously released taxonomies that have not suffered any modification can be referred from a new taxonomy.
Framework
A framework consists of reporting regulations for a domain specific scope of information. The information requirements are structured in the form of tables to ease the understanding for the institutions that are obliged to submit the reporting information to the supervisor. All business rules to be met by the reporting entities are defined in the reporting regulations. Some of these rules are also incorporated in the table design to show which detailed information is being part of a summation.
A DPM can refer to one or more supervisory frameworks. Information should be given to which framework the defined elements of the DPM refer to.
Superclass: Public Element
Taxonomy
A taxonomy, which is related to a framework, is a specific view on a DPM for a specific period in time. Its currency period is defined by the attributes validFrom and validTo. Only those dictionary elements are part of the taxonomy that are still valid for the defined period of time. Public elements like tables and hierarchies that have not been modified can be reused from the previous taxonomy version.
Superclass: Public Element
Business Template
The data requirements for supervisory purposes are described in guidelines or legal-normative standards. To ease the understanding of these regulatory texts supervisory experts provide business templates that show the data requirements in a convenient table structure. From a DPM perspective a template is just one possible representation of supervisory data in a specific business context. However, tables are used for the communication between supervisors and reporting entities so the DPM must contain presentational information to reconstruct the known tables on demand.
Table
For presentational purposes data Points can be grouped in tables or in groups of tables. These tables can reflect the structure of the business templates or just individual views on supervisory data based on a specific business context.
A table consists of the combination of one or more axes which from the columns in the x axis or the rows in the y axis. A duplication of tables is indicated by two or more sheets. Axes can be build on basis of a set of dictionary elements that could be already defined in an hierarchy. The combination of the dictionary elements in each axis define a Cartesian product which represent the set of Data Points reflected in a table. Tables are normalized from a dimensional perspective because a dictionary element can only be associated to one axis.
Superclass: Public Element
Dimension Validation Perspective
From a validation perspective taxonomy can be split in different modules that refer to a specific excerpt of a taxonomy. An excerpt might be linked to the information in one or more business templates being summarised under an specific aspect. A Table Cubes represents sets of actual data requirements. Each Data Point that corresponds to the data requirements of a reporting framework must have its representation in one of the Table Cubes of a Module.
Module
A Module consists of one or more tables which are combined the serve specific aspects in the reporting process. Modules define sets of business information that should be reported together, i.e. to conduct validation rules that are defined across tables.
Superclass: Public Element
Table Cube
A table cube is a set of Data Points which is defined by a module of a taxonomy. A table cube combines Data Points that share the same dimensionality. The same dimensionality is given when the Data Points have the same number of dimensions and the dimensions of each Data Points are equivalent. In comparision to a Table a Table Cube does not contain any combination of dictionary elements on axes that are required. Non required data is often marked with gray cells inside Business Templates.
Data Point
A Data Point as a financial concept is characterized by defining its basic financial meaning and specifying information of breakdowns (hierarchies) in which it is described in different tables or paragraphs of documentation. Each Data Point refers to one Dimensioned Element which delivers the quantitative aspects about the nature (i.e. number, percentage) of the Data Point. The qualitative aspects of a Data Point are described by a set of dimensions where each dimension is refering to one member of a domain.
Contained elements: Dimension Set, Dimensioned Element
References:
| meta class | multiplicity | description |
|---|---|---|
| DimensionedElement | exactly one | References the element to be dimensioned by a set of dimensions with their according members. |
| Dimension | zero or one | References a set of dimensions, each dimension is linked to a domain and one member. |
Business Rule Perspective
Hierarchies are created to fulfill two main objectives. First the purpose is the definition of logical and/or arithmetical relations between Dictionary Elements. Secondly Dictionary Elements are structured in hierarchies to increase the comprehensibility of Data Points and their relations to each other. It is essential that at least Defined Members as well as Dimensioned Elements are represented in hierar-chies.
Enumerable Domains refer to hierarchies to show the relationships between their associated Defined Members. For analysis purposes it is also important to reflect the associations between Dimensions and Hierarchies.
The meta model refers just to the hierarchies but not to the definiton of validation rules in a wider context. Validations rules could be defined by formulas in XBRL or implemented in any other programming language.
Hierarchy
Members as well as Dimensioned Elements can be arranged in hierarchies to represent the relationships to one another. In mathematical terms a hierarchy is a rooted tree that provides the information if a member is at top level, below another member or at the same level. Financial information is often split up in different segmental breakdowns which represent dimensions in multidimensional terms. If the members of a dimension share the same level of detail, they could be represented as a flat list. But often the members relate to each other, i.e. in a parent-child relationship, and so they form natural hierarchies. The information about the location of a member in a hierarchy of a dimension improves its understanding. Furthermore, hierarchies can be used to define rules for calculations or aggregations. In the DPM a hierarchy forms are sets of members of an explicit domain arranged in a hierarchical disposition.
Superclass: Public Element
Hierarchy Relationship
A hierarchy relationship defines a logical relationship between a pair of Dictionary Elements. One of these Dictionary Elements define the parent and the second one the child element. Both Dictionary Elements are referenced by their codes. A Hierarchy Relationship can be of the type presentation or rule.
Rule Relationship
Business rules are part of regulatory frameworks. They should ensure the quality of data being sent by the supervised entity. Rule Rela-tionships have a sign attribute which identifies the arithmetical relationship between the two elements. The list of possible signs in a DPM is not determined. The two Dictionary Elements of a relationship build the operands that are combined by an operator that is rep-resented by a mathematical symbol, like + or -.
Presentation Relationship
Hierarchy relationships are defined for presentational purposes. The order provides information about the appearance of a child element in a tree structure of a hierarchy to be visualized in an axis of a table.
Presentation Perspective
Data required by supervisors is described in legal normative acts and mostly reflected in bi-dimensional forms usually referred to as business templates. In most of the cases a business templates is represented by only one table. Sometimes such a convenient match is not possible because there is a high degree of complexity in the template that does not allow grouping the data points in the same view as the predefined template. A split of a business template in different tables is needed from a presentation perspective. A set of tables reflects then the data requirements defined in one business template. The DPM reflects the link between the business templates and the tables that represent their content.
A table consists of a combination of one or more axes. To each axis a set of Dictionary Elements is assigned to. The x-axis defines the columns as horizontal arrangement whereas the y-axis represents a vertical progression of rows in a table. The z-axis can be interpreted as the identifier of a sheet in a series of two-dimensional tables with the same structure. An axis can be also linked to one or more hierarchies build upon Dictionary Elements.
It is possible to assign Header Labels to an axis. They are specific to a table and only used for presentation purposes. One cell in a table is a combination of one column, one row and optional sheets and hires the dimensional combinations of the dictionary elements linked with these axes. A cell can represent a Data Point in the model if it corresponds to data requirements. In the case of the cell is not asked by a supervisor a dimensional validation ensures that the incorrect Data Point is being identified.
Axis
Some explanation.
Row
Some explanation.
Column
Some explanation.
Sheet
Some explanation.
Cell
Some explanation.
Data Point Metamodel Constraints
General constraints
- 1.01
Each Public Element MUST have a code.
For each Public Element a technical code MUST be defined.
context PublicElement inv:
self.code->size() = 1
At least one label for a Public Element MUST be given which provides the human readable meaning of this element.
context PublicElement inv:
self.label->size() >= 1
Using a code on more than one Public Element is not allowed.
context PublicElement inv:
self.allInstances()->isUnique(p : PublicElement | p.code)
Creating more than one label refering to two different Public Elements is not allowed.
context PublicElement inv:
self.allInstances()->isUnique(p : PublicElement | p.label)
Each Dimensioned Element is to be determined by a data type and a period type.
context DimensionedElement inv:
self.dataType->size() = 1
and self.periodType->size() = 1
Defined Members need a reference to an Enumerable Domain so that they are able to be used for the definition of data points.
context DataPointModel inv:
self.DefinedMember->forAll(m | m.EnumerableDomain->notEmpty())
In some cases breakdowns represent certain business notion rather than disagregation (e.g. Solo, IFRS consolidation, CRD consolidation). In such case the hierarchy would be just a flat list of members.
Some explanation.
context EnumerableDomain inv:
self.DefinedMember->select(isDefault = true)->size() = 1
Some explanation.
Some explanation.
Some explanation.
The root of each hierarchy is an Enumerable Domain. The Defined Members should be attached underneath.
The same member must not be used twice in the same hierarchy.
