Re: [w3c/payment-request] PaymentAddress 'region' inconsistencies (#663)

Two-letter codes could work for [India](https://chromium-i18n.appspot.com/ssl-aggregate-address/data/IN/) using the `isoid` field. However, our [Australia](https://chromium-i18n.appspot.com/ssl-aggregate-address/data/AU/) data has three-letter abbreviations for states. Moreover, our [Ireland](https://chromium-i18n.appspot.com/ssl-aggregate-address/data/IE/) data shows some `isoid` fields with a one letter instead of two.

As for requiring the region in every country, from what I understand, that does not work well in all countries. For example, Google's address in Ireland is "Barrow St, Dublin 4". I do not have to specify the "Co. Dublin" county in order for my package to be delivered there.

All that being said, we can do a better job of normalizing addresses that we return from the browser. I definitely agree that Chrome should not be returning "Californnn" in the API.

@lararennie @roubert @sebsg 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-request/issues/663#issuecomment-352038897