Difference between revisions of "Address/type/unspecific"
Address/type/unspecific
Jump to navigation
Jump to search
(Spreadsheet import) |
|||
| Line 1: | Line 1: | ||
{{Data model value | {{Data model value | ||
|name=Unspecific Address Type | |name=Unspecific Address Type | ||
| − | |description=This type is assigned as [[address/type]] if no specific type is known. In most cases, this causes (at least) a data defect warning if [[business rules]] are applied to validate the related [[address]]. | + | |description=DEPRECATED - This type is assigned as [[address/type]] if no specific type is known. In most cases, this causes (at least) a data defect warning if [[business rules]] are applied to validate the related [[address]]. |
|data source=Data source/CDQ | |data source=Data source/CDQ | ||
|technical key=UNSPECIFIC | |technical key=UNSPECIFIC | ||
|parent concept=Address/type | |parent concept=Address/type | ||
}} | }} | ||
Latest revision as of 12:03, 13 May 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. | Unspecific Address Type |
|---|---|
| Description Informal and comprehensive human-readable definition of a concept. | DEPRECATED - This type is assigned as address/type if no specific type is known. In most cases, this causes (at least) a data defect warning if business rules are applied to validate the related address. |
| 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. | UNSPECIFIC
|
| Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model. | Address Type (CDQ.POOL) |
| Mapping |