Hi all,
I've just set up a page to discuss and move forward
the idea of versioning wfs, aka, cvs for spatial data.
The page is here:
http://docs.codehaus.org/display/GEOS/Versioning+WFS
Can anyone interested in the subject read it, and
then comment here on the ml? Or even, without reading it,
what do you expect from a versioning wfs?
Cheers
Andrea
Thanks Andrea, I will pass the link around.
Hi all,
I've just set up a page to discuss and move forward
the idea of versioning wfs, aka, cvs for spatial data.
The page is here:
http://docs.codehaus.org/display/GEOS/Versioning+WFSCan anyone interested in the subject read it, and
then comment here on the ml? Or even, without reading it,
what do you expect from a versioning wfs?
Comment without reading -- you must really want input.
Well for looking at it blind:
- I expect something similar to SVN
- although I would hope for a more transparent solution like oracle
- imagine the solution will not be out of the box but will require additional information (extra tables, extra columns, extra H2 database?)
- but that was technical - the real question is the process for conflict resolution (perhaps that issues list may come in handy)
Cheers
Andrea
I will visit the link and respond to your actual page later today.
Jody
Jody Garnett ha scritto:
Thanks Andrea, I will pass the link around.
Hi all,
I've just set up a page to discuss and move forward
the idea of versioning wfs, aka, cvs for spatial data.
The page is here:
http://docs.codehaus.org/display/GEOS/Versioning+WFSCan anyone interested in the subject read it, and
then comment here on the ml? Or even, without reading it,
what do you expect from a versioning wfs?
Comment without reading -- you must really want input.
Well for looking at it blind:
- I expect something similar to SVN
- although I would hope for a more transparent solution like oracle
Will try to have another look at the oracle docs
- imagine the solution will not be out of the box but will require additional information (extra tables, extra columns, extra H2 database?)
Was thinking along the line of "its own datastore", since I want version
tables to be updated in the same transaction without having to ask for
a distributed transaction manager (two phase commit).
Yet, the extra could really be handled as a sort of plugin for databases
so that at least it can be added to any jdbc data store. Not sure if we'll be able to make it really datastore agnostic thought...
- but that was technical - the real question is the process for conflict resolution (perhaps that issues list may come in handy)
Which issues list?
Cheers
Andrea