Take as an example the W3C's XHTML specification. Under the auspices of the W3C, member organizations collaborate to draft, test, refine, and release the detailed technical definition of the XHTML technology. Acting as individual organizations, these members implement software that leverage, for commercial and non-commercial purposes, the specification developed by the standards body. It would be, however, very unlikely for the W3C to actually develop a web browser or web server that implemented XHTML in software.
Many standards bodies, like SIFA and the W3C, publish their works openly. Any organization or individual, including Open Source projects, may benefit by deciphering, adopting, and implementing the standards, regardless of membership status, and without paying licensing fees to the standards body. Other standards bodies, in contrast, choose to sell their work using fee-based licenses. Although SIFA is not an Open Source initiative, the open publication of its standards is certainly an enabler for industrious Open Source developers.
SIFA, its members, and the wider world of educational technology would greatly benefit from additional documentation to fill the void between the SIF specifications and their implementation in software. To that end, one of the purposes of this blog is to share some of my practical experience with SIF. I would like to take this opportunity to encourage SIFA to work towards providing more developer-centric documentation, including code samples, as part of its work. Since SIF's core technologies (XML and HTTP) are ubiquitous, basic code samples could be developed for every modern programming language and platform. The results of such work would be clarity for a wider audience of developers in the school market, the demystification of SIF, and, ultimately, wider adoption.
I would also encourage individuals and groups developing Open Source SIF software to become involved in the Association. Involvement will greatly accelerate your efforts in building good software that solves schools’ interoperability and data management needs.