How about an agreement that only one vendor should create a prefix on a feature? So, they create say "-webkit-feature", and can innovate there. Once another ven

How about an agreement that only one vendor should create a prefix on a feature? So, they create say "-webkit-feature", and can innovate there. Once another vendor wants to implement it, they co-operate with the original vendor and interested parties and get a standard together, which everyone can then implement as "feature". It's ridiculous at the moment when you have -o-feature, -moz-feature, -webkit-feature, -ms-feature, and feature, which take 2, 3, 4, or even 5 different syntaxes. W3C considers two implementations sufficient for standardisation, which this process gives. I'd also have an automatic process for moving any vendor prefixed feature into being the standard after they have had it stable for 6 months, other implementations or no. A more predictable timescale would make these "experimental" features more realistically experimental and encourage standardisation.