W3C home > Mailing lists > Public > www-tag@w3.org > July 2014

Re: A proposal for revising the rules on TAG Participation

From: Marcos Caceres <w3c@marcosc.com>
Date: Thu, 17 Jul 2014 13:31:05 -0400
To: David Booth <david@dbooth.org>, Marc Fawzi <marc.fawzi@gmail.com>
Cc: Alex Russell <slightlyoff@google.com>, Charles McCathie Nevile <chaals@yandex-team.ru>, Tim Berners-Lee <timbl@w3.org>, "www-tag@w3.org" <www-tag@w3.org>, Noah Mendelsohn <nrm@arcanedomain.com>
Message-ID: <etPan.53c80859.327b23c6.1a94@Marcoss-MacBook-Pro.local>


On July 16, 2014 at 10:51:32 PM, Marc Fawzi (marc.fawzi@gmail.com) wrote:
> > Metaphor ping pong aside :) ... as a complete stranger to the  
> TAG "scene" can someone explain why MSFT wouldn't be happy to  
> simply counter Google's move and add another sponsored person  
> of their own to the TAG?

They can't just add people to the TAG. People are elected to the TAG so they are required to campaign as individuals to be elected. As I've explained, and as Alex has explained, there is no real motivation for corporations to join the TAG: the TAG has no real power (beyond the respect that the people on it have in the community). People join the TAG out of passion and time in an effort to try to convince others that they should be doing things in a particular way. But they cannot force anyone at the W3C to do anything because the TAG has no real power.

> Why couldn't Mozilla do that, too? There  
> is no universal +1 problem. Every vendor can afford to have another  
> employee dedicated to TAG. It's well within their means. I'm  
> just trying to understand why would anyone assume that Google  
> or some other vendor could have an unfair advantage?

They can't - because it would make no difference. As Charles explained, this view is overly simplistic (i.e., there are far more clever ways to play the standards game than simply stacking a group with people from a company). Even if you stack a working group, it doesn't actually achieve anything. W3C recommendations are just "recommendations" - and no one is forced to implement any recommendation. There are lots of recommendations the W3C makes that are ignored by the Web community (or are only used by a small group of organizations). 

> I say let Google have 10 or 15 people there. MSFT will do the same.  
> And Mozilla, too. I bet that they too could afford it if they had  
> to. And that would be good news for the TAG and the web. But the sad  
> news is that there aren't 15 people who are both talented enough  
> and can get along with each other. 

This is not true. The Web Apps Working Group is a massive group that works extremely well and pumps out most of the core web platform. The same with the WHATWG - that's a massive group that collaborates extremely well with its members (sometimes not so well with external groups). The RICG is another example of a large group of extremely talented individuals that work work effectively together.  

> If anything this discussion  
> demonstrates just that. So I think realistically if you allow  
> 2 per each vendor then each vendor will be happy to contribute  
> 2 and the web will be far happier for it.

I don't think it will change much, tbh. It just won't be as disruptive and will allow people to serve out their full term.  

> The important thing is to keep thinking about the deeper issue:  
> how the browser mark is not designed to scale (2-3 big vendors  
> and no one else with a major share) It's a classical monopoly market. 

Let's not open this can of worms. I'll just say that W3C members are free to standardize whatever they want (and they do!) - so the outputs of the W3C are not just targeted at browser vendors. 

> Don't worry about Google dominating MSFT via the TAG. They've  
> spent billions doing that and are doing that with the full force  
> of their resources. One more guy on the TAG is not a means to tip  
> the balance. It'd be like trying to lift an elephant with a tooth  
> pick as lever.

More elephants! Yay! :D 
Received on Thursday, 17 July 2014 17:31:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:57:03 UTC