Hi all,
I've updated the GSIP 14 page (http://docs.codehaus.org/display/GEOS/GSIP+14+-+WFS+Transaction+handling+framework)
wtih some improved wording, and incorporated Jody feedback about using a CodeList instead of a list of integers for the event types.
When asked for feedback only Jody publicly responded (thought I had private positive feedback from Justin too).
Now, I'd call for a vote (PSC members only), but if you have some feedback now, please speak up anyways.
Here is my +1
Cheers
Andrea
I dont see where to vote on the page, but +1 anyway - it looks well thought out.
Just make sure the implementation is GeoAPI, ISO FeatureModel ready so it doesnt become another hurdle in making geoserver behave sensible for non-trivial geometries.
Rob A
Andrea Aime wrote:
Hi all,
I've updated the GSIP 14 page (http://docs.codehaus.org/display/GEOS/GSIP+14+-+WFS+Transaction+handling+framework)
wtih some improved wording, and incorporated Jody feedback about using a CodeList instead of a list of integers for the event types.
When asked for feedback only Jody publicly responded (thought I had private positive feedback from Justin too).
Now, I'd call for a vote (PSC members only), but if you have some feedback now, please speak up anyways.
Here is my +1
Cheers
Andrea
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Rob Atkinson ha scritto:
I dont see where to vote on the page, but +1 anyway - it looks well thought out.
Ah, sorry, the vote section wasn't there. Added one, and your vote too.
Just make sure the implementation is GeoAPI, ISO FeatureModel ready so it doesnt become another hurdle in making geoserver behave sensible for non-trivial geometries.
Well, the API depends on feature collection and feature store, so changing them will require some adaptation on client code, but that's
inevitable and will hit the rest of Geoserver much harder.
It seems to me changing the feature module won't affect this just like
the rest. If you have suggestions I'm all ears 
Cheers
Andrea
Added my vote to the page; I do not see a Jira task associated with this one yet ... ? Is that an oversight ... or is it created after the proposal is passed?
Nice proposal BTW; good work
Jody
Hi all,
I've updated the GSIP 14 page (http://docs.codehaus.org/display/GEOS/GSIP+14+-+WFS+Transaction+handling+framework)
wtih some improved wording, and incorporated Jody feedback about using a CodeList instead of a list of integers for the event types.
When asked for feedback only Jody publicly responded (thought I had private positive feedback from Justin too).
Now, I'd call for a vote (PSC members only), but if you have some feedback now, please speak up anyways.
Here is my +1
Cheers
Andrea
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Jody Garnett ha scritto:
Added my vote to the page; I do not see a Jira task associated with this one yet ... ? Is that an oversight ... or is it created after the proposal is passed?
Thanks for the vote. About the Jira, I just added it.
Cheers
Andrea
It seemt somehow I can't vote on the page directly.
+1 here
Gabriel
On Wednesday 02 May 2007 15:12, Andrea Aime wrote:
Rob Atkinson ha scritto:
> I dont see where to vote on the page, but +1 anyway - it looks well
> thought out.
Ah, sorry, the vote section wasn't there. Added one, and your vote too.
> Just make sure the implementation is GeoAPI, ISO FeatureModel ready so
> it doesnt become another hurdle in making geoserver behave sensible for
> non-trivial geometries.
Well, the API depends on feature collection and feature store, so
changing them will require some adaptation on client code, but that's
inevitable and will hit the rest of Geoserver much harder.
It seems to me changing the feature module won't affect this just like
the rest. If you have suggestions I'm all ears
Cheers
Andrea
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Gabriel Roldán ha scritto:
It seemt somehow I can't vote on the page directly.
+1 here
Justin, another developer without confluence access it seems.
Cheers
Andrea
Gabriel Roldán ha scritto:
It seemt somehow I can't vote on the page directly.
+1 here
And oh, btw, vote added
Cheers
Andrea