How to deactivate assertions


..-ignore-val.xml   mechanism to deactivate assertions

Date: Brussels, March 2017
Authors: Derek De Brandt,


Background and rationale

Eurofiling Architecture taxonomies are used for data collection with the financial industry by European Authorities (EBA, ECB, EIOPA) and by corresponding National Competent Authorities.

These taxonomies share the same architecture type and can be exploited with open source tools, such as DPM Architect (© Banco de España).

Common elements are referenced in the domain, such as the model and interval arithmetic schemes.

Taxonomies contain in most cases assertion sets with severity assertions, individually triggered depending on the existence of filing indicators in the given instance document.

However, in practise, assertions are frequently “deactivated” via work-arounds.

An embedded taxonomy mechanism to (conditionally) blacklist individual assertions is not available; this paper proposes a mechanism to include the feature in a taxonomy.

This mechanism would enable the simultaneous publication of:

  • List of deactivated (and/or reactivated assertions) in Excel or PDF, as is
  • The same information in an XML file, immediately consumable by XBRL tools

Proposed mechanism.

Precondition: update to the latest version of

The example below is based on a Taxonomy “eac_ind.xsd” attached as zip.

STEP1: include empty blacklist in the Taxonomy

A dummy linkbase (eac-ind-ignore-val.xml) is made (the “Blacklist”):

<?xml version="1.0" encoding="utf-8"?> <!-- dummy linkbase -->
<link:linkbase xmlns:xsi="" 
<gen:link xlink:type="extended" 


The linkbase is linked to the entrypoint:


The taxonomy is published with the dummy Blacklist, which is a single XML file per taxonomy entry point.

STEP 2: deactivate one or more assertions

The Blacklist can be changed by the European Authority to generally deactivate a single assertion by including an extended link in the linkbase:

<gen:link xlink:type="extended" xlink:role="">
<variable:precondition xlink:type="resource" xlink:label="ignore_1" test="false()" />
<link:loc xlink:type="locator" xlink:href="../val/vr-srf_v0003.xml#srb_srf_v0003" 
xlink:label="loc_srb_srf_v0003" />
<gen:arc xlink:type="arc" xlink:arcrole="" xlink:from="loc_srb_srf_v0003" xlink:to="ignore_1" />

STEP 3: deactivate one or more assertions for a single reporting entity

The Blacklist can be changed by any actor to specifically deactivate a single assertion for one reporting entity by including an extended link in the linkbase:

<gen:link xlink:type="extended" xlink:role="">
<variable:precondition xlink:type="resource" 
xlink:label="ignore_2_ALPHANUMERICLENGTH20" test="$RepEntity != 'ALPHANUMERICLENGTH20'" />
<link:loc xlink:type="locator" 
xlink:label="loc_srb_srf_v0015" />
<gen:arc xlink:type="arc" 
xlink:from="loc_srb_srf_v0015" xlink:to="ignore_2_ALPHANUMERICLENGTH20" />


Live examples

EIOPA blacklists for the 2.3.0 taxonomy :