addressing

There is a middle ground and some common patterns that can help. The address field names are fairly standardized[0] and Google has an open dataset (used by Chrome and Android) describing which countries need which fields[1]. I have an older PHP library[2] and a newer Go library[3] that build upon this, while crowdsourcing fixes (since Google hasn't updated their dataset in a while). The Go library allows me to serve all address formats and state lists in a single HTTP request, which can then power a very fast JS widget. [0] Initially by the OASIS eXtensible Address Language (xAL) which trickled down into everything from maps to HTML5 autocomplete. [1] https://chromium-i18n.appspot.com/ssl-address [2] https://github.com/commerceguys/addressing [3] https://github.com/bojanz/address

I have a project with similar aims: https://github.com/commerceguys/addressing It uses the Google dataset, which is under the public domain. Might make sense to compare formats? Btw, I love how your worldwide.yaml, both the deduplication and the redirection for subterritories (such as Vatican City).

And the solutions for C++, Java, PHP: https://github.com/googlei18n/libaddressinput https://github.com/commerceguys/addressing

And my PHP reimplementation: https://github.com/commerceguys/addressing