[georss] What's next--a query API

[Carl Reed OGC Account]

Yes, I like the way this conversation is gelling into consensus. I would, as 
Raj suggests, take baby steps in terms of additional GeoRSS functionality. 
Feature creep could end up marginalizing the work this group has done. Best 
to suggest to those that want more "power" to go to full blown, standards 
based use of web services such as WFS and SOS (sorry Ron . . .)

Using a WFS that can ingest/output GeoRSS-GML seems a logical extension for 
those in OGC land. I would agree that a best practices document would be 
good. I suspect that a little email to the WFS WG on this topic and we would 
have an implementation sometime in the near future :-)

Cheers

Carl

----- Original Message ----- 
From: "Raj Singh" <raj at rajsingh.org>
To: <georss at lists.eogeo.org>
Sent: Monday, May 08, 2006 7:22 PM
Subject: Re: [georss] What's next--a query API


>I only want to stop at BBOX to keep things sane for those systems that are
> interested in becoming "real" GIS software.
>
> If you want really robust geo support, I think the way to go is to simply
> use WFS with GeoRSS-GML as the output format. That's a nice, clean way to 
> do
> it. Eventually I see us describing scenarios like this as "best practices"
> somewhere on the site.
>
> --
> Raj
>
> On 5/8/06 9:05 PM, "Pat Cappelaere" <pat at cappelaere.com> wrote:
>
>> GeoRSS enabled software would store GeoRSS feeds in a WFS (or 
>> equivalent).
>> Users could then do spatio-temporal queries (why stop at BBOX queries!) 
>> and
>> keyword search based on contents of the feed.
>
>
> _______________________________________________
> georss mailing list
> georss at lists.eogeo.org
> http://lists.eogeo.org/mailman/listinfo/georss