[georss] Transport of Toponyms with GeoRSS

Mon Aug 28 15:46:56 EDT 2006

Ron,

Where have you been?  This is the thread of this email!
Look again at that link: http://www.pubsub.com/earthquakes.php
Or look at feedster... There is certainly room for improvement and that's
where you come in :)

So let me rephrase my question again:
Should the GeoRSS feeds support those regions (in addition to geolocation)?
How much granularity should we give to our users?
Pat.

> From: Ron Lake <rlake at galdosinc.com>
> Date: Mon, 28 Aug 2006 12:37:03 -0700
> To: Pat Cappelaere <pat at cappelaere.com>, Marc <marc at geonames.org>, Carl Reed
> OGC Account <creed at opengeospatial.org>
> Cc: <georss at lists.eogeo.org>
> Conversation: [georss] Transport of Toponyms with GeoRSS
> Subject: RE: [georss] Transport of Toponyms with GeoRSS
> 
> Do your pub/sub aggregators deal with geography and time in their
> subscriptions?
> 
> R
> 
> -----Original Message-----
> From: Pat Cappelaere [mailto:pat at cappelaere.com]
> Sent: August 28, 2006 12:34 PM
> To: Ron Lake; Marc; Carl Reed OGC Account
> Cc: georss at lists.eogeo.org
> Subject: Re: [georss] Transport of Toponyms with GeoRSS
> 
> Ron,
> 
> No.  I am just talking about a generalized SAS as you are.
> I just tried to say that this pubsub function is not a WFS function but
> a
> SAS function although you really do not need a SAS if you publish
> content
> the right way.
> For instance, if you were to publish your data as a GeoRSS feed prior to
> storing that information in the WFS.  This data could be syndicated and
> could make its way to an aggregator using standard channels.
> Many of those aggregators support subscription/notification services so
> you
> really do not need a SAS per say (unless you want your own or a
> better/faster/cheaper one...)
> Pat.
> 
> 
>> From: Ron Lake <rlake at galdosinc.com>
>> Date: Mon, 28 Aug 2006 12:07:28 -0700
>> To: Pat Cappelaere <pat at cappelaere.com>, Marc <marc at geonames.org>,
> Carl Reed
>> OGC Account <creed at opengeospatial.org>
>> Cc: <georss at lists.eogeo.org>
>> Conversation: [georss] Transport of Toponyms with GeoRSS
>> Subject: RE: [georss] Transport of Toponyms with GeoRSS
>> 
>> Hi,
>> 
>> I agree that how WFS publish content should be more flexible as should
>> the means for sending commands to WFS.  We are exploring use of XMPP
> in
>> this context as well - essentially generalizing SAS.  I am not sure
> why
>> you say pub/sub is not needed in WFS.  How would you say - "I want to
>> know about entities in this geographic region that satisfy such and
> such
>> criteria"  - do you want everything from WFS to be polled?  Why?
>> 
>> R
>> 
>> -----Original Message-----
>> From: Pat Cappelaere [mailto:pat at cappelaere.com]
>> Sent: August 28, 2006 9:45 AM
>> To: Ron Lake; Marc; Carl Reed OGC Account
>> Cc: georss at lists.eogeo.org
>> Subject: Re: [georss] Transport of Toponyms with GeoRSS
>> 
>> Ron,
>> 
>> The point is that we do not need to have a WFS to get that capability.
>> We need to get OGC web services to syndicate content in a standard way
>> such
>> as GeoRss/Atom 1.0 format.  This can then be picked up by aggregators
>> such
>> as pubsub.com/feedster and this makea the data avaialble to a much
> wider
>> community using interoperable standards. Then we get into geoblogs,
>> geowikis, geoblikis...
>> 
>> This is where the action is.
>> 
>> To get there we need a better way to express contents (especially
>> geospatial
>> content).  GML is certainly a great step and we have to thank you for
>> it.
>> 
>> Again, if you look at the pubsub example, it is intriguing.
>> Should the georss feeds support that kind of added information?
>> I believe that Mark is pushing for something similar to address
>> granularity.
>> 
>> V/R,
>> 
>> Pat.
>> 
>> 
>>> From: Ron Lake <rlake at galdosinc.com>
>>> Date: Mon, 28 Aug 2006 09:17:47 -0700
>>> To: Pat Cappelaere <pat at cappelaere.com>, Marc <marc at geonames.org>,
>> Carl Reed
>>> OGC Account <creed at opengeospatial.org>
>>> Cc: <georss at lists.eogeo.org>
>>> Conversation: [georss] Transport of Toponyms with GeoRSS
>>> Subject: RE: [georss] Transport of Toponyms with GeoRSS
>>> 
>>> We also support subscriptions based on feature type and area of
>> interest
>>> in our WFS.  We can do geoRSS(GML) this way as well.
>>> 
>>> R
>>> 
>>> -----Original Message-----
>>> From: georss-bounces at lists.eogeo.org
>>> [mailto:georss-bounces at lists.eogeo.org] On Behalf Of Pat Cappelaere
>>> Sent: August 28, 2006 6:30 AM
>>> To: Marc; Carl Reed OGC Account
>>> Cc: georss at lists.eogeo.org
>>> Subject: Re: [georss] Transport of Toponyms with GeoRSS
>>> 
>>> Mark,
>>> 
>>> This is an interesting discussion.
>>> My big interest is in the support of user subscriptions based on
>>> geographic
>>> areas of interests (AOI) for alert notifications... Like the OGC
>> SAS/WNS
>>> :)
>>> 
>>> If you look at this pubsub example
>>> (http://www.pubsub.com/earthquakes.php),
>>> It would appear that the feeds would have to be encoded with the
>>> Flinn-Engdahl regions.  This would certainly avoid some expensive
>>> geo-spatial computations.
>>> I guess that the geonames example:
>>> http://www.geonames.org/geonamesRSS.html
>>> is similar in a way.  This is akin to a granularity issue, I suppose.
>>> 
>>> The big deal with georss is that you can define an wider and precise
>>> geographic area using gml.
>>> I think we need both.
>>> Could we get this to merge?
>>> 
>>> Pat.
>>> 
>>>> From: Marc <marc at geonames.org>
>>>> Date: Sun, 27 Aug 2006 23:03:24 +0200
>>>> To: Carl Reed OGC Account <creed at opengeospatial.org>
>>>> Cc: <georss at lists.eogeo.org>
>>>> Subject: Re: [georss] Transport of Toponyms with GeoRSS
>>>> 
>>>> Hi Carl
>>>> 
>>>>> If the georss group does decide to enable encoding of civil address
>>>>> information, why re-invent the wheel?
>>>> 
>>>> I would not go as far and speak about 'invention' in the context of
>>>> GeoRSS or RSS. All I am suggesting is using the country code
> invented
>>> by
>>>> ISO, use it for the vehicle RSS and call this combination GeoRSS.
>> (The
>>>> same is true for ISO 3166-2, the postal code and similarly for the
>>> place
>>>> name.)
>>>> The really hard work, the invention and maintenance is done by ISO.
>>> They
>>>> have invented the wheel. Using it in a xml schema is a piece of cake
>>> and
>>>> I don't really care how this combination is called. I have therefore
>>>> setup a draft for a "geonamesRSS" encoding :
>>>> http://www.geonames.org/geonamesRSS.html
>>>> 
>>>> Any comment is welcome. Either here or on  the geonames mailing list
>> :
>>>> geonames at googlegroups.com <mailto:geonames at googlegroups.com>
>>>> 
>>>> Cheers
>>>> 
>>>> Marc
>>>> _______________________________________________
>>>> 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
>> 
>> 
> 
> 