W3C

- DRAFT -

HTML Speech Incubator Group Teleconference

08 Sep 2011

See also: IRC log

Attendees

Present
Michael_Bodell, +40.33.281.aaaa, Debbie_Dahl, Olli_Pettay, [Microsoft], Michael_Johnston, +1.408.359.aabb, Charles_Hemphill
Regrets
Chair
SV_MEETING_CHAIR
Scribe
Michael_Bodell

Contents


<trackbot> Date: 08 September 2011

<smaug> (I think)

discussion of http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Sep/att-0008/speechwepapi.html

Olli's comments are http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Sep/0009.html

Question about if value of checkbox makes sense => probably want to change the checked status

Olli: consider permission denied event in the case that you have a reco element and don't have permission

michael: the is an isAuthorized method or state variable

Olli: Yes, but would also need an event when that state variable changes

<Robert> BRB 5 mins

http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Sep/att-0008/speechwepapi.html

http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Sep/0009.html

DanD: Concerns about permissions in the non-traditional browser, particularly if you have multiple reco at once

Olli: Add authorization state variable to SpeechInputRequest
... Michael should remove "=FunctionOnly" to allow objects in the section 4 definition

<Robert> back

Michael: In the reco binding, change should to MUST and describe better the bindings (possibly excluding some elements if necessary, or describing them better if it isn't just value)

Section 7

Olli: Change addGrammarName with addGrammarWithName
... Add diableGrammarByName

DanD: Does this set of things match the protocol?

Robert: We don't know yet
... Do we need a grammar name?

Debbie: The name is for builtins

Robert: Builtin can be URI, and may need URI parameters

Charles: What about SRGS strings

Michael: You can sort of do that, with data: URI, but there are escaping issues

Olli: Can construct it by the JS or via an XMLHTTPRequest and pass that in... but could be data:

Robert: It is hard to describe grammars, and if you do that you can go to the extra trouble of data: work

Charles: You often want to include the grammar in the page for documentation/understanding/easier to pass

Debbie: We could have a grammar object complete with methods like add rule, but I think that would be too complexity

Charles: Could have a function like addGrammarByElementId

Olli: But that isn't so easy in HTML, no namespace and mixed HTML document

Robert: I think we'd be safer just going with URI, and people can create the data URI

resolution => remove addGrammarByName and other name

Charles: But beef up the description of addGrammar to mention builtins by uri

<smaug> methods names should use camelCase consistently

Debbie: On 7, we could make the parameters method into attribute values

Glen: We should have error or output if you try to set something during the reco

Michael: We've agreed that all of these only effect the *next* reco

Glen: We should document that

resolution => change teh set methods in section 7 to attributes

Michael: This means the default will be set so if the attribute is unmodified by author, they can inspect it

http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Aug/att-0011/ASRPropertiesAPI.html

<Robert> sorry, I have to go to another meeting. one of those days...

Debbie: What about recognizer.profile, recognizer.gender, recognizer.age?

resolution => add comment in document that user specific information would be set through generic set parameter functionality

Michael: What is the default language, if language is unset?

Debbie: There is a hierachy of possibilities we discussed before ending with the language of the page.

Michael: endpointdetection shoudl default to true, right?

Debbie: I'd think so

Michael: finalizebeforeend should be true too

Debbie: I think so. It might be more expensive, but there are a lot of use cases for that, and I think that is what users would like
... interimresults is the same use case

Michael: Probably should be true too

Debbie: yep, probably true
... setinterimresultsfreq doesn't have a default, maybe 500 ms default?

Charles: doesn't it depend on the technology and grammars and other things

Michael: It is just a hint, the service can override it

discussion of interimresults and interimresultsfrequency... merge them, have only one, have some settings, don't have a frequency

decision => merge interimresults and interimresultsfreq, one thing, an integer, 0 means off, other values are a hint that specifies the approx milliseconds between interim results, default is 0

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.133 (CVS log)
$Date: 2011/09/08 17:48:07 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.133  of Date: 2008/01/18 18:48:51  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_HTML_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: Michael_Bodell
Inferring Scribes: Michael_Bodell
Default Present: Michael_Bodell, +40.33.281.aaaa, Debbie_Dahl, Olli_Pettay, [Microsoft], Michael_Johnston, +1.408.359.aabb, Charles_Hemphill
Present: Michael_Bodell +40.33.281.aaaa Debbie_Dahl Olli_Pettay [Microsoft] Michael_Johnston +1.408.359.aabb Charles_Hemphill

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 08 Sep 2011
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


[End of scribe.perl diagnostic output]