HTML Speech Incubator Group Teleconference -- 28 Jul 2011

<burn> trackbot, start telcon

<trackbot> Date: 28 July 2011

<burn> Scribe: Milan_Young

<burn> ScribeNick: Milan

<bringert> dialing in in a min

Protocol report

Robert: About 1 week behind scedule
... Draft review is public
... Expect to incorperate redraft in one week

Dan: Need to discuss timings

Robert: Seems like a logisitcal challange

Bjorn: What is use case for async sending notifications?

Robert: Still debating

Dan: Let's talk now
... maybe at end of call
... Michael is still on vacation
... but doesn't look like alot of progress on API group

Bjorn: Agree that there has been no progress

Dan: Will speak with Michael when he returns

Bjorn: There are many outstanding tasks which were assigned by Michael

Dan: Agree that we need to follow-up on those tasks

Debbie: It's helpful if people just do their own requirements
... rather than wait for Raj

Robert: Perhaps we should do a task "role call" now

Dan: Good idea

<burn> Reminder email is http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Jul/0018.html

Dan: No communication from Raj

Charles: Did re-review Microsoft proposal
... need to flesh out more of the JavaScript API and maybe make a case for markup

Dan: Need to send everyting ASAP

Charles: Will try to send by next week

Dan: Don't have my task done, and no idea when it will be complete
... and no estimate

Oillie: Have something in mind, but need to formally write up
... will send in next couple days

Dan: Did recieve something from DanD, but not on the call today
... but it needs more discussion
... Did recieve something from Debbie

Debbie: Would like to review item #5
... If time today would like to discuss how to organize parameters
... could get something out by middle of next week
... don't expect a full rewrite, just cleanup and making more specific

Dan: Want to review Bjorn's proposal
... but haven't been on the call
... Did Michael fufil his taks?
... Doesn't seem like he has
... That is complete list of assignments
... but still unassigned tasks
... can do this on email, not just by conference
... Anything that needs to be discussed before charter expires?
... Floated idea to IETF that we may want to formalize the work of the protocol group
... Can take a few months to get a group together, so think about this now
... Need to "socialize" and then BOF session for next IETF (November)
... BOF writes the charter
... correction, BOF only approves the charter
... so should do this in advance
... had some conversations with Francois (from W3C)
... said we were well positioned for a working group creation
... next week is avaible for discussion for subgroup

Protocol work

<burn> ScribeNick: Milan

<burn> milan: Bjorn did you get my email on async events?

<burn> bjorn: yes. why would there be an event rather than something generated in UA?

<burn> milan: there are many different modalities.

<burn> bjorn: so why do we need an event channel?

<burn> bjorn: this would be adding a feature for something else to hijack speech channel and turn it into generic notification channel. it's not necessary.

<burn> charles: do we really need async results?

<burn> milan: you can request something from server and it might have a delayed result

<burn> bjorn: all responses are asynchronous

<burn> charles: why do we need events separate from requests?

<burn> milan: client wouldn't request a response, but server just sends event

<burn> bjorn: doesn't belong. all info from server may be delayed but must still be in response to a request

<burn> milan: okay

<burn> milan: ... I'm fine with that

Organizing parameters of a function

<ddahl> http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Jun/0086.html

Debbie: How to ballance parmeters to put in a recognition request vs on the general channel
... Pick most important properties to put on the recognizer request

Bjorn: Everything should be an attribute on the recognition object

Dan: Discussed parameter effects being immediate

Bjorn: Might have an "updateParameter" method to for them to take effect

Charles: Pause / resume functionality ?

Dan: Continous recognition means change at any point

<burn> bjorn: what's the use case for changing params while reco is running?

<burn> milan: that's how client can send events to server, e.g. mouse click occurred

<burn> bjorn: that's different from setting a param

<burn> milan: we don't have a way to send without setting parameters

<burn> bjorn: in protocol maybe, but we're talking about webapi now

<burn> robert: may be difficult to coordinate. better to send new grammar and then say when grammar is to begin applying

<burn> ... in continuous reco may transition through many different modes. audio needs to be continuous, need to say that grammars changed.

<burn> ... won't have to deal with maxnbest, etc. can set that up before reco. won't change language

Dan: Interesting mentioned language

Robert: Might have to change reconizers with the language

Bjorn: method to apply current parameters

Robjert: Consdier XHR
... if no outstanding request, then can change parameters

Bjorn: Then two types of parametesr

Charles: Runtime vs setup parameters

Dan: Always have some take place immediately and some not, but how does that affect API?

<smaug> setParameters({ param1: value, param2: value2})

<burn> bjorn: atomicity is the issue, but nothing else in HTML has atomicity

Robert: Example of nice HTML API
... perhaps Bjorn could send over email

Debbie: Leave this as an open issues
... will start email thread

- DRAFT -

HTML Speech Incubator Group Teleconference

28 Jul 2011

Attendees

Contents

Protocol report

Protocol work

Organizing parameters of a function

Summary of Action Items

Scribe.perl diagnostic output