Difference between revisions of "Data source/SK.FS/data model/entity/datvymazu"
Data source/SK.FS/data model/entity/datvymazu
Jump to navigation
Jump to search
(Template parameters updated.) |
(Template parameters updated.) |
||
| Line 2: | Line 2: | ||
| concept role = LEAF | | concept role = LEAF | ||
| cardinality = ZERO_OR_ONE | | cardinality = ZERO_OR_ONE | ||
| − | | data type = | + | | data type = STRING |
| parent concept = Data source/SK.FS/data model/entity | | parent concept = Data source/SK.FS/data model/entity | ||
| name = datvymazu | | name = datvymazu | ||
| path = datvymazu | | path = datvymazu | ||
| − | | description = Date of deletion | + | | description = Date of deletion from VAT payers registry |
| technical key = datvymazu | | technical key = datvymazu | ||
| example = 24.07.2016 | | example = 24.07.2016 | ||
| data source = Data source/SK.FS | | data source = Data source/SK.FS | ||
}} | }} | ||
Latest revision as of 10:32, 5 June 2024
| 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. | datvymazu |
|---|---|
| Description Informal and comprehensive human-readable definition of a concept. | Date of deletion from VAT payers registry |
| Example A simple example supporting the understanding of a concept, business rule, etc. | 24.07.2016 |
| Part of Hierarchical relation between two concepts of the CDQ Data Model. | Data source SK.FS |
| 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. | datvymazu
|
| Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model. | Data source/SK.FS/data model/entity |
| 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>. | STRING
|
| Path JSON Path to identify attributes in a data item. | datvymazu
|
| 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 |