How should we handle multiple hierarchies for a single place?

[riordan]

Who's on First is designed to provide multiple hierarchies for a single place (a restaurant in multiple, overlapping neighborhoods or a disputed territory like the Golan Heights or Kashmir).

We're going to need a way for each place to have the potential of multiple hierarchies. But how?

[dianashk]

Will discuss as part of the WOF integration

[riordan]

This applies to more than just the Who's on First records.

An OA or OSM record may be in multiple hierarchies.

[riordan]

What is the simplest, dumbest thing that works right now?

The system MUST be deterministic; same output no matter what the RNG feels like at the time of the build

[riordan]

If the PiP server responds with more than one value for a hierarchy, we're just going to go with the first hierarchy for now.

This could result in bad data, so if the issues are severe enough, we'll immediately reprioritize this.

However, we'll know where the issues are because we'll be logging and tracking where all these issues are.

@trescube: could you flag areas where this may lead to bad data conflicts?

[frodrigo]

The request should also select the "right" hierarchy. Depending of your country or point of view you want only one of this hierarchy. The hierarchy must not only exist, but have acceptable point of view. The request should have country parameter (eg. Ukraine or Russia) and the result about Crimea depend on this.

The WOF disputed attribute is insufficient to do this. The list of disputed area are insufficient and the point of view are not present. Eg. Taiwan is not marked as disputed.