Difference between revisions of "Address/post code"

From CDQ
Address/post code
Jump to navigation Jump to search
(Spreadsheet import)
Line 1: Line 1:
{{data model concept
+
{{Data model concept
| name = Post Code
+
|name=Post Code
| description = A country specific code for a certain [[address]] component or an combination of [[address]] components, e.g. [[address/locality]].
+
|description=A country specific code for a certain [[address]] component or an combination of [[address]] components, e.g. [[address/locality]].
| example = 9000 is the major post code of the [[address/locality]] St. Gallen.
+
|example=9000 is the major post code of the [[address/locality]] St. Gallen.
| data model = CDQ Data Model
+
|data model=CDQ Data Model
| technical key = POST_CODE
+
|technical key=POST_CODE
| parent concept = address
+
|parent concept=Address
| cardinality = ZERO_OR_MORE
+
|cardinality=ZERO_OR_MORE
| path = postCodes[?(@.type.technicalKey=='<KEY>')]
+
|path=businessPartner.addresses[?(@.type.technicalKey=='<addressType>')].postCodes[?(@.type.technicalKey=='<postCodeType>')]
 
}}
 
}}

Revision as of 14:47, 22 October 2020

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. Post Code
Description Informal and comprehensive human-readable definition of a concept. A country specific code for a certain address component or an combination of address components, e.g. address/locality.
Example A simple example supporting the understanding of a concept, business rule, etc. 9000 is the major post code of the address/locality St. Gallen.
Part of Hierarchical relation between two concepts of the CDQ Data Model. n/a
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. POST_CODE
Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model. Address (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. ZERO_OR_MORE
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. businessPartner.addresses[?(@.type.technicalKey=='<addressType>')].postCodes[?(@.type.technicalKey=='<postCodeType>')]
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/> missing
Mapping

Sub concepts