I am grabbing a couple of RFC from the list around the idea of storing styles (SLD or SE) and symbology (icons.zip, icons.ttf etc…).
The existing RFCs were written with a catalog handle for each kind of content: StyleResource, SymbologyResource and so on. The idea is that we would list styles in our catalog in a similar fashion to how an OGC catalog works; and thus be able to query for a list of "predefined" styles for a given dataset. I also really want to have "predefined' maps, in the same fashion as we have page templates. One of our most common requests is how an application can include an example Map for people to start from. Listing it in the file > new > map wizard would be a good answer. In double checking these designs against the OGC catalog spec; I am stumbling (perhaps slowly) onto an idea. OGC Catalog has the concept of the catalog storing small files *in* the catalog. I think I could mirror this design choice and give us a catalog entry that works for any of these file types; as long as the metadata story is okay we should be able to short list these based on their schema and gets good list of "predefined" styles. As for correct metadata - I am going to review the use: - "schema" - several good ResourceType URIs are available in Table 69 of the Catalog Spec (for things like our WMSService GetCapabilities) - "mimeType" - this is the one that will be helpful -- Jody Garnett
_______________________________________________ User-friendly Desktop Internet GIS (uDig) http://udig.refractions.net http://lists.refractions.net/mailman/listinfo/udig-devel
