Views: 68
Definition
Consider what happens if you define it in the dimension hypercube without using the definition link used in 1 XBRL taxonomy.
Note: The files can be found at GitHub.
Taxonomy
Remove the definition link from the definition of 1 taxonomy and consider the dimension definition.
The Dimensional relationship set (DRS)
gl-cor-2020-12-31.xsd
<annotation> <appinfo> <link:linkbaseRef xlink:href="gl-cor-2020-12-31-presentation.xml" xlink:title="Presentation Links, all" xlink:type="simple" xlink:role="http://www.xbrl.org/2003/role/presentationLinkbaseRef" xlink:arcrole="http://www.w3.org/1999/xlink/properties/linkbase"/> <link:roleType roleURI="http://xbrl.org/role/gl-cor_structure" id="gl-cor_structure"> <link:definition>XBRL GL Structure</link:definition> <link:usedOn>link:presentationLink</link:usedOn> <link:usedOn>link:definitionLink</link:usedOn> </link:roleType> </appinfo> </annotation> <!-- Hypercube --> <element name="Hypercube" id="Hypercube" type="xbrli:stringItemType" substitutionGroup="xbrldt:hypercubeItem" abstract="true" xbrli:periodType="instant"/> <!-- Dimension --> <element name="EntryNumber" id="gl-cor_EntryNumber"> <simpleType> <restriction base="string"/> </simpleType> </element> <element name="dEntryNumber" id="gl-cor_dEntryNumber" type="xbrli:stringItemType" substitutionGroup="xbrldt:dimensionItem" abstract="true" xbrli:periodType="instant" xbrldt:typedDomainRef="#gl-cor_EntryNumber"/> <element name="LineNumber" id="gl-cor_LineNumber"> <simpleType> <restriction base="string"/> </simpleType> </element> <element name="dLineNumber" id="gl-cor_dLineNumber" type="xbrli:stringItemType" substitutionGroup="xbrldt:dimensionItem" abstract="true" xbrli:periodType="instant" xbrldt:typedDomainRef="#gl-cor_LineNumber"/> <element name="AccountMainID" id="gl-cor_AccountMainID"> <simpleType> <restriction base="string"/> </simpleType> </element> <element name="dAccountMainID" id="gl-cor_dAccountMainID" type="xbrli:stringItemType" substitutionGroup="xbrldt:dimensionItem" abstract="true" xbrli:periodType="instant" xbrldt:typedDomainRef="#gl-cor_AccountMainID"/>
gl-cor-2020-12-31-definition.xml
<link:roleRef xlink:type="simple" xlink:href="gl-cor-2020-12-31.xsd#gl-cor_structure" roleURI="http://xbrl.org/role/gl-cor_structure"/> <link:arcroleRef xlink:type="simple" xlink:href="http://xbrl.org/2005/xbrldt-2005.xsd#hypercube-dimension" arcroleURI="http://xbrl.org/int/dim/arcrole/hypercube-dimension" /> <link:definitionLink xlink:type="extended" xlink:role="http://xbrl.org/role/gl-cor_structure"> <!-- Hypercube --> <link:loc xlink:type="locator" xlink:href="gl-cor-2020-12-31.xsd#Hypercube" xlink:label="Hypercube" xlink:title="Hypercube"/> <link:loc xlink:type="locator" xlink:href="gl-cor-2020-12-31.xsd#gl-cor_dEntryNumber" xlink:label="dim_EntryHeader" xlink:title="Axis entryHeader"/> <link:loc xlink:type="locator" xlink:href="gl-cor-2020-12-31.xsd#gl-cor_dLineNumber" xlink:label="dim_EntryDetail" xlink:title="Axis entryDetail"/> <link:definitionArc xlink:type="arc" xlink:from="Hypercube" xlink:to="dim_EntryHeader" xlink:arcrole="http://xbrl.org/int/dim/arcrole/hypercube-dimension" xlink:title="definition Hypercube to typed Dimension entryHeader" use="optional" order="1.0"/> <link:definitionArc xlink:type="arc" xlink:from="Hypercube" xlink:to="dim_EntryDetail" xlink:arcrole="http://xbrl.org/int/dim/arcrole/hypercube-dimension" xlink:title="definition Hypercube to Typed Dimension entryDetail" use="optional" order="1.0"/> </link:definitionLink>
DTS
The palette schema includes gl-cor module.
Zip file XBRL-GL-WD-2020-12-31_07-23.zip
Instance document
All items are arranged under the xbrli:xbrl element, but how to represent the entryDetail arranged under the structure of the entryHeader tuple remains to be considered.
The definition of contextRef=”ACCOUNT1451″ in the entryDetail is defined as <gl-cor:specified.account contextRef=”ACCOUNT1451″/>
under entryDetail, and the number of dimension member elements is number of entryHeader elements x number of entryDetail elements. This number becomes huge.
Formula linkbase
Since the tuple structure cannot be used, it is judged from the value of the first debitCreditCode element that appears next in line, so the test condition of General filter is whether the value of following-sibling::gl-cor:debitCreditCode[1] is’D’. Debit/Credit is judged by this value is either ‘D’ or ‘C’.
Execution result
Proof-of-concept implementation trial of international standard data formats
1 XBRL 2.1 taxonomy
UN/CEFACT Core Component Technical Specification(CCTS)/a>
Objective: Improve transparency and extensibility by expressing CCTS structure in XBRL 2.1
Tuple child of tuple does not include child tuple
DTS
Tuple definition
Definition linkbase
Presentation linkbase
2 XBRL 2.1 instance document
Implement definition linkbase (requires-element) relationship using typed dimension
xbrldt:dimensionItem definition in taxonomy document
xbrli:context definition in instance document
Instance document
Execution result of formula linkbase
3 XBRL 2.1 formula
Definition
Execution result of formula linkbase
4 XBRL 2.1 table linkbase [in trial]
Definition
Execution result/a>
5 XBRL 2.1 without child tuple1 [in trial]
Definition
Instance document
Execution result