The existing naming convention sort-of-works for now. I do not think we
will get the various GML encoding issues fixed until after FOSS4G. This
is in my view too long to block a release, which is also holding up a
GeoServer release. These problems mainly affect app-schema.
I am comfortable maki
Hi Rob:
There are two ideas on the floor:
- using the Attribute property map to hide away additional information
- breaking out a ComplexType that has by convention an attribute
called "value" that is the simple type being extended
I would like to confirm that the convention idea will hold Ben
I dont know where Ben got to, but there is _already_ an implementation
for this extension for simple feature types - I need to extend this
ability to map to ComplexAttrImpl to complex types, including GML
types normally bound directly to JTS implementations...
Rob
On Mon, Sep 14, 2009 at 11:26 PM
Hi Ben:
Just a quick sanity check - we were talking about how to encode a
complex extension to a simple type; and discovered that the api was
not complete enough to capture that right now.
Are you able to get by with a naming convention for this release?
Jody
---
