Richard Soderberg posted the following email to the geowanking list on Wednesday. It’s a nice review of the various geo-syntaxes currently in use.
If you know of any others, please let me know.
What all is out there currently, and what’s the conglomerate of them all look like for a given page?
The conglomerate of <HEAD> modifications from what I’ve looked at so far:
<head profile=”http://geotags.com/geo”>
<meta name=”ICBM” content=”44.07,-123.08″ />
<meta property=”geo:lat”>46.1</meta>
<meta property=”geo:long”>124</meta>
<meta name=”geo.position” content=”44.07;-123.08″>
<meta name=”geo.region” content=”US-OR”>
<meta name=”geo.placename” content=”Eugene”>
</head>There’s only one way I’ve found, so far, to associate the data with a given container element:
<span style=”display:none” xmlns:geo=”http://www.w3.org/2003/01/geo/wgs84_pos#”>
<geo:lat>46.1</geo:lat><geo:long>124</geo:long>
</span>Reading an XHTML specification, I find that <meta property> can be used with <link rel=”profile”> to indicate the definitions of certain metadata attributes such as geo:lat, geo:long, and geo:alt. As such, the following syntax should be:
(a) XHTML compliant
(b) human and X?HTML-editor readable
© easy to detect with existing HTML spiders
(d) not limiting future development of shapes and so on.I think it’d be a worthy successor to the ICBM header, even if it’s slightly larger in byte-size. That said, it may not serve the one-tag desires or the per-item desires. I submit this for discussion.
<head>
<link rel=”profile” href=”http://www.w3.org/2003/01/geo/wgs84_pos#”>
<meta property=”geo:lat”>46.1</meta>
<meta property=”geo:long”>124</meta>
</head>- R.
GeoURL:
- To tag an HTML document, put this in the HEAD block:
<meta name=”ICBM” content=”44.07,-123.08″ />Map Bureau:
- To tag an HTML document, put this in the HEAD block:
<meta property=”geo:lat”>46.1</meta>
<meta property=”geo:long”>124</meta>- To tag an HTML container element, include the following block:
<span style=”display:none” xmlns:geo=”http://www.w3.org/2003/01/geo/wgs84_pos#”>
<geo:lat>46.1</geo:lat><geo:long>124</geo:long>
</span>Blogmapper:
- To tag an HTML container element, include the following block:
<span style=”display:none” xmlns:geo=”http://www.w3.org/2003/01/geo/wgs84_pos#”>
<geo:lat>46.1</geo:lat><geo:long>124</geo:long>
</span>Geotags:
- To tag an HTML document, put this in the HEAD block:
<head profile=”http://geotags.com/geo”>
<meta name=”geo.position” content=”44.07;-123.08″>
<meta name=”geo.region” content=”US-OR”>
<meta name=”geo.placename” content=”Eugene”>Locative:
<rdf:RDF
xmlns:rdf=”http://www.w3.org/1999/02/22-rdf-syntax-ns#”
xmlns:rdfs=”http://www.w3.org/2001/02/rdf-schema#”
xmlns:geo=”http://www.w3.org/2003/01/geo/wgs84_pos#”
xmlns:dc=”http://purl.org/dc/elements/1.1/”
xmlns:locative=”http://locative.net/etcon2004/loc#”
xmlns:media=”http://purl.org/dc/dcmitype/”
>
<locative:Packet><dc:coverage>
<geo:Point>
<geo:long>-0.0104</geo:long>
<geo:lat>51.5722</geo:lat>
</geo:Point>
</dc:coverage><locative:media>
<media:Image
rdf:about=”http://iconocla.st/photo/2003/10/12/img_0299-m.jpg”
dc:format=”image/jpeg”/>
</locative:media><rdfs:seeAlso rdf:resource=”http://iconocla.st/photo/2003/10/12/img_0299.html”/>
</locative:Packet>
</rdf:RDF>
