Skimming through the docs, even though warts of postal addressing are mentioned, this seems like a (base-14?) encoding of geocodes rather than unified hierarchi

Skimming through the docs, even though warts of postal addressing are mentioned, this seems like a (base-14?) encoding of geocodes rather than unified hierarchical postal addressing (which is still an accomplishment, and something I can see a need for). Though this seems to work for latin scripts only I guess. For actually representing global postal addressing schemes with all warts and historic practices, I know no better standard than UPU S-1. I had a project for (partially) implementing it for a large logistics provider ten years ago. It was one of the few cases where using XML for business data genuinely made sense, as addresses could be represented in a line-oriented format (as you'd write on a postal piece) and at the same time structured info in the address (postcodes, streets, house numbering tokens) could be tagged for extraction, validation, etc. Though to make end-of-line chars significant in XML (which we had to somehow because postcodes are often placed at the begin or end of a line in formal addresses) we had to represent addresses basically as address_line_1, adress_line_2, etc. SGML could've handled this much more elegantly, as not only can it assign meaning to line breaks via short references, it also (theoretically) allows representation of overlapping (concurrent) tagging structures for two or more vocabularies.