Difference between revisions of "Data source/DNB/data model/organization/telephone/telephoneNumber"
Jump to navigation
Jump to search
(Template parameters updated.) |
(Template parameters updated.) |
||
| Line 5: | Line 5: | ||
| parent concept = Data source/DNB/data model/organization/telephone | | parent concept = Data source/DNB/data model/organization/telephone | ||
| name = telephoneNumber | | name = telephoneNumber | ||
| − | | path = organization.telephone[-1:].telephoneNumber | + | | path = cmpelkV2.organization.telephone[-1:].telephoneNumber |
| description = A sequence of digits used for voice communication with the entity. | | description = A sequence of digits used for voice communication with the entity. | ||
This sequence of digits includes the area code or city code and domestic dialing code. | This sequence of digits includes the area code or city code and domestic dialing code. | ||
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. | telephoneNumber |
|---|---|
| Description Informal and comprehensive human-readable definition of a concept. | A sequence of digits used for voice communication with the entity.
This sequence of digits includes the area code or city code and domestic dialing code. |
| Example A simple example supporting the understanding of a concept, business rule, etc. | 6505550000 |
| 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. | telephone_telephoneNumber
|
| Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model. | Data source/DNB/data model/organization/telephone |
| 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>. | STRING
|
| Path JSON Path to identify attributes in a data item. | cmpelkV2.organization.telephone[-1:].telephoneNumber
|
| 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 target: Phone Number Value (CDQ.POOL), mapping: DNB telephone_telephoneNumber ↣ PHONE_NUMBER_VALUE
|