Release notes: ============== * Exploration of Ecore, the model which drives the Eclipse Modeling Framework, and a comparison with the General Feature Model (GFM) * Proposed classes from 19103 which are going to be needed: Namespace (Qname isn't functionally equivilent), Record, and Multiplicity. Record is also going to be needed to implement coverages. Question: I dumped all these classes in org.opengis.util. Should we start making subpackages? * Proposed GeoAPI feature-related packages.
I think this does a pretty good job of capturing the GFM, without wrestling the poor user to the ground with a forbidding API. It is strongly influenced by Ecore, but the interfaces are expressed in terms of the TC/211 concepts. It is powerful enough to permit the generation of a correct UML diagram directly from the application schema, but this is hidden from casual users. There is a convention for the inclusion and instantiation of Factories with each package in an application schema. This model can easily accomodate both ComplexFeatures and Coverages. Please edit with your comments and return to me. Thanks, Bryce ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
