Postal code schema
Public:Rule Category/POSTAL CODE SCHEMA
| Property | Value |
|---|---|
| A technical identifier, unique in a certain context. Technical key | POSTAL_CODE_SCHEMA
|
| The human-friendly name shown for this concept in the user interface, used instead of the technical name to improve readability and understanding. Display name | Postal code schema |
| An informal and short human-readable definition of a concept, in terms of a 'one-liner'. Short description | Validates that postal codes follow official formatting schemas with correct spacing and separators. |
| Informal and comprehensive human-readable definition of a concept. Description | This category includes data quality rules that verify postal codes are formatted according to official postal code schemas, including proper spacing, hyphens, and presentation. While basic format validation checks syntax, schema validation ensures postal codes match the exact official presentation used by postal authorities. For example, Canadian postal codes should be formatted as 'K1A 0B1' with a space in the middle, UK postcodes as 'SW1A 1AA' with a space before the final three characters, and Netherlands postal codes as '1234 AB' with a space. Proper schema adherence is important for postal processing systems, official documentation, and integration with address validation services that expect specific formatting. These rules support the Representational_consistency dimension by ensuring postal codes match official presentation standards defined by postal authorities. |
| Hierachical parent concept of a concept. Parent | Reference schema |
Data quality rules
CDQ manages 2 data quality rules in this category.
| Data quality rule | The country a linked concept is active or generally relevant for. Country scope | Informal and comprehensive human-readable definition of a concept. Description | Criticality<br/>Specifies how critical of the violation of a data quality rule.<br/>ERROR: Indicates a critical data quality rule violation that requires correction.<br/>WARNING: Indicates a potential data quality issue that should be reviewed.<br/>INFO: Indicates an informational finding with no immediate impact on data quality. Criticality
|
Rule release status<br/>The release status in terms of development progress or maturity of a data quality rule.<br/>IDEA: Initial rule definition that documents a business requirement but is not yet active in services.<br/>DRAFT: Rule concept is being prepared or refined but is not yet finalized for implementation or execution.<br/>HYPERCARE: Rule is newly released and under increased observation to ensure stable behaviour and correct results.<br/>RELEASED: Rule has passed verification and is actively executed in productive CDQ services.<br/>DEACTIVATED: Rule is temporarily removed from the active rule set because it needs correction or clarification before re release.<br/>ARCHIVED: Rule is permanently retired and no longer maintained or intended for future activation. Rule release status
|
|---|---|---|---|---|
Post code format inaccurate (Japan)REPRESENTATIONAL_CONSISTENCY
|
JP (Japan) | Post codes in Japan should always be used in the format NNN-NNNN. This means the hyphen is mandatory for this rule! | INFO
|
RELEASED(2024-04-16)
|
Post code format inaccurate (United States)REPRESENTATIONAL_CONSISTENCY
|
US (United States of America) | The US post code can contain a block of 5 digits or, for more accurate delivery, 9 digits in this format: NNNNN-NNNN. This is known as ZIP + 4.
In case if the post code still has 5 or 9 digits but in other format then NNNNN-NNNN (a space instead of a hypthen, 9 digits without any delimiter etc.) then the rule is broken. |
INFO
|
RELEASED(2024-04-16)
|