Difference between revisions of "Data source/US-CO.BER/data model/entity/agentmiddlename"
Data source/US-CO.BER/data model/entity/agentmiddlename
Jump to navigation
Jump to search
Jakubpluta (talk | contribs) (Spreadsheet import) |
(Template parameters updated.) |
||
| Line 1: | Line 1: | ||
{{Data model concept | {{Data model concept | ||
| − | |name=agentmiddlename | + | | name = agentmiddlename |
| − | |description=Middle name of agent. A registered agent for a business needs to have a Colorado address and serves as the contact for the entity. In the event of litigation, the service of process goes to the registered agent. | + | | description = Middle name of agent. A registered agent for a business needs to have a Colorado address and serves as the contact for the entity. In the event of litigation, the service of process goes to the registered agent. |
| − | |data source=Data source/US-CO.BER | + | | data source = Data source/US-CO.BER |
| − | |technical key=agentmiddlename | + | | technical key = agentmiddlename |
| − | |parent concept=Data source/US-CO.BER/data model/entity | + | | parent concept = Data source/US-CO.BER/data model/entity |
| − | |cardinality=ZERO_OR_ONE | + | | cardinality = ZERO_OR_ONE |
| − | |data type=STRING | + | | data type = STRING |
| − | |path=agentmiddlename | + | | path = agentmiddlename |
| − | |concept role=LEAF | + | | concept role = LEAF |
}} | }} | ||
Latest revision as of 12:12, 11 May 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. | agentmiddlename |
|---|---|
| Description Informal and comprehensive human-readable definition of a concept. | Middle name of agent. A registered agent for a business needs to have a Colorado address and serves as the contact for the entity. In the event of litigation, the service of process goes to the registered agent. |
| Part of Hierarchical relation between two concepts of the CDQ Data Model. | Data source US-CO.BER |
| 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. | agentmiddlename
|
| Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model. | entity (US-CO.BER) |
| 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. | agentmiddlename
|
| 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 |