- From: Dan Burnett <dburnett@voxeo.com>
- Date: Thu, 25 Aug 2011 15:39:09 -0400
- To: public-xg-htmlspeech@w3.org
Group, The Web API summary minutes from today's call are available at http://www.w3.org/2011/08/25-htmlspeech-minutes.html. For convenience, a text version is embedded below. Michael Bodell took the notes. -- dan ********************************************************************************** HTML Speech Web API discussion 25 Aug 2011 [2]Agenda [2] http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Aug/0028.html See also: [3]IRC log [3] http://www.w3.org/2011/08/25-htmlspeech-irc Attendees Present Olli_Pettay, Dan_Burnett, Michael_Bodell, Robert_Brown, Bjorn_Bringert, Debbie_Dahl, Glen_Shires, Charles_Hemphill, Milan_Young, Satish_Sampath Regrets Chair Michael_Bodell Scribe Michael_Bodell Contents * [4]Topics * [5]Summary of Action Items _________________________________________________________ <burn> Scribe: Michael_Bodell <burn> ScribeNick: mbodell discuss [6]http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Aug/ att-0030/speechwepapi.html [6] http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Aug/att-0030/speechwepapi.html <burn> Date: 25 August 2011 changes to section 3: remove bind and unbind changes to section 3: add a method to createSpeech[Input|Output]Request on the SpeechRequest interface issues to section 4: query needs to be async issues to section 4: need a function to return the service based on the URI for the service issues to section 4: need a way to do authorization, possibly as a name/password options in query options, possibly as authorization for an authorization header, possibly just as proprietary stuff on the URI changes to section 3: change the type enum to be a bitfield so TTS is 1, ASR is 2, and don't need TTSASR if you have TTS | ASR issue to section 3: remove the state <Milan> Sorry folks, I have to drop early today. changes to section 4: need Query to be more specific if this is on Window issue to section 4: maybe have constructor and set things? changes to section 4: add successCallBack and failureCallBack to the specific speechQuery function changes to section 4: merge filter and options (the criteria is in the option, probably as a flat list) changes to section 4: filter on required languages and required service type and possibly other things... changes to section 4: possible filter on audio codecs as well <Robert> I don't think you'll ever get browsers to implement SDP for anyhting other than peer-to-peer voip calls <Robert> I'm having network problems.. audio keeps dropping out possible issue to 3: we can have multiple of these, should state that, they go away with garbage collection, only issue is how long does the service stay open after a query, do we need some explicit close/reattach (bind/unbind) or do we just not care... changes to section 5: possible remove form attribute or control... possibly not since this really does tie it to the element properly <burn> on the last issue in 3, above, we decided that we currently believe that we do not need to specify whether the web service connection needs to remain open for a speech service. changes to section 5: Need better definition of "recoable elements", probably listing all such elements section 5: htmlFor is definitely fine, later discussion sounds like control is fine too issue to section 5: need some sentence about security model, but that probably ties to request object and not the reco element issue on section 3 or 4: possibly need a way to check if you have permission to do recognition, method on Service (or on Query?) issue on section 5: Need a way to get at the SpeechRequest associated with the reco element issue on section 5: have a SpeechInputRequest attribute of reco that is the tied request... this could have the default UA service or a service based on URI attribute. From scripting if you get a new SIR you can set the attribute to associate the new SIR with this reco element <satish> Have to leave now, see you next week. issue on section 6: same kind of idea with section 5, with a SpeechOutputRequest instead of SpeechInputRequest issue for section 6 (and generally): Link to the definitions in HTML 5 (for HTMLMediaElement, but also for "potentially playing", etc.) possible issue for section 6: think about CSS audio last call and if it effects section 6 <Charles> Last Call: CSS Speech Module: [7]http://www.w3.org/News/2011.html#entry-9181 [7] http://www.w3.org/News/2011.html#entry-9181 issue with section 7: missing the actual recognize() function issue with section 7: need an attribute to associate the Service on the SIR (probably read only) changes to section 7: for the method need start, stop, cancel Recognition() issue for section 7: possibly better to call stop, finish, in terms of naming issues for section 7: maybe need some sort of grammar object (better for caching, and don't need DOM string) issue for section 7: need some text that describes what happens if someone sets some of these in recognition and some of these not issue for section 8: have language in the SpeechOutputRequest
Received on Thursday, 25 August 2011 19:39:53 UTC