[georss] Transport of Toponyms with GeoRSS

[Josh@oklieb]

Marc,

If you take off the outer tags here from your example, which are  
incorrect for georss simple, then you have the RDF-compatible pattern  
I've proposed for additional georss properties such as  
<georss:featureName>.

However, there are established and popular schemas for at least some  
of the elements you list here. For example, there is a dublin core  
encoding for country code and foaf for some address information. It  
might be better to endorse the use of some of these rather than  
making georss a place for tackling the address mountain.

[<georss:where>]

    <georss:point>45.256 -71.92</georss:point>
    <georss:countryCode>AU</georss:countryCode>
    <georss:regionCode>NSW</georss:regionCode>
    <georss:city>Wollongong</georss:city>
    <georss:postalCode>2500</georss:postalCode>
    <georss:address>1600 Pennsylvania Avenue NW</georss:address>

[</georss:where>]

--Josh


On Aug 17, 2006, at 11:02 AM, Marc wrote:

> I think this problem is due to the lack for encodings of semantic
> geographic information in GeoRSS such as country, administrative
> division or placename. We have discussed this before and the  
> discussion
> has been compiled in a draft :
> http://georss.geonames.org/georss-draft.html
>
> Not only could semantic geographic information in GeoRSS be used to
> display labels but also for fundamental use cases in automatic
> processing like filtering, grouping, prioritizing of feed items
> according to geographic criteria. We shouldn't discard this issue as
> 'human readable' versus 'not human readable'. It is simply an  
> important
> and missing feature in GeoRSS.
>
> Cheers
>
> Marc
> _______________________________________________
> georss mailing list
> georss at lists.eogeo.org
> http://lists.eogeo.org/mailman/listinfo/georss