Why store canonical address components instead of final formatted strings?

Why store canonical address components instead of final formatted strings?

• A. Store final formatted strings
• B. Store canonical components to enable locale-sensitive formatting at display time
• C. Store only postal codes
• D. Store addresses in a fixed global format

Answer: (B)

Storing canonical address components means saving each part of the address as its own field (street, city, region, postal code, country) rather than a single preformatted string. This separation allows you to apply locale-aware formatting rules when you display the address. Different regions use different orderings, separators, and punctuation, and some languages may have specific script or typographic conventions. By keeping the parts separate, you can assemble the correct format for any locale at render time, validate each element individually, and support features like searching, autocompletion, deduplication, and analytics that rely on the actual components rather than a single text blob. If you stored final formatted strings, you’d be locked into one representation, making it hard to adapt to other locales or to update formatting rules. Approaches that store only a postal code or force a fixed global format lose essential structure and localization capability.