The goal of is the discussion is to think about whether we can improve the setting. It’s because this is so important that I want to focus on it.

For example, can we encourage more openness and transparency in the creation of web standards? We’ve proved that openness and transparency work well for code: they encourage discussions to focus on technical merit; they allow everyone who is interested to understand the details; they encourage participation. Why not do this with the creation of web standards?

Similarly, can we create a good means of input for both the “implementors” (in our case, the browser and other software vendors) and the web developers in the standards creation process? Browser makers and web developers are two sides of the same coin — both are needed to have a high quality, interoperable web. And each group can make life miserable for the other.

Are there ways we can improve communication between browser makers and web developers during the creation of a web standard? Not afterward, when the standard is done. Communication at that time makes web developers “consumers” of the standard, not participants in its development.

The earlier post and perhaps a few more are intended to develop a context for this sort of discussion and then action. We can jump into the discussion immediately, but it’s often useful to have shared vocabulary and framework.