On 28/11/13 02:09, Andrea Aime wrote: > My impression is that the in memory model of app-schema uses pointers, > so there are > no special containment vs reference nodes, but when encoding, the first > element encountered > gets encoded as containment, and all the subsequent references to the > same identifiable > object are encoded as references. Is this right?
Andrea, that is correct. GML 3.1 and GML 3.2 GMLConfiguration register a component instance of XSDIdRegistry to record ids seen in an instance document. If the encoder sees an id a second time, the element (typically a feature) is encoded as an xlink:href to the earlier id as an anchor (#earlierid). Note that filters work against the logical information model, not the encoded form (in most cases) so filters against nested properties work even for features encoded by reference to prevent duplication. Rini might be able to clarify/confirm. I think Niels answered your questions on resolve, which he implemented. Kind regards, -- Ben Caradoc-Davies <[email protected]> Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
