So I finally sorted out the catalogue trinity last week in Perth - due to a good update on the Resource/Publishing split from Justin last week.
I am still stuck on the naming of things but progress has been made ... - Workspace - basically folders for DataStores; no real significance in terms of publication of data - Maps - this defines how publication happens; the only thing significant in terms of publication of data - Profile - sets logging level and other application preferences/settings My earlier confusion came from thinking the above concepts were tied together (like you could publish the same map twice using different workspaces). Instead I find they are a trinity each seperated from the other that together form the geoserver configuration. With this in mind: - Maps are still a very difficult name - but they do each represent a public "GeoServer" with as many OGC services enabled as needed. - It would be *so* nice to refer to Map above as a "Service" and refer to enabling/disabling the various WMS/WFS/WCS things as "Protocols" enabled for that service. Out of all the naming ideas this one made the most sense; indeed once we step beyond OGC (with REST etc..>) it becomes even more clear. - The concept of a Map is is exactly what RobA was calling a "profile" (so that one could publish a profile for INSPIRE complete with the correct FeatureTypes; Styles and so on) which could be downloaded and added to your geoserver configuration. Backing this profile onto your own data would be the interesting part. - The current association of namespace to workspace was causing a lot of trouble for people; offering lots of opportunities for confusion. Jody ------------------------------------------------------------------------------ _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
