The phrase ‘open standards’ is widely used but not well understood, to the point that the Open Source Initiative calls it “a feel-good term with no actual technical meaning.”
As we’ll see, that’s an overstatement, but there is still significant confusion about and differences in what ‘open standard’ means in practice. Let’s take a look at what openness in standards is, with a focus on whether and how it helps to legitimize the design and maintenance of the Internet.
Defining open standards
First, let’s review what some governments think open means in the context of standards. The phrase comes up in several legal documents, mostly focused on government procurement and trade.
In the US, OMB Circular A-119 fills that role and is also referenced in some aspects of competition law. It says openness in standards means:
The procedures or processes used are open to interested parties. Such parties are provided meaningful opportunities to participate in standards development on a non-discriminatory basis. The procedures or processes for participating in standards development and for developing the standard are transparent.
OMB Circular A-119 (PDF)
The corresponding document in Europe is Regulation 1025/2012, which says a standard is open when:
the technical specifications were developed on the basis of open decision-making accessible to all interested parties in the market or markets affected by those technical specifications […]
Regulation 1025/2012
In both cases, openness refers to the process used to produce a standard — it needs to be open to all potentially interested parties. Note that these definitions don’t say anything about the decision-making process itself, just access to it.
In contrast, the UK Government’s Open Standards Principles focuses on availability in its definition of open standards:
Open standards give users permission to copy, distribute and use technology freely or at low cost.
Open Standards Principles
In practice, these views don’t really conflict. The procurement guidance from the US and EU also talks about availability, and the UK guidelines cover ‘fair and transparent processes’. They do, however, use ‘open standard’ to mean different things, which can cause confusion.
There are plenty more examples from legislation around the world that also touch on these two themes. Perhaps pragmatically, the Internet Society avoids conflict and defines them as having both attributes:
Open standards are publicly available and developed via processes that are transparent and open to broad participation. In contrast, proprietary standards are privately owned by one or more entities that control their distribution and access.
Policy Brief: Open Internet Standards
But what do these things actually mean in practice for Internet standards?
1. Availability as openness
Let’s start with availability, which begs the question — for what purpose? The UK definition lists ‘copy, distribute, and use’, and I’d add another — permission to change the standard.
The first sense of a standard’s availability is straightforward: What do you need to do to get a copy of it, and can you give it to other people? This isn’t a small thing; many standards bodies charge for their products, and substantial fees can be a barrier not only to implementation but also to independent review. Thankfully, it’s long been a norm that Internet and web standards are free to obtain over the Internet itself, and can be freely distributed.
Second, there’s the question of availability in the sense of implementing open standards — namely, do you need to license any patents to do so? The intricacies of patents in the IETF and W3C have some interesting properties, but that’s a topic that’s too big to cover here. Suffice it to say that both have measures in place to discourage ‘submarine’ patents from those who participate in the standards process.
With those meanings covered, let’s consider the ability to modify an Internet standard. If you want to publish a derivative of an IETF RFC or W3C Recommendation, you’ll need to get permission, because both organizations retain copyright in their works, using very different mechanisms.
In the IETF, the original authors of the RFC retain copyright, giving a license to the IETF Trust to allow it to be published. In theory, that allows the authors to publish a derivative work on their own or give someone else a license to do so. In practice, this doesn’t happen, because most RFCs are collaborations between much larger groups than just the authors, and getting sufficient permission sorted out is impractical. Recently, there was a proposal to allow modification of IETF RFCs, but that seems to have caused enough discomfort in the community to make its adoption unlikely.
W3C, meanwhile, requires authors to transfer copyright to the Consortium. By default, its document license also doesn’t allow modifications, much like the IETF. Interestingly, however, some W3C documents have been published under a more permissive license that does allow ‘forking’ the specification. Most famously, this was used to shift the HTML specification out of the W3C’s hands and into the WHATWG.
How, though, does the ability to modify a standard impact its openness?
Think of copyright as a centralizing force. The entity that controls the definition of the standard controls its future, because they have a monopoly on it. As I’ve written before, centralization can be used for good — especially if it’s to encourage interoperability, and even more so if it’s used to gate-keep in the interest of the common good with appropriate governance. When a standards body is well-run, responsive to the community using its work, and financially healthy, I’d argue it’s probably filling this role well.
If it isn’t one or more of these things, however, that monopoly becomes a liability. For example, if the standards body is captured by malevolent interests or simply loses financial viability, it can put its community of users in an awkward position indeed. Even without those extreme circumstances, locking a standard into one venue creates a moral hazard — the standard will remain not because that venue is the best steward for it, but because it controls the copyright.
2. Openness of standards processes
The other senses of ‘openness’ in standards pertains to the process used to produce them. How open a process is perceived to be can result in the Standards Development Organization’s (SDO’s) legitimacy — and its monopoly over the standard — being either bolstered or questioned.
On the face of it, the mechanism is straightforward. A standards process that is ‘accessible to all interested parties’ enhances input legitimacy by including more diverse views into the work. However, it’s important to inspect some assumptions that are commonly made about the impact of this kind of openness.
First, just because someone has the theoretical ability to participate, it doesn’t mean that they actually can. Standards work has a notoriously steep learning curve. Being effective requires great technical expertise, significant time, and frequent international travel to build influence, relationships and understanding. Yes, SDOs use online tools like mailing lists, videoconferencing, and GitHub to allow remote participation, but they are a poor substitute for face-to-face interaction, hallway discussions and sharing a meal (and, often, a drink). And, even people who follow Internet standards full-time aren’t aware of every development in every specification, because there’s simply too much going on.
Together, this means that the number of people actually paying attention to a particular standard development can be quite small unless it captures the broader imagination. It also means that only those with sufficient incentive to invest resources will participate in a long-term effort.
Second, even those who show up might not have influence over the outcome. While standards decisions might be based upon consensus, there are many pitfalls in its application, and the combination of a large body of standards work and few experts (per above) often means that a small group of specialized experts ‘owns’ each established area of interest, acting as gatekeepers to change. If you have an ‘outsider’ idea that is counter to the thinking of those experts, you’re unlikely to get it successfully adopted.
Third, standards bodies are not and fundamentally cannot be representative, in a democratic sense. They are not accountable to an electorate, there are no demos, and thus they have no meaningful authority based upon whoever does show up. At most, openness creates a presumption that those with the knowledge, resources, interest, and dedication have the opportunity to show up.
In combination, these factors constrain the input legitimacy gained by openness so much as to make it negligible. In practice, standards organizations derive most of their legitimacy from throughput (such as checks and balances in their processes) and output (the success of what they actually produce).
That’s not to minimize the importance of diversity and external engagement in SDOs. Efforts to both onboard new people into these cultures and to reach out to those affected by their work are critical, in my opinion (so much so that I wrote a whole RFC about it). However, standards bodies should never consider themselves to have democratic legitimacy, think that mere openness is enough to justify a decision, or that their processes don’t require regular scrutiny and improvement.
An aside on the ‘M’ word
A word that often comes up in conjunction with ‘open standards’ is ‘multistakeholder.’
This Rorschach test of a word has bugged me for a while — it means so many things to so many people. So much, in fact, that I recently went to a conference on multistakeholderism in Internet governance to delve into why this term is so often used but so rarely defined.
My suspicions were confirmed. This is a word that means very little, except when you use it in the context of its opposite: multilateral governance (for example, through the United Nations). Really, multistakeholder just means not multilateral.
In particular, being characterized as a multistakeholder does not imply that there are specific classes of ‘stakeholders’, or that they have specific rights or representation in the process. So while Internet standards are multistakeholder in the sense that they’re not government-led, that says nothing about their nature beyond that fact.
If this topic is interesting to you, I highly recommend reading the transcript of Milton Mueller’s keynote from that conference.
Necessary, but insufficient
All of this leads to the conclusion that openness of process is clearly necessary to legitimize the work of SDOs and help ensure that anti-competitive behaviour doesn’t arise. However, it isn’t sufficient to assure good governance.
Furthermore, it’s reasonable to say that standards bodies that choose to keep a monopoly on the specifications themselves (thereby withholding that dimension of openness) necessarily subject themselves to increased scrutiny regarding the quality of their governance. What good governance looks like in Internet standards is a theme that I’ll return to.
Mark Nottingham has contributed to the development and maintenance of the Internet and web for more than 20 years. He’s written, edited, or substantially contributed to more than thirty IETF RFCs and W3C Recommendations about topics like HTTP, caching, linking, web architecture, privacy and security. He currently Chairs the IETF’s HTTP Working Group.
Originally published on Mark’s blog as part of a series, The Nature of Internet Standards.
The views expressed by the authors of this blog are their own and do not necessarily reflect the views of APNIC. Please note a Code of Conduct applies to this blog.