The answer (apparently) to list each function with a "fallback value"; please see the SE 1.1 specification for details. So you would list all the possible functions; if the user tries to call a function in a context where it can not be understood the fallback value would be used.
I am not saying this is a great solution; just the one developed by the SE 1.1 spec. Jody > Because WFS does not allow different functions by feature type, > functions not supported by all feature types cannot be published in the > WFS capabilities. So how do clients know what they can call? There has > to be some sort of back-channel agreement. Some have referred to this as > a profile, and the publication and discovery of these is an open > question. (Cue Rob Atkinson ...) > > >> Sorry I did not have the time to follow the debate on this topic >> when it was happening (a couple months ago I believe), so maybe >> I'm missing something obvious here? >> > > No, these are the right questions to ask. > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
