[OSGeodata] WFS-basic and geometadata exchange

[Pat Cappelaere]

Jo,

BTW, I believe that WFS-Basic should have a keyword filter.  This is a big
topic of discussion!  This would still keep it simple.

However, I think that the DescribeFeatureType function and the "pile" of
XMLSchema description verbiage being returned now pushes it over the top to
WFS-Complex.

So I guess we need a good definition of WS-Basic.  I am certain to be
challenged here but... Go for it!

To me, this means:
    - A simple http get
    - No coding required on client side
    - No XML/XSLT skills required on client side
    - Easy to implement on server side
    - Specification of one page or less
    - Output readable in a simple browser or news feed reader.

The best example to me is Google News.
Simply point your browser to: http://news.google.com/?output=atom
Works great with Safari.

Couldn't we think of a similar output for a simple catalog service for the
rest of us? 

Cheers,

Pat.

> From: Jo Walsh <jo at frot.org>
> Reply-To: <geodata at geodata.osgeo.org>
> Date: Sun, 22 Oct 2006 12:48:06 -0700
> To: <geodata at geodata.osgeo.org>
> Subject: [OSGeodata] WFS-basic and geometadata exchange
> 
> dear all,
> 
> I have not been thinking very hard about simple geometadata exchange
> interfaces recently  but every time i hear someone mention Raj's
> WFS-basic effort I jump a bit. You look at the query interface
> to it and it is very simplified - no Filters, just a bounding box and
> date start and end range. There is a DescribeFeatureType function
> which right now is returning a pile of XMLSchema description verbiage.
> I see a big place for dclite4g / GeoRSS in here - i would like to see
> Tom's OWSCat done over WFSBasic. One could even add in OAI-PMH
> functions like ListRecordTypes [sic?] as well, if needed. Am i making sense?
> 
> http://www.ogcnetwork.net/wfsbasic
> 
> cheers,
> 
> 
> jo