Difference between revisions of "Data source/DK.CR/data model/beliggenhedsadresse"
Data source/DK.CR/data model/beliggenhedsadresse
Jump to navigation
Jump to search
(Spreadsheet import) |
(Template parameters updated.) |
||
Line 1: | Line 1: | ||
{{Data model concept | {{Data model concept | ||
− | |name=beliggenhedsadresse | + | | name = beliggenhedsadresse |
− | |description=Location address - a valid address in the authoritative address register. This data element exhibits which addresses the company has been registered at. | + | | description = Location address - a valid address in the authoritative address register. This data element exhibits which addresses the company has been registered at. |
− | |data source=Data source/DK.CR | + | | data source = Data source/DK.CR |
− | |technical key=beliggenhedsadresse | + | | technical key = beliggenhedsadresse |
− | |cardinality=EXACTLY_ONE | + | | cardinality = EXACTLY_ONE |
− | |data type=ARRAY | + | | data type = ARRAY |
− | |path=beliggenhedsadresse[-1:] | + | | path = beliggenhedsadresse[-1:] |
− | |concept role=NODE | + | | concept role = NODE |
}} | }} |
Revision as of 05:51, 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. | beliggenhedsadresse |
---|---|
Description Informal and comprehensive human-readable definition of a concept. | Location address - a valid address in the authoritative address register. This data element exhibits which addresses the company has been registered at. |
Part of Hierarchical relation between two concepts of the CDQ Data Model. | Data source DK.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. | beliggenhedsadresse
|
Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model. | No parent concept, this is the root concept. |
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. | EXACTLY_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>. | ARRAY
|
Path JSON Path to identify attributes in a data item. | beliggenhedsadresse[-1:]
|
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 | mapping target: Address Type (CDQ.POOL), mapping: DK.CR beliggenhedsadresse ↣ ADDRESS_TYPE
|
Sub concepts