Difference between revisions of "Data source/DE.RC/data model/record/businessPartner/addresses/thoroughfares/value"

From CDQ
Data source/DE.RC/data model/record/businessPartner/addresses/thoroughfares/value
Jump to navigation Jump to search
(Template parameters updated.)
 
(Template parameters updated.)
 
Line 6: Line 6:
 
  | name = thoroughfare
 
  | name = thoroughfare
 
  | path = businessPartner.addresses[0].thoroughfares[0].value
 
  | path = businessPartner.addresses[0].thoroughfares[0].value
  | description = Street name and number
+
  | description = Street name
 
  | technical key = thoroughfare
 
  | technical key = thoroughfare
  | example = Wasserklammstraße 10
+
  | example = Wasserklammstraße
 
  | data source = Data source/DE.RC
 
  | data source = Data source/DE.RC
 
}}
 
}}

Latest revision as of 13:00, 9 January 2025

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. thoroughfare
Description Informal and comprehensive human-readable definition of a concept. Street name
Example A simple example supporting the understanding of a concept, business rule, etc. Wasserklammstraße
Part of Hierarchical relation between two concepts of the CDQ Data Model. Data source DE.RC
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. thoroughfare
Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model. Data source/DE.RC/data model/record/addresses
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
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. businessPartner.addresses[0].thoroughfares[0].value
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: Thoroughfare Value (CDQ.POOL), mapping: DE.RC thoroughfareTHOROUGHFARE_VALUE