- From: Erik Wilde <dret@berkeley.edu>
- Date: Thu, 09 Jul 2009 12:55:04 -0700
- To: public-geolocation@w3.org
- CC: hedenus@pixel.de
hello michael. Michael Hedenus wrote: > You're both right. You can address a position or a point of intereset > (POI) with a URI (e.g. http://www.walhalla-regensburg.de) which provides > RDF data with geo-properties (which are widely used) and at the same time > with a geo-URI. Both ways complete each other. > But to set up the connection betwen a POI and its geolocation you need a > tool and a application. That's the reason why it would be great not only > to have an API to get a position but also to connect a position with > (meta)information. The API could be the "missing link". given your example you seem to see a POI as an HTTP URI, and then you want to associate some description about that resource with the resource (the POI identified by an HTTP URI) via some discovery mechanism. this is actually a very generic problem of the semantic web, and not at all location-specific (because the description could be anything, not just geolocation information). consequently, you might want to look into a general mechanism for description discovery for URI-identified resources, and there currently is a lively thread about this exact problem over at uri@w3.org: http://lists.w3.org/Archives/Public/uri/2009Jun/0011.html cheers, dret.
Received on Thursday, 9 July 2009 19:55:59 UTC