I would like to develop the IEEE2407 standard in parallel with the development of a F/OSS "reference implementation" of such standard, and with the target end users providing direct, constant, and valuable guidance to the development of both deliverables from the start.
What I propose below is definitively a new standards / system co-development model that IEEE might want to consider using IEEE2407 as a prototype.
Background:
* I am a big Free / Open Source Software proponent. GNU/Linux, Apache, MySQL, and many other software tools are currently available, source code included, at very low or no cost. F/OSS is highly relevant in LDCs and other resource-constrained settings (such as academic and medical institutions; NGOs; etc.).
* Experience has also taught me that the use of the F/OSS development methodology (free access to source code; all development conducted in the public eye; frequent releases; heavy end-user interaction) leads to much more robust, secure, and effective systems.
Proposed implementation:
* My ideal scenario would be for a team of global stakeholders (already
identified) to contribute to the development of the IEEE2407 standard.
* __In parallel__ with the above, a separate team of software developers will develop, under F/OSS methodologies, a "reference implementation" of a freely-downloadable system that implements the IEEE2407 standard.
* This "reference implementation" will be developed to allow end-users and other stakeholders (health workers; physicians; etc.) to actively "test-run" the reference implementation to make sure it (and the underlying IEEE2407 standard) meet the needs and requirements of the target end-users.
* Therefore, a new dynamic will take place: as the standard is developed, it will be implemented in the reference implementation, giving all stakeholders a say in the process. Stakeholders' feedback will then brought back into both the standards process as well as the reference implementation development. Loop endlessly.
Why doing this?
* Traditionally, standards are driven by vendors interested in promoting a chosen technology.
* The model proposed above will allow _stakeholders_ outside vendors to drive the standards-development process to better meet the stakeholders'
needs, not just those of vendors.
* This proposed model could lead to a virtuous circle: once the standard is ratified, a solid, free, 100% standard-compliant reference implementation is made available; and stakeholders embrace the standard because they were directly involved (and consulted) in the development of the standard. And service providers can immediately use the reference implementation to offer commercial services that are standards-compliant, with the knowledge that stakehodlers already approve of such standard.
References:
* F/OSS: Free and Open Source Software.
[http://en.wikipedia.org/wiki/Free/Open-Source_Software]
* LDCs: Less Developed Countries.
