[georss] Lack of standardisation and forethought in Draft for Encoding Geographic Features in GeoRSS

[Andy Mabbett]

Hi,

My first post to this list ;-)

If I use geo-metadata in my web pages, I have to use two formats:

         <meta name="ICBM" content="52.6866, -2.1937">

(with a comma separating the latitude and longitude)

         <meta name="geo.position" content="52.6866; -2.1937">

(with a semi-colon separating the latitude and longitude)

and now, I see, that the "Draft for Encoding Geographic Features in
GeoRSS":

         http://georss.geonames.org/georss-draft.html

proposes using a space as a separator:

         <georss:point>45.256 -71.92</georss:point>

This makes my head hurt!


Also, I see that the draft says of the IETF encoding:

         Too complex for our needs (we don't need room numbers ...)

but suppose someone has an RSS feed for a list of, say, events at a
conference, including the room number of each...

-- 
Andy Mabbett
                 Say "NO!" to compulsory ID Cards:  <http://www.no2id.net/>

                 Free Our Data:  <http://www.freeourdata.org.uk>