Thoroughfare (CDQ.POOL)
Address/thoroughfare
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. | Thoroughfare |
---|---|
Description Informal and comprehensive human-readable definition of a concept. | Details of the access route along which buildings, lots, or land are located, such as street, road, channel, crescent, avenue, etc. This also includes canals or banks on which houses or boat houses are located where people live. |
Example A simple example supporting the understanding of a concept, business rule, etc. | 17 Wall Street, New York City, New York 10005, USA. Wall Street is a thoroughfare in New York City with the house number 17. A thoroughfare can have a hierarchy of sub thoroughfares. However, sub thoroughfares are rarely used. |
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. | THOROUGHFARE
|
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 |
Path JSON Path to identify attributes in a data item. | address.thoroughfares[0]
|
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/> | NODE
|
Mapping |
Sub concepts