Questions regarding the CSW 2.0.2 bindings.

We ran into the issue where the CSW 2.0.2 bindings return java.lang.Object instead of the expected OGC Filter object.

That [change in behaviour](https://github.com/highsource/ogc-schemas/commit/bd070174011708ec239d55914507cf381b0efdb8) looks to have been to reduce the context mappings needed to unmarshal a CSW 2.0.2 document.

While I can certainly appreciate the size of the dependency tree for that schema and we could certainly work with those generated bindings, it is a shame to have to trade off compile-time type safety for dynamic runtime checks.

@highsource, could you elaborate on why you felt the mappings needed to be reduced? Was there a problem that was encountered that this was trying to solve? Were you just trying to make it easier for a client to set up the context object? Did you want a smaller footprint for the JavaScript bindings?