Ben Caradoc-Davies wrote: > Justin Deoliveira wrote: >> Ben Caradoc-Davies wrote: >>> Justin Deoliveira wrote: >>>> So with the (FPT,GU) tuple returned, the binding for >>>> FeaturePropertyType is up next, and it will be asked for its >>>> properties being passed in the GU feature. >>> With gml:FeaturePropertyType it works. The problem I have is that I >>> have gsml:GeologicFeaturePropertyType which has no binding. This >>> property type is not derived from gml:FeaturePropertyType, nor does >>> it have to be to conform to the GML encoding rules. >> Interesting... and problematic. Is there a reason why it does not >> extend from FeaturePropertyType? Or some other type that marks it as >> a property type. > > There is no requirement to do so. The GML encoding rules state that it > is sufficient to follow the pattern. Model developers will not avoid > this patten when they know that other implementations can encode it. > > The example is from GeoSciML: http://geosciml.org/ > > An encoder for GML complex features must search the substitution group > of the enclosed element for permitted types. When I override > XSAnyTypeBinding to do this, it works. > >> I don't have a great idea of how to handle this one. My only thought >> would be to somehow associate with the geotools type that it is >> indeed a feature property type, via the type metdata or something. >> I believe Gabriel might have employed a trick like this way back when. > > No, I checked, he overrode XSAnyTypeBinding as well. Right. If I'm getting the point right, a feature object model may chose to follow or not the propery/Object pattern which is a recommendation in the GML spec, but as long as we can encode and parse general xml elements we simply don't care how it was modeled, right? so no trick to do on our side, there's no such a thing as a geotools feature property type... for example, if the model follows the property/Object pattern there might be a property like roadProperty/Road. Otherwise there might be simply a property named Road. There should be no difference for us in terms of parsing/encoding capabilities.
Cheers, Gabriel > I am still sweating blood trying to get trunk to work as well as > Gabriel's community-schemas version. It is quite an education. > > Kind regards, > ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
