With EBA, the filing indicator codes are included in module definition file like so:
mod\ae.json
"tables": {
"tA_00-01": {
"eba:documentation": {
"FilingIndicator": "A_00.01",
"TableKeyID": null,
"tableVID": 6355,
"templateID": 325
},
"optional": true,
"template": "A_00-01",
"url": "a_00.01.csv"
},
If that is missing, the result can be guessed somewhat reliably.
EIOPA doesn't (at least yet) provide that information in json files.
One way to get it would be to parse from xml taxonomy files:
\tab\e.01.01.16.01\e.01.01.16.01-lab-codes.xml
<label:label xlink:label="label_s2md_tE.01.01.16.01_1" xlink:type="resource" xlink:role="http://www.eurofiling.info/xbrl/role/filing-indicator-code" xml:lang="en">E.01.01</label:label>
But rather than add logic to find the file and parse the xsd, these cases can also be reliably guessed. This however requires additional logic so the length (number of parts) and separators are correct for each case (ESA)
so for
EBA: tA_00-01 -> A_00.01
EIOPA: E.01.01.16.01 -> E.01.01
With EBA, the filing indicator codes are included in module definition file like so:
mod\ae.json
If that is missing, the result can be guessed somewhat reliably.
EIOPA doesn't (at least yet) provide that information in json files.
One way to get it would be to parse from xml taxonomy files:
\tab\e.01.01.16.01\e.01.01.16.01-lab-codes.xml
<label:label xlink:label="label_s2md_tE.01.01.16.01_1" xlink:type="resource" xlink:role="http://www.eurofiling.info/xbrl/role/filing-indicator-code" xml:lang="en">E.01.01</label:label>But rather than add logic to find the file and parse the xsd, these cases can also be reliably guessed. This however requires additional logic so the length (number of parts) and separators are correct for each case (ESA)
so for
EBA: tA_00-01 -> A_00.01
EIOPA: E.01.01.16.01 -> E.01.01