Familypedia:Site schema

Goals

 * 1) Commonality of names across languages
 * 2) Capability to scope queries based on knowledge of the containment hierarchy of locations. EG. that Calgary is a town is in a county is in a province (Alberta) is in a country (Canada).
 * 3) Capability to autocomplete forms based on containment hierarchy.

Categories versus Properties
Properties would have been used entirely except that nested properties cannot be used for autocompletion. For this reason we have both a category and property tree for locations.
 * Sublocations: Given a location, constrain autocompletion to a list of locations within that location
 * The Tree: Category:Valid name of {geographic group}- {location} is used for autocompletion. Given a location eg New York, it produces a list of all locations including subcategories nested within that tree.
 * Super Locations: Given a location, find the locations that it is within.
 * The Tree: Property: locality of subdivision and other Property:{geographic subgroup} of {geographic supergroup} allows an #ask on this property and either return the super location, for a given location or can constrain a query to a particular superlocation, or can list all sublocations of a given location. This is the preferred access mechanism for locations.  The Category tree is only for autocompletion.