Re: Co-chair

I think that we can move to a standards-track group at any time. The main thing that we need to do is to submit a charter, first to W3C management and then to the AC list. Dan has a draft charter, I think, that can serve as a template. Once we agree on the content, we submit it, handle any comments we get, and we're in business. 

Jim

________________________________

From: Young, Milan <Milan.Young@nuance.com> 
To: Glen Shires <gshires@google.com>; Jerry Carter <jerry@jerrycarter.org>; Ian Jacobs <ij@w3.org> (ij@w3.org) <ij@w3.org>; Doug Schepers (schepers@w3.org) <schepers@w3.org> 
Cc: olli@pettay.fi <olli@pettay.fi>; Jim Barnett; bringert@google.com <bringert@google.com>; satish@google.com <satish@google.com>; raj@openstream.com <raj@openstream.com>; dahl@conversational-technologies.com <dahl@conversational-technologies.com>; public-speech-api@w3.org <public-speech-api@w3.org> 
Sent: Wed Jun 13 16:38:19 2012
Subject: RE: Co-chair 



Taking a step back, we’re in a situation where a Google representative decides when consensus is reached, and if we lack consensus we default to whatever Google wanted earlier.  Do the folks in this community feel this is a path to building a spec that has the broad-based support needed to attract missing browser and speech vendors?

 

I’d also like to call out an recent instance where consensus was reached, but the agreed changes did not make their way into the spec.  This happened near the end of the EMMA thread where Satish, Deborah, and I finally agreed to drop the requirement for EMMA attributes in exchange for adding use cases [1].  But when the changes were pushed through, they were missing the compromise text [2].  And my notification to this problem didn’t generate any response from the chair or editors [3].  This is especially worrisome given that we just published our first draft (sans compromise text) without any advanced notification, vote, or opportunity for review [4].  Perhaps this is simply a case of broken timeline expectations, but given that my requests have fallen off the proverbial radar several times before (most recently [5]), it feels like a bias is at play.

 

I would like to hear from others in the community on this topic.  I’m particularly interested to know thoughts around the formation of an official WG where we can produce a standards-track specification.

 

Thanks

 

[1] http://lists.w3.org/Archives/Public/public-speech-api/2012Jun/0060.html


[2] http://lists.w3.org/Archives/Public/public-speech-api/2012Jun/0061.html <http://lists.w3.org/Archives/Public/public-speech-api/2012Jun/0061.html> 

[3] http://lists.w3.org/Archives/Public/public-speech-api/2012Jun/0062.html <http://lists.w3.org/Archives/Public/public-speech-api/2012Jun/0062.html> 

[4] http://lists.w3.org/Archives/Public/public-speech-api/2012Jun/0076.html


[5] http://lists.w3.org/Archives/Public/public-speech-api/2012Jun/0010.html <http://lists.w3.org/Archives/Public/public-speech-api/2012Jun/0010.html> 

 

 

From: Glen Shires [mailto:gshires@google.com] 
Sent: Wednesday, June 13, 2012 8:02 AM
To: Jerry Carter
Cc: Young, Milan; olli@pettay.fi; Jim Barnett; bringert@google.com; satish@google.com; raj@openstream.com; dahl@conversational-technologies.com; public-speech-api@w3.org
Subject: Re: Co-chair

 

Changes to the spec and to the structure of this CG are decided by rough consensus. There is no clear consensus on the co-chair proposal, so there will be no changes in the structure of this CG at this time.

 

Glen Shires