> > However, this does bring to light a potential issue: is there a single > orthodox FeatureModel<->XML encoding in the code base? We may have to > factor that out so that we can have a GML2 plugin coexist with a GML3.1.1 > plugin, coexisting with a 19139 plugin, coexisting with custom schema > encoding plugin (ala 19118). > Indeed. This is a very important aspect of being able to encode features in both gml2 and gml3. Not so much dates, but the gml schema geometry bindings are different. So the mapping from our jts geometry classes to gml schema types must be abstracted out.
> Bryce > ------------------------------------------------------------------------- > 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 > Geotools-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geotools-devel > > !DSPAM:1004,45edfb0a111881702038478! > -- Justin Deoliveira The Open Planning Project http://topp.openplans.org ------------------------------------------------------------------------- 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 Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
