[georss] GeoRss Encoding

[Joshua Lieberman]

On Oct 12, 2007, at 4:04 PM, Chris Howell wrote:

> Josh,
>
> Yes I thought that I probably should have put it inside of the georss
> elements after I put it in, it was a typo essentially.

That is precisely what would "not" be alright to do. GeoRSS specifies  
in some detail what goes inside georss elements so that it can be  
interpreted both widely and correctly. Putting something outside of  
georss:where in its own namespace is the safest way to go.

>    I don't really care if Jim Bob's feed aggregator strips it off, our
> vendor specific element. I am well aware of the fact that we are the
> only ones that will be able to read it. What it will allow me to do is
> have someone running our app in one sense Geo-tag something in  
> their app
> and have our apps feed aggregator pick up and know how to interpret  
> that
> coordinate. Plus I think it allows anyone else using a different
> application to look at something geo-tagged in Pyxis because it would
> still contain the native lat/lon of a WGS84 component. What they  
> choose
> to do with something they don't understand its really their choice.
>
> Chris
> _______________________________________________
> georss mailing list
> georss at lists.eogeo.org
> http://lists.eogeo.org/mailman/listinfo/georss