Hey, Congratulations on the work.
Could you explain the rationale for the "Applications" name? As I understand it (badly), your work aims to build a mechanism for access to data defined through 'multiple', possibly 'distant', schemas. In that context "Application" at best means nothing at worst is misleading to new users. But perhaps that is wrong; either way, we need a rationale that we pass on to users when they ask questions. cheers, --adrian On Mon, 2008-11-10 at 11:01 +0900, Ben Caradoc-Davies wrote: > To better conform to ISO 19101 nomenclature, after discussions with Rob > Atkinson and others, I have renamed the GeoTools unsupported module > community-schemas to app-schema on trunk. This change resolves the > misleading complex/community-schemas naming tangle. > > Some significant changes: > > (1) Renamed classes ComplexDataStore* -> AppSchemaDataAccess*. > > (2) Renamed artifact gt-community-schemas-ds -> gt-app-schema. > > (3) Renamed containing module directory community-schemas -> app-schema. > > (4) Changed dbtype connection parameter from "complex" to "app-schema". > > The module app-schema now compiles and all unit tests pass. No > regression tests have been performed as GeoServer integration has not > been performed. > > Consider this software to be pre-alpha. > > More notes on the port can be found here: > https://www.seegrid.csiro.au/twiki/bin/view/Infosrvices/GeoserverPortToTrunk > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
