Difference between revisions of "Data source/DNB/data model/organization/primaryAddress/addressLocality"
Data source/DNB/data model/organization/primaryAddress/addressLocality
Jump to navigation
Jump to search
(Template parameters updated.) |
(Template parameters updated.) |
||
| Line 5: | Line 5: | ||
| parent concept = Data source/DNB/data model/organization/primaryAddress | | parent concept = Data source/DNB/data model/organization/primaryAddress | ||
| name = addressLocality | | name = addressLocality | ||
| − | | path = organization.primaryAddress.addressLocality | + | | path = cmpelkV2.organization.primaryAddress.addressLocality |
| description = The details of the city, town, township, village, borough, etc. in which this address is located. | | description = The details of the city, town, township, village, borough, etc. in which this address is located. | ||
| technical key = primaryAddress_addressLocality | | technical key = primaryAddress_addressLocality | ||
| data source = Data source/DNB | | data source = Data source/DNB | ||
}} | }} | ||
Latest revision as of 07:24, 6 October 2021
| 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. | addressLocality |
|---|---|
| Description Informal and comprehensive human-readable definition of a concept. | The details of the city, town, township, village, borough, etc. in which this address is located. |
| Part of Hierarchical relation between two concepts of the CDQ Data Model. | Data source DNB |
| 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. | primaryAddress_addressLocality
|
| Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model. | primaryAddress (DNB) |
| 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>. | OBJECT
|
| Path JSON Path to identify attributes in a data item. | cmpelkV2.organization.primaryAddress.addressLocality
|
| 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