Configuring NST Extension Taxonomy

This appendix provides important information about how to configure NST extension taxonomy. In High Volume XBLR configuration directory, you must manually edit the configuration file dpm_taxonomy_info.xml to support NST publishing.

The NST mapping file is responsible for mapping data from an Oracle Hyperion Financial Management Application into XBRL using the NST extension taxonomy package and NST DPM dictionary.

The authoring process is designed to handle millions of rows of transactional data for the National Specific Templates (NSTs) publishing. The NST extension taxonomy package defines the taxonomy elements and validates the data collected by National Supervisory Authority (NSA). The dpm_taxonomy_info.xml configuration file that enables High Volume XBRL to publish data.

For example, let’s consider Central Bank of Ireland taxonomy metadata support to configure the NST extension taxonomy. For NST Publishing, you need to author and deploy the NST configuration before registering a mapping file.

The CBI NST XBRL taxonomy utilizes the same XBRL specifications and technical constructs as the EIOPA Solvency II XBRL taxonomy. The CBI NST XBRL taxonomy contains the latest release of the Taxonomy Packages specification.

If High Volume XBLR finds dpm_taxonomy_info.xml file, then the configuration information in the file is used instead of the EIOPA SII taxonomies up to version 2.0.1.

The tnsStartsWith attribute needs to be modified for assigning NST extension taxonomy configuration to entry points used for XBRL publishing. The dpm_taxonomy_info.xml file defines the value to each entry point XSD and targetNamespace attribute values. For the CBI set of entry points, a common string is the following: http://www.centralbank.ie/xbrl/md/fws/nst/nst/2015-10-3.

HVX automatically assigns the NST extension taxonomy configuration to all the NST Extension Taxonomies that match the tnStartsWith attribute value. This is the best way to author the NST mappings.

The primaryItemNamespace is determined by opening up met.xsd for the NST extension taxonomy and reviewing the targetNamepace attribute value. This schema contains all metrics that can be mapped to values in the instance document. The metric target namespace is listed in the formal documents such as DPM Dictionary, Annotation Templates and more.

  To author and deploy the NST configuration, perform these steps:

  1. Place the XML configuration file dpm_taxonomy_info.xml in the location: MW_HOME\user_projects\epmsystem1\DisclosureManagement\discman1\config. This file is located in the server, where Disclosure Manager is running.

  2. Copy the existing taxonomy metadata support section, and edit the following entries in the dpm_taxonomy_info.xml file.

    1. In dpm_taxonomy_info.xml file, verify and update the tnsStartsWith entry. The date entry should point to the new taxonomy. For example: The path varies for the CBI Taxonomy Package, you need to verify the medium dimensionality (md) met path in the taxonomy extension.

      From : http://eiopa.europa.eu/xbrl/s2md/fws/solvency/solvency2/2015-10-21

      To :http://www.centralbanl.ie/xbrl/md/fws/nst/nst/2015-10-31

    2. In dpm_taxonomy_info.xml file, verify the owner entry in the taxonomy extension, and update the owner entry from s2md to iemd.

      Note:

      The path and owner details can be found at the top of a sample XBRL file.

    3. In dpm_taxonomy_info.xml file, verify the primaryItemNamespace entry in the taxonomy extension, and update the primaryItemNamespace entry from http://eiopa.europa.eu/xbrl/s2md/dict/met to http://www.centralbanl.ie/xbrl/md/dict/met

    4. In dpm_taxonomy_info.xml file, you need to add a new metric Namespace entry for the new owner iemd_met entry. A namespace mapping for CBI extension taxonomy such as <Namespace prefix="iemd_met" taxonomyPrefix="iemd_met" value="http://www.centralbanl.ie/xbrl/md/dict/met" />

    5. In dpm_taxonomy_info.xml file, you need to verify for new dimension, owner, and domain entries in the taxonomy extension.

    6. In dpm_taxonomy_info.xml file, you need to verify and update the dimName and dimNamespace entries from the EIOPA path to the taxonomy extension path. For example:

      From: dimName="s2c_dim" dimNamespace="http://eiopa.europa.eu/xbrl/s2c/dict/exp"

      To: dimName="iec_dim" dimNamespace="http://www.centralbanl.ie/xbrl/c/dict/dim"

    7. In dpm_taxonomy_info.xml file, if there are new dimension entries, then verify and update the Primary dimensional namespace entries and create a new primary dimensional namespace mapping for CBI extension taxonomy.

      For example: <namespace prefix="iec_dim" taxonomyprefix="iec_dim" value="http://www.centralbanl.ie/xbrl/c/dict/dim" />

    8. In dpm_taxonomy_info.xml file, under the Dimension to Domain mapping section, you need to add new dimension and related domain entries from the CBI extension taxonomy.

      For example: <DimensionDomain from="iec_MA" to="iec_MC" />

    9. In dpm_taxonomy_info.xml file, you need to add new domain entries to the Domain mapping section from the CBI extension taxonomy.

      For example: <namespace prefix="iec_MC" taxonomyprefix="iec_s2c_MC" value="http://www.centralbanl.ie/xbrl/c/dict/dom/s2c_MC" />

    10. Before importing a file to HVX, the taxonomyPackage.xml file must be corrected and then added back to the taxonomy package zip file.

      You need to correct the entry point in the taxonomyPackage.xml file, before loading the taxonomy from HVX Taxonomy Manager.

      For example, you need to correct the path information:

      From: <tp:entryPointDocument href="http://www.centralbank.ie/ie/xbrl/iemd/fws/nst/nst/2015-10-31/mod/arsgb.xsd"/>

      To: <tp:entryPointDocument href="http://www.centralbank.ie/ie/xbrl/md/fws/nst/nst/2015-10-31/mod/arsgb.xsd"/>