15:45:58 RRSAgent has joined #htmlspeech
15:45:58 logging to http://www.w3.org/2011/05/12-htmlspeech-irc
15:46:04 Zakim has joined #htmlspeech
15:46:10 trackbot, start telcon
15:46:12 RRSAgent, make logs public
15:46:14 Zakim, this will be
15:46:14 I don't understand 'this will be', trackbot
15:46:15 Meeting: HTML Speech Incubator Group Teleconference
15:46:15 Date: 12 May 2011
15:46:18 zakim, this will be htmlspeech
15:46:18 ok, burn; I see INC_(HTMLSPEECH)12:00PM scheduled to start in 14 minutes
15:46:32 Chair: Dan Burnett
15:46:43 Agenda: http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011May/0005.html
15:52:22 bringert has joined #htmlspeech
15:54:13 burn has joined #htmlspeech
15:54:23 zakim, who's here?
15:54:23 INC_(HTMLSPEECH)12:00PM has not yet started, burn
15:54:25 On IRC I see burn, bringert, Zakim, RRSAgent, trackbot
15:55:03 INC_(HTMLSPEECH)12:00PM has now started
15:55:10 +Dan_Burnett
15:55:30 + +44.122.546.aaaa
15:55:49 zakim, aaaa is Bjorn_Bringert
15:55:49 +Bjorn_Bringert; got it
15:56:37 zakim, who is noisy?
15:56:48 burn, listening for 10 seconds I heard sound from the following: Bjorn_Bringert (45%)
15:57:05 +Milan_Young
15:57:07 -Bjorn_Bringert
15:57:29 bringert has joined #htmlspeech
15:57:34 Milan has joined #htmlspeech
15:57:52 +Michael_Bodell
15:58:15 mbodell has joined #htmlspeech
15:58:16 +[Microsoft]
15:58:28 zakim, [Microsoft] is Robert_Brown
15:58:28 +Robert_Brown; got it
15:58:37 bringert_ has joined #htmlspeech
15:58:45 I'm having connectivity issues
15:58:56 and it looks like I'm in here twice
15:59:27 Charles has joined #htmlspeech
15:59:35 +AZ
15:59:56 zakim, AZ is Bjorn_Bringert
15:59:56 +Bjorn_Bringert; got it
16:00:21 zakim, who's here?
16:00:21 On the phone I see Dan_Burnett, Milan_Young, Michael_Bodell, Robert_Brown, Bjorn_Bringert
16:00:24 On IRC I see Charles, bringert_, mbodell, Milan, bringert, burn, Zakim, RRSAgent, trackbot
16:00:25 + +1.425.381.aabb
16:00:26 ddahl has joined #htmlspeech
16:00:31 + +1.425.830.aacc
16:00:35 DanD has joined #htmlspeech
16:00:37 zakim, aabb is Dan_Druta
16:00:37 +Dan_Druta; got it
16:01:00 +Debbie_Dahl
16:01:02 zakim, aacc is Charles_Hemphill
16:01:02 +Charles_Hemphill; got it
16:01:03 robert has joined #htmlspeech
16:01:32 satish has joined #htmlspeech
16:01:50 bjorn, we can hear you
16:01:59 ok, I can't hear anyone else
16:02:12 -Bjorn_Bringert
16:02:14 try a different connection
16:02:17 trying
16:02:44 Scribe: Dan_Druta
16:02:48 ScribeNick: DanD
16:03:39 Agenda: http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011May/0005.html
16:04:05 smaug has joined #htmlspeech
16:04:17 Topic: Updated final report draft
16:04:43 burn: Made a few changes
16:05:22 Burn: Topic: Design Decisions with agreements
16:05:34 +??P12
16:05:51 Topic: Design Decisions with agreements
16:05:52 zakim, ??P12 is Olli_Pettay
16:05:56 +Olli_Pettay; got it
16:06:02 Zakim, nick smaug is Olli_Pettay
16:06:02 ok, smaug, I now associate you with Olli_Pettay
16:06:07 Burn: Any new items we agree on?
16:06:19 Burn: No design decisions?
16:06:36 Burn: Any other topics to be discussed later?
16:07:18 Topic: Issues discussed in the appendix
16:07:46 Topic: Audio Codex
16:07:54 +Michael_Johnston
16:09:37 robert: We don't think we should agree on codex. We should look at a few items: One by bandwidth, ip issues,
16:10:09 s/codex/codec
16:10:25 robert: there are trade offs
16:10:26 bringert_ has joined #htmlspeech
16:10:56 +Bjorn_Bringert
16:11:06 robert: fidelity is another issue
16:11:52 burn: We want the ideal codec but there no such thing
16:12:22 burn: Opus is a combination of codecs and an attempt to provide an industry standard
16:12:28 +Patrick_Ehlen
16:12:42 Milan: RTCWeb is looking at Opus
16:13:13 burn: The issue is which audio codex is mandatory to support
16:13:53 mbodell: The question is if you can recognize an audio file
16:14:32 Milan: is the synthesizer also part of this?
16:15:29 Bringrt: Three items: 1. Codex use for remote speech engine
16:15:35 bringert has joined #htmlspeech
16:15:46 1. codecs used between browser and web app specified recognizer
16:16:11 Milan: 2. Codec use for file speech
16:16:16 2. codecs used between web app and browser for recognition of existing audio
16:16:23 there is terrible echo now
16:16:40 bringert_ has joined #htmlspeech
16:16:46 zakim, who's making noise?
16:16:57 burn, listening for 10 seconds I heard sound from the following: Dan_Burnett (43%), Milan_Young (14%), Dan_Druta (14%)
16:17:06 3. codes used between browser and web app specified synthesizer
16:17:11 -Bjorn_Bringert
16:17:15 zakim, who's making noise?
16:17:25 burn, listening for 10 seconds I could not identify any sounds
16:18:15 +Bjorn_Bringert
16:18:45 mbodell: we should allow other codec to be used
16:18:58 Milan: Sounds like requirements
16:20:24 robert: Microsoft uses SIREN owned by Polycom.
16:20:53 burn: Voxeo support all
16:21:09 Google uses Speex, FLAC and AMR
16:21:36 Michael has joined #htmlspeech
16:22:12 Milan: Opus has the notion to cutoff audio and saves bandwidth
16:22:39 Milan: speech has a critical requirement to capture the first part
16:22:54 burn: There are several codecs in Opus
16:23:23 burn: There was an attempt to merge
16:23:59 Michael: is the issue of support in mobile devices (hardware)
16:24:39 Michael: for the mobile browsing we can rely on hardware and fall back
16:25:19 bringert: The one codec that has must support is Speex
16:25:51 bringert: Caution - there's no container format
16:26:26 burn: another issue is transport (framing)
16:26:52 Milan: isn't an IETF standard
16:27:10 burn: It will require some sort of support for RTP
16:27:30 burn: How much SIP support will be needed?
16:28:10 burn: There's disarrangement and not everybody want a full SIP stack
16:28:22 bringert: how about OGG?
16:28:30 s/disarrangement/disagreement
16:28:37 Speex codec in OGG container
16:28:42 s/disarrangement/disagreement/
16:29:32 burn: It is appropriate not to commit yet and review next week
16:30:01 Milan: It would be useful to know streaming
16:30:49 mbodell: Add a forth item to the list of elements: support for streaming
16:31:18 Milan: can we agree that the architecture should support streaming?
16:32:45 bringert: I'm fine if we support streaming before the engine starts processing
16:33:55 Milan: Recognizer should be able to return results before the end of speech
16:34:52 burn: Recognizer should be able to return final result before the end of speech
16:35:10 bringert: This rules out HTTP
16:36:56 mbodell: You can't get duplex but you can get intermediary responses
16:37:06 zakim, who is noisy?
16:37:18 burn, listening for 11 seconds I heard sound from the following: Michael_Bodell (12%), Bjorn_Bringert (8%), Milan_Young (73%), Robert_Brown (14%)
16:37:19 Milan: The client can chunk up responses
16:37:58 Milan: Is it a violation if we use web sockets?
16:38:05 I'm muted
16:41:37 burn: we don't seem to have scribe anymore
16:42:21 DanD has joined #htmlspeech
16:42:56 burn: We need to be careful not to go in a different direction from RTCWeb
16:43:25 mbodell: different protocol for different use cases
16:43:44 mbodell: http works well for certain cases
16:44:01 robert: we don't want to over complicate
16:44:23 robert: RTC has a different set of requirements
16:44:57 burn: you are right
16:45:26 bringert: We have two choices: we go with http and add RTCweb
16:45:28 zakim, who is noisy?
16:45:39 burn, listening for 10 seconds I heard sound from the following: Robert_Brown (7%)
16:45:42 robert: or web sockets
16:46:52 bringert: is anyone opposing support for HTTP?
16:47:03 bringert: for streaming
16:47:16 bringert: We support it in Chrome 11
16:48:46 bringert: We want to have http used for other interactions between the user agent and server
16:49:38 mbodell: It's not just audio if we understand correctly
16:50:48 mbodell: different apps would use different approaches
16:51:45 burn: we can't predict how it will be used
16:52:21 Milan: there's a continuous response
16:52:53 robert: I'd like to see a proposal before we agree
16:53:34 http://tools.ietf.org/html/draft-zhu-http-fullduplex-02
16:53:35 -Patrick_Ehlen
16:54:18 +Patrick_Ehlen
16:55:04 Milan: I agree with a solution that uses HTTP as a basic but not full solution
16:55:28 robert: I would not call Web Sockets HTTP and I'd like to see a proposal
16:55:54 bringert: We should be able to use HTTP
16:56:37 burn: We are saying we are mandating HTTP not eliminating the potential support for other
16:56:52 zakim, who is noisy?
16:57:06 burn, listening for 12 seconds I heard sound from the following: Charles_Hemphill (3%)
16:57:26 bringert: the server does not know what's supported on the browser
16:57:50 robert: we need some discovery capability
16:58:05 -Robert_Brown
16:59:13 burn: We believe Web Sockets will not be mandated for support
16:59:38 Milan: I'm not asking for that but a solution for bidirectional support
17:00:01 Milan: if HTTP can do bidirectional we're fine
17:00:36 bringert: there's no reason not support HTTP.
17:01:20 bringert: would love bidirectional support if we had a good solid candidate for it
17:01:29 Milan: Instead of saying HTTP is required let's list the elements
17:01:58 bringert: We should require HTTP
17:02:28 burn: Agreement - we require http support for all communications and allow for others
17:03:37 mbodell: I'd like to have a solution for bidirectional support but we should not block the spec
17:04:28 burn: other topics around codecs?
17:04:56 mbodell: some audio codecs that support audio and video
17:05:49 mbodell: recognize audio from a video+audio stream
17:06:28 bringert: I would suggest we don't send video to reduce bandwidth
17:07:23 bringert: if we don't have strong use cases we should not add it to the spec
17:07:24 -Patrick_Ehlen
17:07:44 +Patrick_Ehlen
17:08:40 bringert: Should we disallow sending video?
17:09:52 burn: no agreements and the best way is not to make any other statements
17:10:11 burn: add this to the list of topics
17:10:50 burn: nobody is talking about gesture recognition just audio
17:13:04 burn: we will get back to this
17:13:36 burn: Other items related to codecs?
17:14:36 Milan: are there any other candidates:
17:15:04 burn: OPUS. Big but with support for different use cases
17:16:08 http://en.wikipedia.org/wiki/Comparison_of_audio_codecs
17:17:49 Topic: F2F Logistics
17:18:05 bringert: no updates
17:18:42 bringert: I will come back with directions from the hotel to the offices
17:20:11 bringert: We sent the directions from the airport
17:20:30 bringert: everybody should have gotten the email
17:21:32 burn: it would still be good if we have some directions from hotel to the Google offices
17:22:18 burn: one more call before the f2f
17:23:25 -Milan_Young
17:26:07 bringert: There's a statement about the agreement on the user interface that is not well captured
17:26:34 burn: We need to revise it
17:27:04 -Michael_Bodell
17:27:09 -Olli_Pettay
17:27:10 -Debbie_Dahl
17:27:11 -Patrick_Ehlen
17:27:21 -Michael_Johnston
17:27:23 -Dan_Druta
17:27:42 bringert has joined #htmlspeech
17:27:58 -Bjorn_Bringert
17:28:24 Regrets: Marc_Schroeder
17:28:33 -Charles_Hemphill
17:30:13 s/We need to revise it/Yes, I somehow dropped the most important decision -- that it must NOT be possible to customize the part of the user interface that indicates the microphone is open. I will add that in./
17:30:23 s/codex/codecs/g
17:30:40 -Dan_Burnett
17:30:41 INC_(HTMLSPEECH)12:00PM has ended
17:30:42 Attendees were Dan_Burnett, +44.122.546.aaaa, Bjorn_Bringert, Milan_Young, Michael_Bodell, Robert_Brown, +1.425.381.aabb, +1.425.830.aacc, Dan_Druta, Debbie_Dahl, Charles_Hemphill,
17:30:45 ... Olli_Pettay, Michael_Johnston, Patrick_Ehlen
17:30:57 zakim, bye
17:30:57 Zakim has left #htmlspeech
17:31:06 rrsagent, make log public
17:31:15 rrsagent, draft minutes
17:31:15 I have made the request to generate http://www.w3.org/2011/05/12-htmlspeech-minutes.html burn
17:31:33 ddahl has left #htmlspeech
17:32:33 s/, +44.122.546.aaaa//
17:33:01 s/, +1.425.381.aabb, +1.425.830.aacc//
17:33:08 rrsagent, draft minutes
17:33:08 I have made the request to generate http://www.w3.org/2011/05/12-htmlspeech-minutes.html burn
17:34:51 s/Codex/Codecs/g
17:34:56 rrsagent, draft minutes
17:34:56 I have made the request to generate http://www.w3.org/2011/05/12-htmlspeech-minutes.html burn