Wednesday, 22 December 2010
Saturday, 18 December 2010
Friday, 17 December 2010
Thursday, 16 December 2010
- Re: "Protocol" requirement - Session
- Re: "Protocol" requirement - Re-recognition
- Re: "Protocol" requirement - Interpretation
- [agenda] telecon 16 December 2010
Wednesday, 15 December 2010
- Re: <device> questions
- RE: <device> questions
- RE: <device> questions
- Re: <device> questions
- RE: <device> questions
- Re: <device> questions
- RE: <device> questions
Tuesday, 14 December 2010
- Re: <device> questions
- <device> questions
- RE: "Protocol" requirement - Cancel request
- Re: "Protocol" requirement - Re-recognition
- RE: "Protocol" requirement - Re-recognition
- Re: "Protocol" requirement - Cancel request
- Re: "Protocol" requirement - Session
- Re: "Protocol" requirement - Re-recognition
- RE: "Protocol" requirement - Re-recognition
- Re: R19. End user extensions should be available both on desktop and in cloud
- RE: "Protocol" requirement - Session
- RE: "Protocol" requirement - Cancel request
- RE: "Protocol" requirement - Session
- RE: "Protocol" requirement - Session
- Re: "Protocol" requirement - Interpretation
- Re: "Protocol" requirement - Cancel request
- Re: R19. End user extensions should be available both on desktop and in cloud
- Re: "Protocol" requirement - Session
- [minutes] 9 December 2010
- RE: "Protocol" requirement - Session
- RE: "Protocol" requirement - Re-recognition
- RE: "Protocol" requirement - Session
- Re: R19. End user extensions should be available both on desktop and in cloud
- RE: R10. Web application authors need to be able to use full SSML features
Monday, 13 December 2010
- Re: R10. Web application authors need to be able to use full SSML features
- RE: Modification of FPR 30 - Common UA <=> SS protocol
- RE: "Protocol" requirement - Cancel request
- RE: "Protocol" requirement - Re-recognition
- RE: "Protocol" requirement - Interpretation
- RE: "Protocol" requirement - Best practices
- RE: "Protocol" requirement - Session
- Re: Modification of FPR 30 - Common UA <=> SS protocol
- Re: "Protocol" requirement - Cancel request
- Re: "Protocol" requirement - Re-recognition
- Re: "Protocol" requirement - Interpretation
- Re: "Protocol" requirement - Best practices
- Re: "Protocol" requirement - Session
- Re: "Protocol" requirement - Encryption
Friday, 10 December 2010
- RE: Modification of FPR 30 - Common UA <=> SS protocol
- "Protocol" requirement - Cancel request
- Modification of FPR 30 - Common UA <=> SS protocol
- "Protocol" requirement - Re-recognition
- "Protocol" requirement - Interpretation
- "Protocol" requirement - Best practices
- "Protocol" requirement - Session
- "Protocol" requirement - Encryption
Thursday, 9 December 2010
- Re: R19. End user extensions should be available both on desktop and in cloud
- Re: R19. End user extensions should be available both on desktop and in cloud
- RE: R13. Web application author should have ability to customize speech recognition graphical user interface
- Re: R9. Web application author provided synthesis feedback
- Re: R9. Web application author provided synthesis feedback
- Re: R13. Web application author should have ability to customize speech recognition graphical user interface
- Re: R11. Web application author must integrate input from multiple modalities
- Re: R11. Web application author must integrate input from multiple modalities
- RE: R13. Web application author should have ability to customize speech recognition graphical user interface
- Re: R13. Web application author should have ability to customize speech recognition graphical user interface
- RE: R13. Web application author should have ability to customize speech recognition graphical user interface
- Re: UA <=> SS Protocol
- Re: R23. Speech as an input on any application should be able to be optional
- Re: UA <=> SS Protocol
- Re: UA <=> SS Protocol
- Re: UA <=> SS Protocol
- Re: R13. Web application author should have ability to customize speech recognition graphical user interface
- Re: UA <=> SS Protocol
- Re: [agenda] telecon 9 December 2010
- Fwd: [agenda] telecon 9 December 2010
- Re: UA <=> SS Protocol
- [agenda] telecon 9 December 2010
- RE: R13. Web application author should have ability to customize speech recognition graphical user interface
- RE: R11. Web application author must integrate input from multiple modalities
- RE: R19. End user extensions should be available both on desktop and in cloud
- RE: R32. End users need a clear indication whenever microphone is listening to the user
- RE: R34. A trust relation is needed between end user and whatever is doing recognition
Wednesday, 8 December 2010
- RE: R19. End user extensions should be available both on desktop and in cloud
- RE: UA <=> SS Protocol
- Re: R13. Web application author should have ability to customize speech recognition graphical user interface
- Re: R9. Web application author provided synthesis feedback
- Re: R32. End users need a clear indication whenever microphone is listening to the user
- Re: R9. Web application author provided synthesis feedback
- Re: R19. End user extensions should be available both on desktop and in cloud
- Re: R9. Web application author provided synthesis feedback
- Re: R19. End user extensions should be available both on desktop and in cloud
- Re: R19. End user extensions should be available both on desktop and in cloud
- Re: R13. Web application author should have ability to customize speech recognition graphical user interface
- Re: R32. End users need a clear indication whenever microphone is listening to the user
- Re: R32. End users need a clear indication whenever microphone is listening to the user
- R9. Web application author provided synthesis feedback
- R19. End user extensions should be available both on desktop and in cloud
- R13. Web application author should have ability to customize speech recognition graphical user interface
- R32. End users need a clear indication whenever microphone is listening to the user
Tuesday, 7 December 2010
- RE: UA <=> SS Protocol
- RE: UA <=> SS Protocol
- Re: UA <=> SS Protocol
- Re: UA <=> SS Protocol
- RE: UA <=> SS Protocol
- Re: UA <=> SS Protocol
- RE: UA <=> SS Protocol
- Re: UA <=> SS Protocol
Monday, 6 December 2010
Sunday, 5 December 2010
Friday, 3 December 2010
- RE: UA <=> SS Protocol
- RE: UA <=> SS Protocol
- RE: R34. A trust relation is needed between end user and whatever is doing recognition
- Re: UA <=> SS Protocol
- Re: R34. A trust relation is needed between end user and whatever is doing recognition
- Re: R11. Web application author must integrate input from multiple modalities
- Re: R34. A trust relation is needed between end user and whatever is doing recognition
- R11. Web application author must integrate input from multiple modalities
- R34. A trust relation is needed between end user and whatever is doing recognition
Thursday, 2 December 2010
- [minutes] draft minutes 2 December 2010
- UA <=> SS Protocol
- RE: Requirement for UA / SS protocol
- [agenda] telecon 2 December 2010
- Re: R10. Web application authors need to be able to use full SSML features
- Re: Requirement for UA / SS protocol
- Re: R12. Web application author must be able to specify a domain specific statistical language model
- Re: R20. Web author selected TTS service should be available both on device and in the cloud.
- Re: R23. Speech as an input on any application should be able to be optional
- Re: R10. Web application authors need to be able to use full SSML features
- Re: R2. Application change from directed input to free form input.
- Re: R24. End user should be able to use speech in a hands-free mode
- Re: R14. Web application authors need a way to specify and effectively create barge-in (interrupt audio and synthesis)
- Re: R25. It should be easy to extend the standard without affecting existing speech applications
- Updated requirements document
- Re: R10. Web application authors need to be able to use full SSML features
- Re: R10. Web application authors need to be able to use full SSML features
- Re: Requirement for UA / SS protocol
- Re: R12. Web application author must be able to specify a domain specific statistical language model
- RE: Requirement for UA / SS protocol
- RE: R12. Web application author must be able to specify a domain specific statistical language model
- RE: Requirement for UA / SS protocol
Wednesday, 1 December 2010
- Re: R12. Web application author must be able to specify a domain specific statistical language model
- Re: Requirement for UA / SS protocol
- Re: R10. Web application authors need to be able to use full SSML features
- RE: Requirement for UA / SS protocol
- R10. Web application authors need to be able to use full SSML features
- R12. Web application author must be able to specify a domain specific statistical language model