3 ms·
As its name hints the Consortium is intended as a way for organisations to work together. This seemed like a natural fit for the Web which had all these excitin
by tialaramex 7y ago
As its name hints the Consortium is intended as a way for organisations to work together. This seemed like a natural fit for the Web which had all these exciting startups in the Valley and around the world. If you look at something like the IETF where notionally all participation is individual and organisations are acknowledged only as the employer of an individual contributor you see plenty of stuff getting done that is blatantly, even explicitly, done on behalf of that employer. So why not cut out the middle man?
But it turns out that's probably the wrong shape. While some stuff at IETF would get done by "any Google employee" or "any Microsoft employee" or "any Cisco employee" plenty of stuff that actually gets done is because one or more specific people cared about it, regardless of their employer or occasionally even if they don't have one.
For years it was literally impossible to work on W3C standards as an individual. They eventually fixed that, but the message sent echoes forever, "Go away, we don't care".
I like Tim (he is a nerd, he used to derail our apparently serious board-level meetings with his IT problems), but my impression is that one of the things that lead to the W3C was that Tim could see from pretty early on (certainly by the time W3C is founded) that there's a lot of cash sloshing about for his Web, and of course it's the nature of the beast that Tim doesn't automatically get a slice. That's part of the reason other systems didn't get traction - nobody wants to pay a toll. The W3C is a way for Tim to get some of that money for his pet projects.