So the language isn't just a hint, but a prerequisite as soon as a `language` field exists on the page model? That's a departure from the current model where the information in `proximity_info` is only used for setting preference.

The change would also be backwards incompatible. You can't be sure that a given application content is always included in all languages on a given site.