Robert, thanks for your feedback > Yes I believe it's the right way to go... If we had somewhere a central > repository of WMS servers (eventually with their capabilities cached on it), > WMSManager could request it, eventually on various criteria (for example > given a current viewbox ?), it would just have to implement a request > protocol and response processing (does exist an OGC one ? Could it be about > "registry" ?) > > This repository could be cooperative, if you know a server which isn't on the > list you could put it on, just like web2 "social sites". > > Currently I'm maintaining my own list on del.ico.us (see > http://del.icio.us/rrpro/wmsserver) > But of course it's just a flat list of links. The same thing with OGC-aware > processing functions would be wonderful. > Just dreaming... > >
An OGC Catalogue Service (CAT) [1] interface should be the best solution IMO. Thanks to Schuyler and Chris that are updating the cgi proxy it will be easier to add servers on the fly to WMSManager. I'm studying the way to do the CATManager and all feedbacks about it are precious. It is important to remember that a OWS resource without Metadata means quite nothing. That's why the CAT make sense. A good example is FAO GeoNetwork [2]. I would like to make a minimal interface to CAT for a generic user. If you have examples to show and suggest, I'll be pleased to have a look. ciao Lorenzo [1] http://www.opengeospatial.org/standards/cat [2] http://www.fao.org/geonetwork/srv/en/main.home _______________________________________________ Dev mailing list [email protected] http://openlayers.org/mailman/listinfo/dev
