code (DNB)
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. | code |
---|---|
Description Informal and comprehensive human-readable definition of a concept. | The code that identifies the business activity in which the entity is engaged.
For example, 1611 represents the highway and street construction industry in the U.S. SIC (Standard Industrial Classification) system. Note: These are generally external codes created by an external authoritative body, like the U.S. Office of Management and Budget (OMB); however, Dun & Bradstreet may have created extensions to more precisely define an activity, as in the case of the SIC 2+2 (the last 4 digits of an 8-digit SIC). |
Example A simple example supporting the understanding of a concept, business rule, etc. | 323111 |
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. | industryCodes_code
|
Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model. | Data source/DNB/data model/organization/industryCodes |
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.industryCodes[-1:].code
|
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 |