Geo NIC: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m (Probably SPAM related to the GEOnic.net. Redirecting to "Internet: Ways of linking schools to the outside world") |
||
(32 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
#REDIRECT [[Internet#Ways_of_linking_schools_to_the_outside_world]] |
|||
A NIC could serve a new top level domain ".geo" |
|||
The hierarchy under that domain could be predefined as |
|||
[http://en.wikipedia.org/wiki/UN/LOCODE UN LOCODE].[http://en.wikipedia.org/wiki/ISO_3166-2 ISO 3166-2 subdivision].[http://en.wikipedia.org/wiki/ISO_3166-1 ISO 3166-1 alpha-2 country code].geo |
|||
For example: |
|||
nyc.ny.us.geo for New York, USA and |
|||
cgn.nw.de.geo for Cologne, Germany. |
|||
Airports could be listed under [http://en.wikipedia.org/wiki/IATA IATA code].airport.geo. |
|||
IATA codes and location codes could link conveniently to a map of the region. (e.g. on Google Earth or similar services, possibly based on user preferences). |
|||
On the next level businesses could reserve their own homepages. |
|||
All "www" addresses could be reserved as free redirects to the home page of a city, region or airport. |
|||
== Service type == |
|||
One could also register businesses according to service type. A service type identifier could then list all businesses of that type: supermarket.nyc.ny.us.geo would list all known supermarkets in New York (with an option to switch between map and list view). |
|||
[[Category:Fundraising idea]] |