Locality Type (CDQ.POOL)

From CDQ
Address/locality/type
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. Locality Type
Description Informal and comprehensive human-readable definition of a concept. Type of a locality.
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 CDQ.POOL
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. LOCALITY_TYPE
Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model. Locality (CDQ.POOL)
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. EXACTLY_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. address.localities[0].type
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/> LEAF
Mapping

mapping source: type (HK.CR), mapping: HK.CR referenceAddressDto_localities_typeLOCALITY_TYPE
mapping source: type (HK.CR), mapping: HK.CR referenceAddressDto_localities_typeLOCALITY_TYPE
mapping source: technicalKey (IE.CR), mapping: IE.CR referenceAddressDto_localities_type_technicalKeyLOCALITY_TYPE
mapping source: technicalKey (IE.CR), mapping: IE.CR referenceAddressDto_localities_type_technicalKeyLOCALITY_TYPE
mapping source: adresas (LT.CR), mapping: LT.CR adresasLOCALITY_VALUE, LOCALITY_TYPE, THOROUGHFARE_VALUE, THOROUGHFARE_TYPE, POST_CODE_VALUE, POST_CODE_TYPE, ADMINISTRATIVE_AREA_VALUE, ADMINISTRATIVE_AREA_TYPE
mapping source: landkode (NO.RBE), poststed (NO.RBE), mapping: NO.RBE forretningsadresse_poststed, forretningsadresse_landkodePOST_CODE_VALUE, POST_CODE_TYPE, LOCALITY_VALUE, LOCALITY_TYPE
mapping source: name (PEPPOL), mapping: PEPPOL address_localities_1_type_nameLOCALITY_TYPE
mapping source: , mapping: SG.BR ↣ LOCALITY_TYPE
mapping source: RECORD (VIES), mapping: VIES recordTHOROUGHFARE_VALUE, THOROUGHFARE_TYPE, POST_CODE_VALUE, POST_CODE_TYPE, LOCALITY_VALUE, LOCALITY_TYPE


Values