The current User Manual section on Versioning is at: *[GEOSDOC:6 Versioning]*
This area represents the work done to implement 'versioning' in WFS, that is how to keep track of changes to data in GeoServer, leveraging the WFS-T standard. The current state is that a first working server version is complete. See the notes on Trying out the early WFS-V prototype, to download and set it up yourself, or visit http://sigma.openplans.org:8080/v-geoserver and walk through the demo requests to see it in action.
Though we have a fully working server, there is still quite a lot of work to do. The versioning module is integrated with GeoServer trunk, and we should have some sort of release with GeoServer 1.6.0-beta1. We're working on implementing a client that offers access to the versioning operations. Currently OpenLayers is the leading candidate, though we hope to encourage many different implementations. Working with a client should help shape the protocol, refining it even more.
Past just establishing the basics, we hope to do a lot more work on more options like GeoRSS and email notifications about transactions and more granular security. We've got a new security framework on trunk, we just need to start exercising and integrating it more. We also want to make it easier for groups to select licenses, as well as explore advanced features like branches, and hooking up our validation engine.
The document is quite long, so it has been split into subpages:
- Requirements specification
- Versioning approaches classification
- Analysis of existing implementations
- Implementations and proposals
- Trying out the early WFS-V prototype
- GeoGit approach
A R&D notes page is available that stores notes about alternative ways we could implement versioning based on the feedback we gathered so far on WFS-V users