Rob Atkinson ha scritto: > Here are some further thoughts on this matter: > > https://www.seegrid.csiro.au/twiki/bin/view/AppSchemas/FeatureModel#GML_Feature_Collection > > > > Given this, we care about a FC as a transfer object I think - maybe it > should be nothing more than a handle on a virtual set of Features, than > can be serialised if desired, and unmarshalled into another FC instance.
GML FeatureCollection is just a way to store data, it's a full representation of it, GeoAPI feature collection is a data access mediator. Two different animals imho, and it's a bad thing they do share the same name. > My own experience suggests that FCs come into play when we want to > serialise relationships between features of different types, and > defining a specialised FC can provide serialisation strategies (which > types to serialise first to make serialisation and parsing easiest - but > I'm not convinced the answer to this is straightforward either) Well, but you do use them also as GetFeature response, again, as data transport tool (not as a mediator). GML elements should be used as a data model, not forced to describe data access as well imho. GeoAPI FeatureCollection mixes in different concerns as a result creates confusion imho... Cheers Andrea ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
