From CDQ
Data source/LEI/data model/RelationshipRecord/2/Relationship
Jump to navigation
Jump to search
| Name Name of a concept, e.g. a data model concept. In contrast to terms, the name does not depend on a given context, e.g. a country-specific language.
|
Relationship
|
| Description Informal and comprehensive human-readable definition of a concept.
|
n/a
|
| Example A simple example supporting the understanding of a concept, business rule, etc.
|
no example available
|
| Part of Hierarchical relation between two concepts of the CDQ Data Model.
|
Data source LEI
|
| Technical key Defines a unique key by which e.g. data model concepts can be referenced in a technical integration context. These keys are unique in the CDL context.
|
Relationship2
|
| Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model.
|
Data source/LEI/data model/RelationshipRecord
|
| Cardinality Cardinality of data model concepts.<br/><code>ZERO_OR_ONE</code>: Optional, but max. 1 instance related to its parent.<br/><code>EXACTLY_ONE</code>: Exactly 1 instance related to its parent.<br/><code>ZERO_OR_MORE</code>: Optional, multiple instances related to its parent may exist.<br/><code>ONE_OR_MORE</code>: Mandatory, multiple instances related to its parent may exist.
|
ZERO_OR_ONE
|
| Data type Data type of a data model concept, i.e., <code>ARRAY</code>, <code>BOOLEAN</code>, <code>DATE</code>, <code>ENUM</code>, <code>INTEGER</code>, <code>OBJECT</code>, or <code>STRING</code>.
|
n/a
|
| Concept type Complex data type of a data model concept, defined by another data model concept. Allows re-use of data type concepts, e.g. for several address types in a data model.
|
SELF
|
| Path JSON Path to identify attributes in a data item.
|
relations[2].relationship
|
| Concept role The role of a Category:Data model concept in the tree structure of a data model.<br/><code>ROOT</code>: Root concept in a data model, i.e., no parent concepts.<br/><code>NODE</code>: Structure concepts in a data model, i.e., parent and child concepts.<br/><code>LEAF</code>: Leaf concept in a data model, i.e., no child concepts, provides the effective data values.<br/>
|
NODE
|
| Mapping
|
|
Sub concepts
| Concept | Description |
|---|
| EndNode (LEI) | An LEI or provisional (ISO 27442-compatible) technical identifier for a legal entity in the relationship, together with a code indicating the type of identifier. |
| RelationshipPeriods (LEI) | A collection of paired beginning and end dates, defining a time period of a type indicated by an enumerated code: the relationship itself, periods (e.g. accounting) covered by documents demonstrating the relationship, or the filing date(s) of those documents. |
| RelationshipStatus (LEI) | The status of the legal entities\' relationship itself (e.g. currently active, historical only). |
| RelationshipType (LEI) | A unique code designating the specific category of a directional relationship between two legal entities. |
| StartNode (LEI) | An LEI or provisional (ISO 27442-compatible) technical identifier for a legal entity in the relationship, together with a code indicating the type of identifier. |
Values
| Value | Description | Technical key |
|---|
| isDirectlyConsolidatedBy2 (LEI) | "Child" entity is directly consolidated by "parent" entity. | IS_DIRECTLY_CONSOLIDATED_BY |
| isInternationalBranchOf2 (LEI) | "Child" entity is an international branch of the legal entity designated by "parent" entity (in jurisdiction country of "child" entity). The "parent" entity is the Head Office and must have an LEI. | IS_INTERNATIONAL_BRANCH_OF |
| isUltimatelyConsolidatedBy2 (LEI) | "Child" entity is ultimately consolidated by "parent" entity. The "child" entity has its accounts fully consolidated by the "parent" entity in the sense given by the accounting standard(s) specified in RelationshipQualifier; the "parent" entity is the most distant fully consolidating parent from the "child" entity in any applicable hierarchical ownership structure. | IS_ULTIMATELY_CONSOLIDATED_BY |