Difference between revisions of "Address/context"

From CDQ
Address/context
Jump to navigation Jump to search
(Changed redirect target from Address Contexts to Address/contexts)
Tag: Redirect target changed
(Removed redirect to Address/contexts)
Tag: Removed redirect
 
Line 1: Line 1:
 
+
{{Data model concept
#redirect [[Address/contexts]]
+
|name=Address Context
 +
|description=The address context provides us with some additional information about the usage or specific recipient information of the addresses. It may hold multiple information organized as "tags".
 +
|data source=Data source/CDQ
 +
|technical key=ADDRESS_CONTEXT
 +
|parent concept=Address
 +
|cardinality=ZERO_OR_MORE
 +
|path=address.contexts
 +
|concept role=LEAF
 +
}}

Latest revision as of 10:03, 5 July 2022

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. Address Context
Description Informal and comprehensive human-readable definition of a concept. The address context provides us with some additional information about the usage or specific recipient information of the addresses. It may hold multiple information organized as "tags".
Example A simple example supporting the understanding of a concept, business rule, etc. no example available
Part of Hierarchical relation between two concepts of the CDQ Data Model. Data source CDQ.POOL
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. ADDRESS_CONTEXT
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. address.contexts
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