15:54:48 RRSAgent has joined #htmlspeech
15:54:48 logging to http://www.w3.org/2011/10/27-htmlspeech-irc
15:54:57 Milan has joined #HtmlSpeech
15:55:28 trackbot, start telcon
15:55:30 RRSAgent, make logs public
15:55:32 Zakim, this will be
15:55:32 I don't understand 'this will be', trackbot
15:55:33 Meeting: HTML Speech Incubator Group Teleconference
15:55:33 Date: 27 October 2011
15:55:39 zakim, this is htmlspeech
15:55:39 ok, burn; that matches INC_(HTMLSPEECH)11:30AM
15:55:48 Chair: Dan_Burnett
15:55:49 Agenda: http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Oct/0058.html
15:56:01 +??P34
15:56:17 Zakim, ??P34 is Olli_Pettay
15:56:17 +Olli_Pettay; got it
15:56:25 +Milan_Young
15:56:36 Zakim, nick smaug is Olli_Pettay
15:56:46 ok, smaug, I now associate you with Olli_Pettay
15:57:25 ddahl has joined #htmlspeech
15:57:48 zakim, I am Dan_Burnett
15:57:49 ok, burn, I now associate you with Dan_Burnett
15:57:51 mbodell has joined #htmlspeech
15:58:12 +Debbie_Dahl
15:58:44 zakim, who is here?
15:58:44 On the phone I see Dan_Burnett, Olli_Pettay, Milan_Young, Debbie_Dahl
15:58:45 On IRC I see mbodell, ddahl, Milan, RRSAgent, Zakim, burn, smaug, trackbot
16:00:08 +Michael_Bodell
16:00:40 +Dan_Druta
16:01:34 Charles has joined #htmlspeech
16:02:29 +Charles_Hemphill
16:02:35 glen has joined #htmlspeech
16:03:58 + +1.408.359.aaaa
16:04:16 zakim, aaaa is Glen_Shires
16:04:17 +Glen_Shires; got it
16:04:20 Agenda: http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Oct/0058.html
16:04:49 scribe:ddahl
16:05:02 chair:Dan_Burnett
16:05:12 topic: protocol questions
16:05:18 Document is http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Oct/0033.html
16:06:43 dan: let's postpone this
16:06:49 topic: f2f planning
16:06:58 zakim, who's here?
16:06:58 On the phone I see Dan_Burnett, Olli_Pettay, Milan_Young, Debbie_Dahl, Michael_Bodell, Dan_Druta, Charles_Hemphill, Glen_Shires
16:07:00 dan: who will be at f2f?
16:07:01 On IRC I see glen, Charles, mbodell, ddahl, Milan, RRSAgent, Zakim, burn, smaug, trackbot
16:07:54 olli: can we call in?
16:08:21 dan: didn't ask for a phone, usually hard to talk to someone on the phone at f2f
16:08:46 I know Robert will be there and so will Avery (a person from Microsoft who is starting to track these issues)
16:09:25 dan: will look into one-way audio stream
16:09:42 ...topics that people want to discuss?
16:10:02 glenn: won't that be close to our last chance?
16:10:18 dan: we need to be done by the end of November
16:10:36 s/glenn/glen
16:10:50 glen: we won't have much time after f2f, only 1-2 calls
16:11:15 michael: we should not expect to have any substantive discussions after f2f
16:11:29 ...only editorial
16:12:06 dan: after f2f, anything that we don't agree on, we have to stop work on
16:12:17 ...editorial work can be substantial, too
16:12:56 glen: should go into f2f with prioritized list of issues that we want to resolve
16:13:43 michael: try to raise open issues on email, can people also write up code examples, also want to make sure that we're handling use cases
16:14:19 dan: get people to sign up for sample code, even if not coming to f2f
16:14:28 +[Microsoft]
16:14:34 glen: what sample code should we be completing? is there a list?
16:14:49 http://www.w3.org/2005/Incubator/htmlspeech/live/requirements.html#section-use-cases
16:15:05 michael: we don't have a list, but can work through use cases to generate a list
16:16:02 glen: we should have priorities and examples ahead of time
16:16:06 zakim, [Microsoft] is Robert_Brown
16:16:06 +Robert_Brown; got it
16:16:32 robert has joined #htmlspeech
16:16:52 +Michael_Johnston
16:16:55 dan: we know what needs to happen, now we need to get people to sign up to do things.
16:17:12 MJ has joined #htmlspeech
16:17:22 glen: will sign up to do some sample code
16:18:32 michael: about seven people here who will be at f2f
16:19:34 registrants -- http://www.w3.org/2002/09/wbs/35125/TPAC2011/registrants#HTMLSpeech
16:19:48 glen: need quality use cases
16:20:29 danD: from a developer's perspective, I would like to see some real examples that allow me to accomplish a particular task
16:21:19 ...e.g. voice search, set up a service that isn't a default service
16:21:40 ...for example, a speech recognition service
16:22:10 glen: specifying a speech service is a good idea for an example.
16:22:58 ...some use cases span the gamut, that might require a huge JavaScript effort
16:24:06 danD: to show developers that this is real, we need to address immediate needs. we might not have the resources to fully accomplish this, but we should have a few examples
16:24:25 glen: I'm willing to take a crack at many of these
16:25:08 michael: some are pretty extensive, everyone should prepare samples for using the protocol and for using the WebAPI.
16:25:46 ...it doesn't hurt if there is some duplication, but would like to have coverage of many use cases
16:26:05 dan: do we need to make this more precise?
16:26:19 glen: no suggestions for making this more precise
16:27:05 michael: people should check with others if they also plan to do some
16:27:42 olli: will try something for permission handling
16:28:31 milan: would like to do something about continuous dictation in the protocol
16:28:56 ...would do the full stack
16:29:09 glen: will focus on the WebAPI, not the protocol
16:30:48 DanD has joined #htmlspeech
16:31:02 debbie: will do use case 5, Domain Specific Grammars Filling Multiple Input Fields
16:31:20 glen: what is the protocol aspect of that?
16:32:01 michael: the author doesn't have to get into that but we have to specify what goes into the protocol to accomplish the use case.
16:34:43 danD: could give a summarized description of what the connection is between the WebAPI and the protocol, could go back to the architecture and describe the bits and pieces we've put together over the past year. I can describe the architecture visually and in words.
16:35:35 michaelJ: will try to do something around multimodal interaction
16:36:46 dan: if you can't send sample before f2f, there probably won't be a chance to discuss it.
16:36:57 ...this is an important deadline
16:37:53 charles: will review and provide feedback on other contributions, will take a look at TTS but can't promise
16:38:51 http://www.w3.org/2005/Incubator/htmlspeech/live/NOTE-htmlspeech.html#use-cases
16:40:16 robert: driving directions, u15, rerecognition
16:41:41 ...will look at 3.3.3
16:42:38 dan: could we find something for Bjorn and Satish?
16:42:40 i'll look at 3.3.3, 3.3.7 and 3.3.15. can't promise quality
16:42:55 glen: will encourage them to do what they can
16:44:49 michael: can do a quick example on speech translation, both API and protocol
16:45:15 dan: might do an example of interpret from text, but may not get that done
16:45:46 ...will primarily work on compiling the report together
16:46:09 michaelJ: did we end up having the ability to put the grammar inline?
16:46:37 michael: not currently, but we talked about using a data scheme in the URI
16:46:56 charles: we should have an example showing that
16:47:26 ...can volunteer to provide that
16:48:10 michael: please send any substantive issues to the list in advance of the meeting.
16:48:27 topic: questions on the protocol
16:48:30 For the data scheme if people need reminders on how it works the wikipedia page at http://en.wikipedia.org/wiki/Data_URI_scheme describes it
16:49:04 robert: the first question is whether we would ever allow unencryted transmission
16:49:28 ...I think TLS encryption should be optional
16:50:00 olli: if there's a proxy, the proxy must not be able to read the transmission
16:50:17 michael: the user should know if the speech is happening over a secure channel or not
16:50:34 ...i don't know if it needs to be required for that
16:51:01 robert: if the page was fetched over TLS, would expect speech to be handled over TLS
16:51:21 dan: the security of the speech should be at least as strong as the security of the page
16:51:45 michael: the page should tell you what's secure and what's not
16:52:03 olli: this is a new kind of data, speech is more private
16:52:16 robert: what do current services use?
16:52:24 michael: Bing uses both
16:52:42 glen: I don't know about Google Voice Search
16:52:46 -Olli_Pettay
16:52:51 what...
16:53:23 robert: we should say that browsers have a strict policy about this, but it's not clear that we should disallow unencrypted transmission
16:54:00 dan: in MRCP it was useful to talk about the idea of a controlled environment
16:54:26 ...e.g. if the components are located on the same machine with no external network
16:55:00 robert: there are probably trivial applications where I'm not saying anything that's personally identifiable.
16:55:01 +??P2
16:55:17 Zakim, ??P2 is Olli_Pettay
16:55:17 +Olli_Pettay; got it
16:55:18 dan: could conceivably capture enough of your voice to train a TTS
16:55:21 -Dan_Burnett
16:55:34 michael: this is just about informed user consent
16:55:47 got dropped. was saying this is indeed different from mrcp where the user is not involved
16:55:58 ...people are putting their voices up in YouTube all the time
16:56:28 +Dan_Burnett
16:56:33 charles: people can restrict who can see their YouTubes
16:56:37 zakim, I am Dan_Burnett
16:56:37 ok, burn, I now associate you with Dan_Burnett
16:57:00 charles: people might assume that a commercial service is secure
16:57:26 robert: there are a lot of policy issues that depend on what country you're in, for example
16:58:32 glen: if you're jumping from one speech engine to another with different policies, it gets complicated, because the user might not know about it
16:59:02 robert: is there a strong case for disallowing unencrypted transmission?
16:59:30 glen: we had a discussion on how the user authorizes what speech engines are used
17:00:04 olli: there could be a proxy that recognizes you or other things like your gender from your voice
17:00:22 dan: don't see any reason to disallow unencrypted speech
17:01:14 michael: could discuss what happens when you're loaded securely and then Javascript tries to do something insecure
17:01:30 olli: is there any reason to allow unencrypted speech?
17:02:48 dan: we never know how our technologies are used you can't assume that there's always a person at the client, or you can't assume that the client and server are on different networks
17:03:15 ...there could be significance performance implications from encryption
17:03:44 olli: there could be an additional spec for more controlled environments
17:04:14 dan: wouldn't have a problem with always encrypting
17:04:34 robert: there has to be a consent UI to even send your voice to a service
17:05:02 olli: what happens to the data between the client and the service, there could be any number of proxies in between.
17:05:20 robert: the concern is about man in the middle attacks.
17:05:34 ...your server could disallow non-TLS connections
17:06:03 olli: but spec needs to be interoperable
17:06:47 robert: TLS is required in UA's because of man in the middle attacks, but could be optional in the other cases. we could say that between the browser and the server TLS is required.
17:07:31 michael: we should try to be consistent with other API's
17:07:54 olli: but this is a different kind of data. we could look at RTC, for example.
17:08:16 dan: there is a requirement for support of TLS, but I don't know if that's mandatory.
17:09:08 There is text in html for fetching at http://dev.w3.org/html5/spec/fetching-resources.html#fetch and it talks about various things (including same origin, and possilby CORS) but I don't see where it says things need to be secure, even when on a secure page
17:09:19 olli: in that case the UA can decide, but our situation is different
17:09:58 -Milan_Young
17:10:34 dan: will look for RTC info offline
17:11:45 robert: voice data is sensitive, and people don't realize that just because they're talking to their browser they might be vulnerable
17:11:57 ...however, other services might not be affected
17:12:42 robert: once you've given the data to a service, it can do whatever it likes with it
17:13:12 danD: it could use dedicated media transport and might not need TLS
17:13:22 dan: it's outside our scope.
17:13:42 danD: as a user, you trust the service that you're using
17:14:18 topic: EMMA with JSON payload
17:15:05 robert: in EMMA you can return pretty much whatever you like, JSON seemed like a good example, but we had decided not to use JSON
17:15:34 michael: it's ok to pull it out, the new examples will give a better sense of what you can do
17:16:13 michaelJ: i'm fine with that, you can do that with 1.0, in EMMA 1.1 you can specify the type of payload.
17:16:46 ...you can put all kinds of information in EMMA, for example, emotional state
17:17:35 ...the use case I'm most interested in is "send info". what does the EMMA coming back look like?
17:18:10 ...if you want something outside of the API, you can go into the EMMA to get it.
17:18:22 robert: will pull the example.
17:18:42 ...posted an update last week, won't plan to do another draft
17:18:51 ...comment if you have suggestions
17:19:07 topic:
17:19:19 dan: are we close to having a consensus?
17:20:12 michael: I think glen and I are close, not sure about everyone else
17:20:38 dan: let's summarize what it means to be close to an agreement
17:21:49 http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Oct/0060.html
17:21:57 http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Oct/0048.html
17:22:02 michael: made changes to the WebAPI document, sent around, topic of binding might be too dense for now
17:22:03 http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Oct/0055.html
17:22:24 ...if people have questions we could probably take a look at those.
17:22:33 Those links are examples from me, Glen, and charles respectively
17:23:37 dan: won't have a chance to pull things together until Sunday, so updates can be sent until then
17:24:16 robert: will do a quick update including today's discussion
17:24:31 s/updates/Robert's final updates to the protocol
17:25:04 michaelJ: do we have any js examples for current API spec?
17:25:42 michael: we have some simple examples for the markup, but not API
17:26:56 ...could try to write up a quick example that we could start from, will add an API example to section 1 today or tomorrow.
17:27:37 olli: needs to reread binding stuff
17:28:07 -Glen_Shires
17:28:08 -Robert_Brown
17:28:09 -Olli_Pettay
17:28:11 -Dan_Druta
17:28:15 -Debbie_Dahl
17:28:16 -Michael_Bodell
17:28:19 -Charles_Hemphill
17:28:22 -Dan_Burnett
17:28:35 zakim, who's on the phone?
17:28:35 On the phone I see Michael_Johnston
17:29:23 ddahl has left #htmlspeech
17:29:41 rrsagent, make log public
17:29:44 -Michael_Johnston
17:29:46 INC_(HTMLSPEECH)11:30AM has ended
17:29:47 Attendees were Dan_Burnett, Olli_Pettay, Milan_Young, Debbie_Dahl, Michael_Bodell, Dan_Druta, Charles_Hemphill, +1.408.359.aaaa, Glen_Shires, Robert_Brown, Michael_Johnston
17:29:50 rrsagent, draft minutes
17:29:50 I have made the request to generate http://www.w3.org/2011/10/27-htmlspeech-minutes.html burn
17:31:40 s/, +1.408.359.aaaa//
17:31:46 rrsagent, draft minutes
17:31:46 I have made the request to generate http://www.w3.org/2011/10/27-htmlspeech-minutes.html burn
17:34:47 mbodell has left #htmlspeech
19:46:33 Zakim has left #htmlspeech
21:40:10 smaug has joined #htmlspeech
22:59:02 smaug has joined #htmlspeech