Why store both a canonical form and a local form of international addresses?

Why store both a canonical form and a local form of international addresses?

• A. To save storage and avoid duplication.
• B. To ensure data integrity only; local forms are unnecessary.
• C. To enforce a single canonical format across all systems.
• D. To support formatting and searching in different contexts while preserving the local representation.

Answer: (D)

Addresses arrive in many styles depending on country and system. Storing both a canonical form and a local form lets you do two essential things at once: reliable processing and authentic display. The canonical form standardizes the components (like street, city, postal code, country) so you can compare records, deduplicate entries, and enable consistent searching and interoperability across systems. At the same time, the local form preserves the exact, locale-specific representation as it was entered or officially used, which is crucial for displaying addresses correctly to users and for any country-specific formatting or validation rules.

That’s why the best choice highlights both formatting for display in different contexts and the ability to search and compare across datasets while keeping the original local representation intact.

The other options miss one or both benefits: trying to save storage by keeping only a canonical form ignores the need to display or match local representations; enforcing a single canonical format across all systems ignores local variations and can hinder user familiarity and correct formatting in different contexts; and treating local forms as unnecessary skips important usability and searchability considerations.