[georss] Quick Fire Summary

[Gregor J. Rothfuss]

Ron Lake wrote:

> This is why the GeoRSS documentation needs to be clear that it *is* lat,
> lon. So people like me, who implement on examples instead of specs,
> don't get confused. 
> 
> You need to reference an authoritative registry - which will soon be
> available.

referencing the correct spec is not enough. the kind of people who are 
attracted to georss for its simplicity won't read them. this is why i 
liked alan's idea of a visual check in the feedvalidator:

parse the coordinates people have in their feeds and ask them "are these 
where you think they should be?". and yes, having examples outside of 
90x90 makes it much more obvious if you got it right in your implementation.

the reason this came up in the meeting: we should not go off on wild 
goose chases to add obscure new functionality before we haven't made 
headway into this most basic interop problem.

there is also no need to make georss into kml.

the default experience for georss sucks. for example, if you click on

http://api.flickr.com/services/feeds/photos_public.gne?id=35034346572@N01&tags=cheese&format=rss_200&georss=1

you get a "subscribe to this feed" page (browser-specific). none of the 
default choices in there (bloglines, google reader, my yahoo, etc) do 
anything useful with the geo. we need to lobby the various rss reader 
developers to show a map if they detect geo (or some other useful UI). 
until that happens, georss is a failure, sorry.
_______________________________________________
georss mailing list
georss at lists.eogeo.org
http://lists.eogeo.org/mailman/listinfo/georss