Difference between revisions of "Data source/LV.CR/data model/record/address"
Data source/LV.CR/data model/record/address
Jump to navigation
Jump to search
(Spreadsheet import) |
(Template parameters updated.) |
||
| Line 1: | Line 1: | ||
{{Data model concept | {{Data model concept | ||
| − | |name=address | + | | name = address |
| − | |description=Legal address of the company, comprising city and street | + | | description = Legal address of the company, comprising city and street |
| − | |example=Dundagas nov., Kolkas pag., Kolka, "Krastnieki" | + | | example = Dundagas nov., Kolkas pag., Kolka, "Krastnieki" |
| − | |data source=Data source/LV.CR | + | | data source = Data source/LV.CR |
| − | |technical key=address | + | | technical key = address |
| − | |parent concept=Data source/LV.CR/data model/record | + | | parent concept = Data source/LV.CR/data model/record |
| − | |cardinality=ZERO_OR_ONE | + | | cardinality = ZERO_OR_ONE |
| − | |path=address | + | | path = address |
| − | |concept role=LEAF | + | | concept role = LEAF |
}} | }} | ||
Latest revision as of 08:39, 23 April 2021
| 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 |
|---|---|
| Description Informal and comprehensive human-readable definition of a concept. | Legal address of the company, comprising city and street |
| Example A simple example supporting the understanding of a concept, business rule, etc. | Dundagas nov., Kolkas pag., Kolka, "Krastnieki" |
| Part of Hierarchical relation between two concepts of the CDQ Data Model. | Data source LV.CR |
| 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
|
| Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model. | RECORD (LV.CR) |
| 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
|
| 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 Number (CDQ.POOL), Thoroughfare Value (CDQ.POOL), Premise Value (CDQ.POOL), Administrative Area Value (CDQ.POOL), mapping: LV.CR address ↣ THOROUGHFARE_VALUE, THOROUGHFARE_NUMBER, PREMISE_VALUE, ADMINISTRATIVE_AREA_VALUE
|