Page:<http://docs.codehaus.org/display/GEOTOOLS/Feature+Model+Proposal>
UML:<http://docs.codehaus.org/download/attachments/30791/featuremodel.gif>
Javadocs:<http://lists.refractions.net/geotools/geoapi/proposal>
I will bounce this idea off the members of GeoServer community that in
town later this week.
Changes were to change Node to AttributeDescriptor (Justin though
declaration may be more appropriate)? Schema has been broken out into
top level classes - consider renaming "Schema" to Descriptor or
Declaration as suites? I still find "Schema" appropriate - but not
enough to belabor the point.
Complex renamed to ComplexAttribute, a change for the better - thanks
for the suggestion.
Restriction replaced with Filter (as one declarative set membership
thing is enough for any API).
And finally GenericName replaced with QName (cleaning up a lot of code).
For those worried about these changes (as expressed in IRC today), there
are two more steps I want to see passed. The use of XPath against this
model, and support for Gabriels complex content (as listed on his
project requirements).
IRC also touched into several other lacks, Geometry and Metadata. These
are separate subjects - we can run this design ontop of JTS and without
metadata as needed.
Jody
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Geotools-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
