The WFSHarvester is now an Open Source project on SourceForge.
Project website: http://wfsharvester.sourceforge.net
SourceForge site: http://sourceforge.net/projects/wfsharvester
There is not a lot to find though. At this moment I am adding comments to the source files, cleaning up some stuff, writing a few lines of documentation. When this is done I will put it in the SourceForge.
After that I will create some sample files and a simple client for testing.
Because the WFS Harvester is so simple and might be useful for other organisations as well I’ve decided to create an Open Source project. Apart from making the harvester available to other people, I also hope someone might improve it 
For a project it is necessary to harvest data from several distributed WFS’s and put the data in a central WFS. A simple and configurable WFS Harvester is developed to perform this task. Because a few easy to configure configuration files are used it can be used relatively easy for different WFS’s.
The WFS Harvester requires 4 parameters:
1. XML file
2. URL of WFS
3. URL of WFS-T (Transactional WFS)
4. XSL file
The XML file contains a GetFeature request. This request is sent to a WFS. The XML result of this request is transformed into a Transaction request using the XSL file. This transaction request is then sent to the WFS-T.
Of course it could be improved by requesting for the capabilities of a WFS and so on, but now it’s an easy simple library. The XSL file allows for example to copy WFS data from one datamodel into different datamodel and store it in another WFS.
Yesterday I worked with my colleague Martijn on making openstreetmap data available through a WFS. First he put the data in a PostGIS database (see the post on his blog). After that it was quite easy to make the data available in Deegree WFS.
It appeared the import tool om OSM did not add primary keys, so they were made by adding a serial type column to all OSM tables and making it the primary key.
After running a java tool to create the Deegree WFS datastore XML for OSM and adding some lines to make the OSM features visible and queryable the Deegree WFS was up and running.
So now we have a WFS 1.1 service supplying OSM data in GML 3.1.1 format.
Nice result in a few hours, but I still want to do some things, namely:
- Change the default app namespace into an osm namespace. Actually this is done in 5 seconds…
- Try to output GML SF. The OSM tables are very simple and flat, so SF should be more than enough.
In 2007 the state secretary (deputy minister) Heemskerk launched an actionplan to improve interoperability between and inside governmental organisations using Open Standards and Open Source.
On march 3th the first action was presented: a first version of a list containing the open standards Dutch government organisations should use or support. The list can be downloaded here: http://www.forumstandaardisatie.nl/fileadmin/OVOS/Basislijst_OS1.pdf
Apart from several national standards some of the choices are:
Regarding GDI it is proposed to use the “Framework van standaarden voor de Nederlandse GII”, version 2.0 as defined by Geonovum.