> > Can you make me an example of "getting the info from the optimal place > in the optimal way"? Afaik with the current configuration API we have > just one place to grab each information we need to build up a UI, > and this sounds like a very good thing (TM) imho. >
OK, for example, we specify namespaces in several locations (schema, info, datastore config, catalog file, SLD), but they should all be inherited from the target schema (yes I know I'm talking about community schema support, but there is very little requirement for WFS without it - do you see many deployed?) likewise, any filter or attribute controlled style in an SLD refers to the schema. We should put database connection params in one spot, not in each feature type. all the "service metadata" probably ought to be derived from the deploying organisations policies, and be linked to metadata in something like GeoNetwork, not retyped. etc I see very little metadata or configuration that a deployer ought to "make up" as they configure. (but then again, my background is in building clients to use these services, and registries and metadata to describe them - so i'm convinced its more important to make it meaningful for the many users than the few deployers or very few developers.) :-) Rob > Cheers > Andrea > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
