In addition to GeoSPARQL, NeoGeo, INSPIRE, ISA Programme Location Core Vocabulary, schema.org and W3C Point of Interest, there is ADMS. This can describe a Community data Repository and its contents (Assets). Those Repositories have Assets@Location, and, for example, if Federal, State, Local, and Municipal Governments run the Repositories then they can be specified by the existing coding system.
For example, US Federal Information Processing Standards (FIPS) are a cascade system, but you can make Domains from the same codes. If you embed ADMS at the proper level, you create a Repository for that level with fixed metadata for the location.
I made an example of the “Tarrant County Texas Data Repository”.
Data : http://www.rustprivacy.org/2012/roadmap/locadd/em-adms1.txt
In XML with client-side XSLT (view the source to see the XML):
XML : http://www.rustprivacy.org/2012/roadmap/locadd/em-adms1.xml
It validates (http://www.rustprivacy.org/2012/roadmap/locadd/em-adms-trace.txt), although ADMS 0.8 was too big to put on my server.
Using the “Local Repository” as a proxy location, you can get Weather Forecasts and Reports, Water Quality Data, and all sorts of handy stuff. The main problem is the sheer number of Domain Identifiers – FIPS has about 40,000. The EU has 27 members, but that’s easy – just put an EU wrapper over the cascade (or FIFA, or G-20, or …)
PS You owe Makx a beer.