Rename geoip to location

The current geoip fields (https://github.com/elastic/ecs#geoip) are inspired by the geoip ingest processor form Elasticsearch (https://www.elastic.co/guide/en/elasticsearch/plugins/6.2/using-ingest-geoip.html). In recent discussion around geo fields it became clear not all geo information is coming necessarly from an ip address and there is also geo / location information which does not necessarly can be extracted from an ip.

I would like to suggest to rename geoip fields to location. I was also thinking of renaming it to geo but I think location is more specific.

[nickpeihl]

My preference is geo and geo.location. “Geo” is a common designation in the GIS industry (Geospatial, GeoJSON, Geographic Information Systems). And, imo, it’s a better specifier as a top level element than location since “location” may also be used in non-spatial contexts (URLs, files on disk).

[jordansissel]

+1 to renaming geoip to location. This would allow folks to place any where-style data in this set, such as: region, cloud platform, datacenter, rack, building number, address, zip code, etc.

Not all where have “geo” or “ip” concepts, so I think location matches much more nicely.