Open Network Foundation to Promote New Network Architecture
![](https://www.consortiuminfo.org/wp-content/uploads/2019/11/OpenFlow.jpg)
What’s happening in the world of consortia, standards,
and open source software
The Standards Blog tracks and explains the way standards and open source software impact business, society, and the future. This site is hosted by Gesmer Updegrove LLP, a technology law firm based in Boston, Massachusetts, USA. GU is an internationally recognized leader in creating and representing the organizations that create and promote standards and open source software. The opinions expressed in The Standards Blog are those of the authors alone, and not necessarily those of GU. Please see the Terms of Use and Privacy Policy for this site, which appear here. You can find a summary of our services here. To learn how GU can help you, contact: Andrew Updegrove
Have you discovered The Alexandria Project?
As I noted last week, the British government recently came out strongly in favor of royalty free standards and active consideration of open source software in public procurement. As expected, this decision was greeted with less than universal enthusiasm. One trade group that predictably reacted negatively was the Business Software Alliance, an association that supports the robust preservation of rights in patents. The BSA had previously lobbied actively (and successfully) to delete a similar position from the new version of the European Interoperability Framework (EIF).
The U.K. has become the latest country to conclude that for information and communications technology (ICT) procurement purposes, “open standards” means “royalty free standards.” While apparently falling short of a legal requirement, a Cabinet Office Procurement Policy Note recommends that all departments, agencies, non-departmental bodies and “any other bodies for which they are responsible” should specify open standards in their procurement activities, unless there are “clear business reasons why this is inappropriate.”
For some time now, I have been meaning to write a series of blog posts setting forth my views on best practices in forming and governing open source foundations. Why? Because despite the increasing reliance of just about every part of our modern world (government, finance, defense, and so on) on open source software (OSS) and Free and Open Source Software (FOSS), there has been very little written on the subject.
That means that neither a community nor a corporation has much to refer to in creating the kind of governance structure most likely to ensure that the intentions of the founders are carried out, that the rights of contributors are respected, and that the code upon which end users will rely is properly maintained into the future.
The following is the introduction to the Feature Article in the most recent issue of Standards Today, the free "eJournal of News, Ideas and Analysis" that I have been writing for the last seven years. You can read the entire article here, and sign up for a free subscription here.
For more than 100 years, the United States has been the exemplar of the "bottom up" model of standards development. Under this methodology, society relies on the private sector to identify standards-related needs and opportunities in most sectors, and then develops responsive specifications. Government, for its part, retains ultimate control over domains such as health, safety, and environmental protection, but preferentially uses private sector standards in procurement, and also references private sector standards into law when appropriate (e.g., as building codes).
Until recently, government agencies in the United States commonly developed their own standards for procurement purposes. This era of separate but equal standards creation officially came to an end with the passage of the National Technology Transfer and Advancement Act of 1995. With this legislation, Congress directed government agencies to use "voluntary consensus standards" (VCSs) and other private sector specifications wherever practical rather than "government unique standards," and to participate in the development of these standards as well. In 1998, Office of Management and Budget Circular A-119 was amended to provide additional guidance to the Federal agencies on complying with the NTTAA.
Over the last few months, I've frequently pointed out the vulnerability of important open source projects that are supported and controlled by corporate sponsors, rather than hosted by independent foundations funded by corporate sponsors. One of the examples I've given is SUSE Linux, which has been hosted and primarily supported by Novell since that company acquired SuSE Linux AG in 2003. Novell, as you know, is expected to be acquired by a company called Attachmate a few weeks from now, assuming approval of the transaction by the Novell stockholders and by German competition regulators.
Recently, the future of the SUSE Linux Project (as compared to the Novell commercial Linux distribution based on the work of that project) has become rather murky, as reported by Pamela Jones, at Groklaw. Apparently, Novell is facilitating some sort of spin out of the Project, which is good but peculiar news.
The pace of technology is wondrous indeed. No corner of our lives seems safe from digital invasion, from picture frames to pasta makers. For years now, we have been threatened with Internet-enabled refrigerators, and perhaps 2011 will see it so.
Nor is the process likely to stop there. Soon, we are told, our homes will become infested by "mesh networks" of sensors, each one whispering information surreptitiously to its neighbor, in order to render our lives more energy efficient. But in so doing, they will observe our every move and report it to heavens knows whom.
Have you discovered The Alexandria Project?