Adjust to Comments from GeoAPI
------------------------------
Key: GEOS-565
URL: http://jira.codehaus.org/browse/GEOS-565
Project: GeoServer
Type: Sub-task
Reporter: Jody Garnett
Assigned to: Jody Garnett
We have the community schema "complex feature" proposal ported into geoapi pending.
That is the good news.
The other good news is that the community (especially bryce) has been poking holes in it for us.
As a result the current "feature model" is much more object oriented in its approach, the structures that form tree is XML (choice, all, sequence) are explciitly typed. In order to maintain XPathness we do mark some types (say a repeating sequence of elements) so that the XPath implementation (JXPath) can skip over them.
The result is a strong binding to an object model for those who like their coffee straight, while still allowing us to get the job done.
All that and it is less code (& ideas) to worry about.
The bad news is I have yet to bring the names in line with what Bryce wants.
TODO:
- sync up with naming improvements (isolated problem to AttributeName)
- match names for core concepts (Record, Property, Attribute, Opperation, Association)
- support opperations at the api level (for GridCoverage)
I would like to do this for phase 2 once the existing work has be resuced to trunk. A big old day with a refactoring tool should do it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira