Tuesday, 30 November 2010
Monday, 29 November 2010
- Re: R23. Speech as an input on any application should be able to be optional
- RE: R23. Speech as an input on any application should be able to be optional
- Re: R20. Web author selected TTS service should be available both on device and in the cloud.
- Re: R2. Application change from directed input to free form input.
- R2. Application change from directed input to free form input.
- R20. Web author selected TTS service should be available both on device and in the cloud.
Friday, 26 November 2010
Wednesday, 24 November 2010
- RE: Requirement for UA / SS protocol
- Re: Requirement for UA / SS protocol
- Re: R23. Speech as an input on any application should be able to be optional
Tuesday, 23 November 2010
- Re: R23. Speech as an input on any application should be able to be optional
- RE: Requirement for UA / SS protocol
- RE: Requirement for UA / SS protocol
- Re: Requirement for UA / SS protocol
- RE: Requirement for UA / SS protocol
- RE: Requirement for UA / SS protocol
- RE: Requirement for UA / SS protocol
- RE: Requirement for UA / SS protocol
- Re: Requirement for UA / SS protocol
- Re: Requirement for UA / SS protocol
- RE: Requirement for UA / SS protocol
- RE: Requirement for UA / SS protocol
- Re: R23. Speech as an input on any application should be able to be optional
- Re: R23. Speech as an input on any application should be able to be optional
- RE: R23. Speech as an input on any application should be able to be optional
- Re: R23. Speech as an input on any application should be able to be optional
- RE: R23. Speech as an input on any application should be able to be optional
- Re: Requirement for UA / SS protocol
- Re: R24. End user should be able to use speech in a hands-free mode
- Re: R23. Speech as an input on any application should be able to be optional
- Re: R23. Speech as an input on any application should be able to be optional
- RE: R23. Speech as an input on any application should be able to be optional
- RE: R24. End user should be able to use speech in a hands-free mode
Monday, 22 November 2010
- RE: Requirement for UA / SS protocol
- RE: Requirement for UA / SS protocol
- RE: R23. Speech as an input on any application should be able to be optional
- Re: R24. End user should be able to use speech in a hands-free mode
- Re: R25. It should be easy to extend the standard without affecting existing speech applications
- Re: R23. Speech as an input on any application should be able to be optional
- Re: R14. Web application authors need a way to specify and effectively create barge-in (interrupt audio and synthesis)
- Re: R24. End user should be able to use speech in a hands-free mode
- Re: R25. It should be easy to extend the standard without affecting existing speech applications
- R24. End user should be able to use speech in a hands-free mode
- R25. It should be easy to extend the standard without affecting existing speech applications
- RE: Requirement for UA / SS protocol
- Re: Requirement for UA / SS protocol
Saturday, 20 November 2010
Friday, 19 November 2010
- RE: Requirement for UA / SS protocol
- RE: Requirement for UA / SS protocol
- Draft minutes 18 November 2010
- Re: Requirement for UA / SS protocol
- RE: Requirement for UA / SS protocol
- RE: Requirement for UA / SS protocol
- Re: Requirement for UA / SS protocol
- Re: Requirement for UA / SS protocol
- RE: Requirement for UA / SS protocol
- Requirement for UA / SS protocol
Thursday, 18 November 2010
- RE: R23. Speech as an input on any application should be able to be optional
- Re: R23. Speech as an input on any application should be able to be optional
- Re: R14. Web application authors need a way to specify and effectively create barge-in (interrupt audio and synthesis)
- R23. Speech as an input on any application should be able to be optional
- R14. Web application authors need a way to specify and effectively create barge-in (interrupt audio and synthesis)
- Re: Clairiifcation
- Re: R26. There should exist a high quality default speech recognition visual user interface.
- Re: R26. There should exist a high quality default speech recognition visual user interface.
- Re: R5. Web application must be notified when speech recognition errors and other non-matches occur.
- Re: R26. There should exist a high quality default speech recognition visual user interface.
- [agenda] telecon 18 Nov. 2010
- RE: R30. End users should not be forced to store anything about their speech recognition environment in the cloud.
- RE: R26. There should exist a high quality default speech recognition visual user interface.
- RE: R28. Web application must not be allowed access to raw audio.
- RE: R7. Web application must be able to specify domain specific custom grammars.
- RE: R5. Web application must be notified when speech recognition errors and other non-matches occur.
Wednesday, 17 November 2010
- Re: R26. There should exist a high quality default speech recognition visual user interface.
- Re: R26. There should exist a high quality default speech recognition visual user interface.
Tuesday, 16 November 2010
- RE: R26. There should exist a high quality default speech recognition visual user interface.
- Re: R5. Web application must be notified when speech recognition errors and other non-matches occur.
- Re: R28. Web application must not be allowed access to raw audio.
- Re: R26. There should exist a high quality default speech recognition visual user interface.
- RE: R26. There should exist a high quality default speech recognition visual user interface.
- Re: R26. There should exist a high quality default speech recognition visual user interface.
- RE: R26. There should exist a high quality default speech recognition visual user interface.
- Re: R26. There should exist a high quality default speech recognition visual user interface.
- RE: R26. There should exist a high quality default speech recognition visual user interface.
- Re: R5. Web application must be notified when speech recognition errors and other non-matches occur.
- Re: R26. There should exist a high quality default speech recognition visual user interface.
- Re: R5. Web application must be notified when speech recognition errors and other non-matches occur.
- Re: R26. There should exist a high quality default speech recognition visual user interface.
- R5. Web application must be notified when speech recognition errors and other non-matches occur.
- R26. There should exist a high quality default speech recognition visual user interface.
Friday, 12 November 2010
- Re: R28. Web application must not be allowed access to raw audio.
- RE: R28. Web application must not be allowed access to raw audio.
- RE: R7. Web application must be able to specify domain specific custom grammars.
- Re: R28. Web application must not be allowed access to raw audio.
- Re: R7. Web application must be able to specify domain specific custom grammars.
- Re: R7. Web application must be able to specify domain specific custom grammars.
- R7. Web application must be able to specify domain specific custom grammars.
- R28. Web application must not be allowed access to raw audio.
- irc channel
Thursday, 11 November 2010
- Re: Clairiifcation
- Re: Clairiifcation
- telecon minutes 11 Nov 2010
- Re: Clairiifcation
- Re: R8. Web application must be able to specify language of recognition.
- Re: R8. Web application must be able to specify language of recognition.
- Re: R30. End users should not be forced to store anything about their speech recognition environment in the cloud.
- Re: R8. Web application must be able to specify language of recognition.
- Re: Minutes from Nov 4 AM2 session
- Re: [agenda] telecon 11 Nov. 2010
- [agenda] telecon 11 Nov. 2010
- Update requirements document
- RE: R8. Web application must be able to specify language of recognition.
- RE: R17. User perceived latency of recognition must be minimized.
- RE: R6. Web application must be provided with full context of recognition.
- RE: R30. End users should not be forced to store anything about their speech recognition environment in the cloud.
- RE: R21. Any public interface for creating extensions should be speakable
- RE: R18. User perceived latency of synthesis must be minimized
- RE: R30. End users should not be forced to store anything about their speech recognition environment in the cloud.
- RE: R8. Web application must be able to specify language of recognition.
Wednesday, 10 November 2010
- R8. Web application must be able to specify language of recognition.
- R30. End users should not be forced to store anything about their speech recognition environment in the cloud.
- RE: R18. User perceived latency of synthesis must be minimized
- Re: R18. User perceived latency of synthesis must be minimized
- Re: Minutes from Nov 4 AM2 session
- RE: R18. User perceived latency of synthesis must be minimized
- Re: R18. User perceived latency of synthesis must be minimized
- [f2f] compiled minutes
- Re: R18. User perceived latency of synthesis must be minimized
- Re: R18. User perceived latency of synthesis must be minimized
- RE: R18. User perceived latency of synthesis must be minimized
Tuesday, 9 November 2010
- RE: Minutes from Nov 4 AM2 session
- Re: Text to Speech proposal
- Re: R18. User perceived latency of synthesis must be minimized
- Re: Text to Speech proposal
- Re: Weekly teleconference information
- RE: Weekly teleconference information
- Weekly teleconference information
Monday, 8 November 2010
- RE: R18. User perceived latency of synthesis must be minimized
- Re: R18. User perceived latency of synthesis must be minimized
- Re: R18. User perceived latency of synthesis must be minimized
- RE: R18. User perceived latency of synthesis must be minimized
- Re: R18. User perceived latency of synthesis must be minimized
- RE: R18. User perceived latency of synthesis must be minimized
- Re: R6. Web application must be provided with full context of recognition.
- Re: R17. User perceived latency of recognition must be minimized.
- Re: R6. Web application must be provided with full context of recognition.
- Re: R17. User perceived latency of recognition must be minimized.
- R6. Web application must be provided with full context of recognition.
- R17. User perceived latency of recognition must be minimized.
- Re: Text to Speech proposal
Friday, 5 November 2010
- Re: Text to Speech proposal
- Re: R21. Any public interface for creating extensions should be speakable
- Re: Text to Speech proposal
- Re: R18. User perceived latency of synthesis must be minimized
- Re: R18. User perceived latency of synthesis must be minimized
- Re: R18. User perceived latency of synthesis must be minimized
- Re: R18. User perceived latency of synthesis must be minimized
- Re: Text to Speech proposal
- Re: Text to Speech proposal
- Re: R18. User perceived latency of synthesis must be minimized
- Re: R18. User perceived latency of synthesis must be minimized
- RE: Text to Speech proposal
- RE: R18. User perceived latency of synthesis must be minimized
- RE: R21. Any public interface for creating extensions should be speakable
- Re: R21. Any public interface for creating extensions should be speakable
Thursday, 4 November 2010
- Re: R18. User perceived latency of synthesis must be minimized
- Re: R21. Any public interface for creating extensions should be speakable
- RE: R18. User perceived latency of synthesis must be minimized
- RE: R21. Any public interface for creating extensions should be speakable
- Re: R21. Any public interface for creating extensions should be speakable
- Re: R18. User perceived latency of synthesis must be minimized
- R21. Any public interface for creating extensions should be speakable
- R18. User perceived latency of synthesis must be minimized
- Re: Text to Speech proposal
- Re: Text to Speech proposal
- RE: Text to Speech proposal
- Text to Speech proposal
- Minutes from Nov 4 AM2 session
- Re: Minutes from Nov 4 first monring session
- [f2f] updated agenda
- Minutes from Nov 4 first monring session
Wednesday, 3 November 2010
- Re: Offline webapps and speech UI
- Re: Offline webapps and speech UI
- Re: Offline webapps and speech UI
- Re: Offline webapps and speech UI
- Re: Offline webapps and speech UI
- Re: Offline webapps and speech UI
- Re: Offline webapps and speech UI
- Re: Offline webapps and speech UI
- Re: Offline webapps and speech UI
- Re: Offline webapps and speech UI
- Re: Offline webapps and speech UI
- Re: Offline webapps and speech UI
- Re: Offline webapps and speech UI
- Re: Offline webapps and speech UI
- Re: Offline webapps and speech UI
- Re: Organized first draft of Use Case and Requirements Document
- Re: Offline webapps and speech UI
- Re: [f2f] Agenda
- "Prompting the user is a security failure"
- Re: Offline webapps and speech UI
- Re: A study of various security prompts/user-permission scenarios
- A study of various security prompts/user-permission scenarios
- Fwd: minutes
- Offline webapps and speech UI
- RE: [f2f] Minutes - Tue Nov 2 - PM2
- Re: TPAC meeting and confidentiality
- Re: [f2f] Minutes - Tue Nov 2 - PM2