Jan Willem Broekema

Implement but don't tell anyone.

The wish of Dutch Parliament to enforce the use of open standards and to promote the use of open source software (2002) is still under development. The present-day programme NOiV (Netherlands Open in Connection) is very active on the communication side, with many great examples but few if any that the programme itself started, financed or supported. There are quite a few governmental projects that have been hailed but in the end failed, for obscure reasons. Could it be that being in the spotlight attracts too much attention?

What happens if you start a programme but do not tell it is open sourced (or open standarded)? Is that helpful or does it hurt the 'good cause'? Will it help you getting the assignment or not? Should the organisation that hires you know? And how do you introduce an open license model during procurement? I am looking forward to an active discussion.


Jan Willem Broekema worked in many roles on the user-side of new technology (sales, marketing, product management, training, consulting). He was manager of the programme Open Standards and Open Source Software (OSOSS) and secretary for the national Forum on Standardisation in the period late 2005-early 2008. Right now he is advisor of governmental bodies on information strategy, working for RedNose Consulting.

Read more about Jan Willem Broekema