[georss] Georss extension

[Raj Singh]

It seems reasonable to put those tags inside the <georss:where> element
since they relate to location. They, of course, wouldn't be 'official'
GeoRSS elements, but good parsers should ignore anything they don't
understand, and as long as the required GeoRSS elements were included, it
would still be well-formed GeoRSS.
 
--Raj

On 9/9/06 4:53 PM, "Pat Cappelaere" <pat at cappelaere.com> wrote:

> Well, that's the question.
> It does feel like georss, addresses some granularity issues and allow for
> easier publish/subscribe.
> Pat.
> 
> 
>> From: "Kralidis,Tom [Burlington]" <Tom.Kralidis at ec.gc.ca>
>> Date: Sat, 9 Sep 2006 16:07:35 -0400
>> To: Pat Cappelaere <pat at cappelaere.com>, <georss at lists.eogeo.org>,
>> "Josh at oklieb" <josh at oklieb.net>
>> Conversation: [georss] Georss extension
>> Subject: RE: [georss] Georss extension
>> 
>>  
>>> Would this be acceptable to extend georss this way?
>>>     <georss:where>
>>>       <gml:Point>
>>>         <gml:pos>-159.774,62.1664</gml:pos>
>>>       </gml:Point>
>>>     </georss:where>
>>>     <georss:zone_number>1</georss:zone_number>
>>>     <georss:zone_name>Central Alaska</georss:zone_name>
>>>     <georss:region_number>1</georss:region_number>
>>>     <georss:region_name>Alaska - Aleutian Arc</georss:region_name>
>>> 
>>> I need to extend the EO-1 Geobliki atom feeds so we can test
>>> the SAS/pubsub mechanism and I need to stay away from spatial
>>> operations for the moment...
>> 
>> Do we need to get GeoRSS involved at all here?  You can put these under
>> another namespace.
>> 
>> ..Tom
>> 
> 
> 
> _______________________________________________
> georss mailing list
> georss at lists.eogeo.org
> http://lists.eogeo.org/mailman/listinfo/georss