<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>How to use table Linkbase information to facilitate XBRL report analysis</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Jean-Paul Daisomont</string-name>
          <email>jean-paul.daisomont@acsone.eu</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Denis Robinet</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Haute École Robert Schuman</institution>
          ,
          <addr-line>Wallonia</addr-line>
          ,
          <country country="BE">Belgium</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>acsone</institution>
          ,
          <addr-line>Brussels</addr-line>
          ,
          <country country="BE">Belgium</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This paper explores the technical challenges and difficulties to cover table Linkbase and dimensions management in case of open axes. These characteristics are mainly present in Solvency II taxonomy, and, to a lesser extent, in CRD IV taxonomies. This exploration started last year when we discovered fact description given by OIM specification. Of course, OIM target is to simplify XBRL reports formatting and exchange. Fact description in OIM highlights clearly the relationship between facts and dimensional information. From our side, this triggers a reflection over the exploitation of dimensional descriptions in the context of data dissemination. In other words, it concerns the way to enrich fact description with taxonomy information to help data analysis. One of the main expected qualities is to avoid specific development related to the specificity of the XBRL reports. This requires working on the abstract definition of XBRL taxonomies. In this paper, we will first describe which source of information will be handled, how it will be processed and designed into a database schema. This study is currently relevant for European taxonomies, using table Linkbase specifications, as specified by EIOPA and EBA. .</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>1.1</p>
      <p>Aspects of the facts
Aspects are immediately available within XBRL reports; simple parsing of XBRL
report is enough to retrieve this type of information. Labels can be retrieved from
taxonomy specifications.</p>
      <p>Here after, we illustrate for a fact from Solvency II report in OIM CSV format:
Here after, the same fact with its XBRL properties (on the left side) and its table
presentation (on the right side).</p>
      <p>Facts in reports are only defined by its aspects. For analysis, information over table
structure is also relevant. Three types of information over table structure are relevant:
• Ventilation of the dimensions over axes;
• Description of table structure in terms of axes, breakdowns and structural nodes;
• Labels related to concepts, dimensions, members and table structure
Ventilation of dimensions over axes. Here is the ventilation of the fact
dimensions over the axis of the fact from table S.05.02.01.01; members of the dimensions
are defined by the following table Linkbase.</p>
      <p>Dimensions
S2c_dim:BL
S2c_dim:DI
S2c_dim:EE
S2c_dim:IZ
S2c_dim:TB</p>
      <p>Members
S2c_LB:x79
S2c_DI:x5
S2c_GA:x24
S2c_RT:x1
S2c_LB:x107</p>
      <p>X-axis
S2c_dim:VG</p>
      <p>S2c_AM:x84
This is a simple case because axes of table S.05.02.01.01 are closed.</p>
      <p>Solvency II taxonomy use quite frequently open axes; the most sophisticated situation
is present in table S.22.06.01.04 where all the axes X, Y and Z are open. Here follows
an illustration of this case.</p>
      <p>The ventilation of the fact dimensions over the axis is the following:</p>
    </sec>
    <sec id="sec-2">
      <title>Dimensions</title>
    </sec>
    <sec id="sec-3">
      <title>Members</title>
    </sec>
    <sec id="sec-4">
      <title>X-axis</title>
    </sec>
    <sec id="sec-5">
      <title>Y-axis</title>
    </sec>
    <sec id="sec-6">
      <title>Z-axis</title>
      <p>S2c_dim:BL</p>
      <p>S2c_LB:x65
S2c_dim:EE</p>
      <p>S2c_GA:x74
S2c_dim:LG</p>
      <p>S2c_GA:DK
S2c_dim:OC</p>
      <p>S2c_CU:EUR
S2c_dim:RC</p>
      <p>S2c_CU:x4
S2c_dim:VG</p>
      <p>S2c_AM:x80
S2c_dim:VL</p>
      <p>S2c_VM:x5</p>
      <p>In this case, member definitions are coming from the table Linkbase and also from
the report fact. In that case, the table Linkbase specifies the allowed set of values.</p>
      <p>The third interesting case occurs when the member is defined by the entity in the
report. Table S.09.01.01.01 from Solvency II illustrates it; one dimension, XD, is
attached to the fact and to Y-axis.</p>
      <p>Dimensions</p>
      <p>Members X-axis</p>
      <p>Y-axis
S2c_dim:XD</p>
      <p>1
Fig. 4. : XBRL properties of a fact in the case of Y-axis open table with dimension member
defined by the entity.</p>
      <p>Table structure in terms of axes, breakdowns and structural nodes. In addition
to the axes description, information over breakdowns and structural nodes are also
useful to use the table structure. Breakdowns and structural nodes are defined in table
Linkbase specifications.</p>
      <p>Labels. Data without labels is not useful; labels over table structure can be
retrieved within table Linkbase specifications.
2</p>
      <sec id="sec-6-1">
        <title>How can it be processed?</title>
        <p>Previous chapter draws the list of wishable information over table structure that can
be useful for data analysis. This chapter will describe the organisation of the data
(database schema) that we suggest storing reports.</p>
        <p>Two sets of data/processing have to be distinct:
• Data/processing related to the taxonomy
• Data/processing related to the report
The processing that we have implemented is based on the technical environment of
Arelle project; it means that its processing works on taxonomy specifications only and
does not include taxonomy dependent processing.
2.1</p>
        <p>Data model for the taxonomy
The information that we retrieve from taxonomy specifications are: taxonomy
version, table, breakdown (orientation means axis), structural node, member, domain,
dimension and relationship between structural node and member.
Information specific to the report are: report, fact, context, user dimension and
relationship between user dimension and context. A lot of links exist between report and
taxonomy data; the main are the link between:
• fact and structural node.
• user dimension and taxonomy dimension.
• context and taxonomy dimension and taxonomy member.
• fact and taxonomy member.</p>
        <p>Here after the data model combining report and taxonomy tables. We use colours
to distinct tables related to taxonomy from tables linked to reports.</p>
      </sec>
      <sec id="sec-6-2">
        <title>Conclusion</title>
        <p>In Europe, the learning processes over new regulations are based on table description
of reports such as QRT. Unfortunately, the excellent OIM specification does include
not information over that point of view.</p>
        <p>Our approach is to enrich the OIM with X-axis, Y-axis and Z-axis information; that
table presentation information will mainly be useful to load XBRL reports into
database and data warehouse.</p>
        <p>This paper tries to show which table information can be extracted from taxonomies
and exploited for data analysis. It assumes that table Linkbase specifications are
available. The approach presents some limitations:</p>
        <p>• Multilingual information is not yet managed; it can be useful for the French
RAN taxonomy, the Dutch Specific templates (Verzekeraars Nationale
StatenTaxonomy), the Single Resolution Board.</p>
        <p>• It does not yet support presentation Linkbase taxonomies.
• Member hierarchies are not explored.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list />
  </back>
</article>