Difference between revisions of "Address/geographic coordinates"
Address/geographic coordinates
Jump to navigation
Jump to search
(Spreadsheet import) |
(Spreadsheet import) |
||
| Line 2: | Line 2: | ||
|name=Geographic Coordinates | |name=Geographic Coordinates | ||
|description=Geographic coordinates identify uniquely a location on the Earth. In the Corporate Data League context, geographic coordinates identify [[address]]es. | |description=Geographic coordinates identify uniquely a location on the Earth. In the Corporate Data League context, geographic coordinates identify [[address]]es. | ||
| − | |data | + | |data source=Data source/CDQ |
|technical key=GEO_COORDINATES | |technical key=GEO_COORDINATES | ||
|parent concept=Address | |parent concept=Address | ||
|cardinality=ZERO_OR_ONE | |cardinality=ZERO_OR_ONE | ||
|path=address.geographicCoordinates | |path=address.geographicCoordinates | ||
| + | |concept role=NODE | ||
}} | }} | ||
Latest revision as of 07:48, 30 November 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. | Geographic Coordinates |
|---|---|
| Description Informal and comprehensive human-readable definition of a concept. | Geographic coordinates identify uniquely a location on the Earth. In the Corporate Data League context, geographic coordinates identify addresses. |
| 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. | GEO_COORDINATES
|
| 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_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>. | n/a |
| Path JSON Path to identify attributes in a data item. | address.geographicCoordinates
|
| 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