A good explanation of this against competing standards seems to be available here [1]. It seems weird that they complain about discontinuities in such a system,

A good explanation of this against competing standards seems to be available here [1]. It seems weird that they complain about discontinuities in such a system, where there has to be some discontinuities in a tiled system. Now, could this be used as an alternative to DNS? have a registrar per tile, and delegate if necessary. I wish this could be used as a geo: URL, or as a location field in my ical invites. I guess I need better support in various apps for it. Maybe it lack elevation information to specify meeting rooms, though? Perhaps it could be extended to support both ground and absolute elevation. Excluding words somewhat makes sense, but also removes some opportunities for artificial attractions, it isn't like some areas don't already have interesting ones [2]). So I am a bit split on this one, as it does generate longer names. Maybe emojis would be a better fit? Now, a note about standard presentation: I would have preferred a technical overview to an introduction that merely sums up some obvious (to me) facts, without really getting into explaining the standard. Perhaps someone has already come up with a way to publish standards together with a few sliders to control the amount of content displayed? That would be great. [1]: https://github.com/google/open-location-code/wiki/Evaluation-of-Location-Encoding-Systems https://github.com/google/open-location-code/wiki/Evaluation... [2]: https://www.estately.com/blog/2016/09/the-complete-list-of-lewd-sounding-town-names-in-america/ https://www.estately.com/blog/2016/09/the-complete-list-of-l... as an example, it gets worse if you include foreign cities, regardless of the language.