[georss] Transport of Toponyms with GeoRSS

[Ron Lake]

Hi,

A name for a point, a geometric point I would say is something different
from naming a feature.  The latter refers to some identifiable (in an
application context) entity which one could identify without actually
knowing in any precise way its location.  Points in this object might be
given identifiers and located and then treated as the nominal location
of the object.  A named point to me would be more like in say an active
(or passive) control network - namely just being a geometric point with
identity.  This might be a point on an object (e.g. those markings at
the intersections of roads used as control points for aerial
triangulation) or GCPs.  In the usual sense of the word, a toponym is
NOT the name of a geometric point, but rather the name of a geographic
feature.  To me this means that there has to be features in order for
them to have names.

Cheers

Ron

-----Original Message-----
From: georss-bounces at lists.eogeo.org
[mailto:georss-bounces at lists.eogeo.org] On Behalf Of Josh at oklieb
Sent: August 15, 2006 3:54 PM
To: georss at lists.eogeo.org
Subject: Re: [georss] Transport of Toponyms with GeoRSS

Aye, there's the rub. What is it you are describing with a toponym?  
The resource described by the RSS entry (probably not in general a  
toponym) or the "feature-ness" of the resource which is bestowed upon  
it by GeoRSS.

It seems you want to construct a link with two characteristics: a  
zoom-in action and a label to suggest what is geographically being  
zoomed in to. The former could be addressed with the "radius"  
attribute; the latter is probably a use case for adding a "name" or  
"featurename" attribute to georss:point / georss:where.

Just a heads up that applying georss to update w3c geo (and thereby  
also making it more palatable to the microformat-ists) means in all  
likelihood coming up with an rdf serialization of georss. This means  
that the attributes we have hung on the georss properties such as  
georss:point cannot be there (being properties themselves, they can  
only describe a node or concept). This means either turning  
somersaults conceptually or moving the attributes up into separate  
rss properties, e.g. (rss 1.0)

<item rdf:about=
       'http://www.oreillynet.com/pub/wlg/8466?CMP=OTC-TY3388567169'>
   <title>Live Coverage XML 2005 (Tuesday Keynotes)</title>
   <link>http://www.oreillynet.com/pub/wlg/8466?CMP=OTC-TY3388567169</ 
link>
   <description>
	   <![CDATA[A live look at the XML Keynotes and seminal
talks.]]>
   </description>
   <dc:creator>Kurt Cagle</dc:creator>
   <dc:date>2005-11-15T07:45:58-08:00</dc:date>
   <georss:featuretypetag>TGN:City</georss:featuretypetag>
   <georss:featurename>US_Cities:Albany</georss:featurename>
   <georss:radius>5000</georss:radius>
   <georss:point> 46.183 -123.816</georss:point>
</item>

In essence, the <title> property describes the item resource, while  
the <georss:featurename>  property describes the item "feature"

I'll look for the time to explain this more graphically.

--Josh

On Aug 15, 2006, at 6:27 PM, Allan Doyle wrote:

>
> On Aug 15, 2006, at 18:09, noiv wrote:
>
>>> Couldn't you simply use the RSS "title" field for the link?
>>>
>>> Mikel
>>
>> Hi Mikel,
>>
>> thanks for input. Publishers use the title tag as a description
>> of the content. I think there is no chance to convince for example
>> Reuters and have toponyms only as title.
>>
>> Which tag is designed to describe the coordinates
>> of a GeoRSS feed entry in a human readable way?
>>
>
> Is this perhaps the difference between RSS and a microformat? My
> impression is that microformats are meant to encapsulate information
> that is meant to still show up on the web page whereas RSS is really
> not meant to be "human readable" in the sense of being shown directly
> on a web page.
>
> Thus if you have a microformat + CSS, you can see something useful.
> If you have RSS + CSS that's not always the case, you may also need
> some XSLT or some other processing to make it "pretty" again.
>
> One of these days we need to work out the microformat serialization
> of GeoRSS. Ideally by working together with the microformat folks.
>
> 	Allan
>
>> --
>> noiv - ExploreOurPla.net
>> _______________________________________________
>> georss mailing list
>> georss at lists.eogeo.org
>> http://lists.eogeo.org/mailman/listinfo/georss
>
> -- 
> Allan Doyle
> +1.781.433.2695
> adoyle at eogeo.org
>
>
>
> _______________________________________________
> georss mailing list
> georss at lists.eogeo.org
> http://lists.eogeo.org/mailman/listinfo/georss

_______________________________________________
georss mailing list
georss at lists.eogeo.org
http://lists.eogeo.org/mailman/listinfo/georss