Just a quick comment because we were confused here: >> Understood; the only remaining attraction I have to the idea is >> defining a factory so we could intercept requests to external >> graphics and handle them locally as an optimization I guess. > I lost you there. How is this any better than rolling the plugin > system against the WellKnownName? Pros: allows us to optimize external references (and replace them with the use of a internal factory seamlessly). Cons: stupid; wellknownname makes more sense
I have looked quickly at the 1.1 documents: - http://www.opengeospatial.org/standards/symbol - http://www.opengeospatial.org/standards/sld It looks like there are now three options: - wellknown name - online resource (with optional format or mark index) - inline content (in binary or xml) (with optional format or mark index) Where the following is listed about mark index: > The alternative to a WellKnownName is an external mark format. The > MarkIndex allows an individual mark in a mark archive to be selected. > An example format for an external mark achive would be a TrueType font > file, with MarkIndex being used to select an individual glyph from > that file. In a fit of stupidity mark index is an integer and not an expression :-( Just like well known name is a string ... sure wish I was involved more in the OGC these days. Cheers, Jody ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
