public-xg-htmlspeech@w3.org from November 2010 by author

Andy Mauro

• Re: Offline webapps and speech UI (Wednesday, 3 November)
• Re: Offline webapps and speech UI (Wednesday, 3 November)
• Re: Offline webapps and speech UI (Wednesday, 3 November)
• Re: Offline webapps and speech UI (Wednesday, 3 November)
• Re: Offline webapps and speech UI (Wednesday, 3 November)
• Re: Offline webapps and speech UI (Wednesday, 3 November)
• Re: Offline webapps and speech UI (Wednesday, 3 November)
• Re: Organized first draft of Use Case and Requirements Document (Wednesday, 3 November)

Baggia Paolo

• RE: Text to Speech proposal (Thursday, 4 November)
• RE: [f2f] Minutes - Tue Nov 2 - PM2 (Wednesday, 3 November)
• [f2f] Minutes - Tue Nov 2 - PM2 (Tuesday, 2 November)

Bjorn Bringert

• Re: R20. Web author selected TTS service should be available both on device and in the cloud. (Monday, 29 November)
• Re: R2. Application change from directed input to free form input. (Monday, 29 November)
• Re: Requirement for UA / SS protocol (Wednesday, 24 November)
• Re: R23. Speech as an input on any application should be able to be optional (Wednesday, 24 November)
• Re: Requirement for UA / SS protocol (Tuesday, 23 November)
• Re: R23. Speech as an input on any application should be able to be optional (Tuesday, 23 November)
• Re: Requirement for UA / SS protocol (Tuesday, 23 November)
• Re: R24. End user should be able to use speech in a hands-free mode (Tuesday, 23 November)
• Re: R23. Speech as an input on any application should be able to be optional (Tuesday, 23 November)
• Re: R23. Speech as an input on any application should be able to be optional (Tuesday, 23 November)
• Re: R25. It should be easy to extend the standard without affecting existing speech applications (Monday, 22 November)
• Re: Requirement for UA / SS protocol (Friday, 19 November)
• Re: R23. Speech as an input on any application should be able to be optional (Thursday, 18 November)
• Re: R14. Web application authors need a way to specify and effectively create barge-in (interrupt audio and synthesis) (Thursday, 18 November)
• Re: R5. Web application must be notified when speech recognition errors and other non-matches occur. (Thursday, 18 November)
• Re: R26. There should exist a high quality default speech recognition visual user interface. (Thursday, 18 November)
• Re: R26. There should exist a high quality default speech recognition visual user interface. (Wednesday, 17 November)
• Re: R26. There should exist a high quality default speech recognition visual user interface. (Tuesday, 16 November)
• Re: R26. There should exist a high quality default speech recognition visual user interface. (Tuesday, 16 November)
• Re: R5. Web application must be notified when speech recognition errors and other non-matches occur. (Tuesday, 16 November)
• Re: R26. There should exist a high quality default speech recognition visual user interface. (Tuesday, 16 November)
• Re: R28. Web application must not be allowed access to raw audio. (Friday, 12 November)
• Re: R28. Web application must not be allowed access to raw audio. (Friday, 12 November)
• Re: R7. Web application must be able to specify domain specific custom grammars. (Friday, 12 November)
• Re: Clairiifcation (Thursday, 11 November)
• Re: R30. End users should not be forced to store anything about their speech recognition environment in the cloud. (Thursday, 11 November)
• Re: R8. Web application must be able to specify language of recognition. (Thursday, 11 November)
• Re: R18. User perceived latency of synthesis must be minimized (Wednesday, 10 November)
• Re: R18. User perceived latency of synthesis must be minimized (Wednesday, 10 November)
• Re: R18. User perceived latency of synthesis must be minimized (Tuesday, 9 November)
• Re: Text to Speech proposal (Tuesday, 9 November)
• Re: R18. User perceived latency of synthesis must be minimized (Monday, 8 November)
• Re: R6. Web application must be provided with full context of recognition. (Monday, 8 November)
• Re: R17. User perceived latency of recognition must be minimized. (Monday, 8 November)
• Re: Text to Speech proposal (Friday, 5 November)
• Re: Text to Speech proposal (Friday, 5 November)
• Re: R18. User perceived latency of synthesis must be minimized (Friday, 5 November)
• Re: Text to Speech proposal (Friday, 5 November)
• Re: R18. User perceived latency of synthesis must be minimized (Friday, 5 November)
• Re: R21. Any public interface for creating extensions should be speakable (Thursday, 4 November)
• Re: R18. User perceived latency of synthesis must be minimized (Thursday, 4 November)
• Re: Text to Speech proposal (Thursday, 4 November)
• Text to Speech proposal (Thursday, 4 November)
• Re: Offline webapps and speech UI (Wednesday, 3 November)
• Re: Offline webapps and speech UI (Wednesday, 3 November)
• Re: Offline webapps and speech UI (Wednesday, 3 November)
• Re: Offline webapps and speech UI (Wednesday, 3 November)
• Re: Offline webapps and speech UI (Wednesday, 3 November)

chan@info-cast.com

• Re: R23. Speech as an input on any application should be able to be optional (Friday, 26 November)
• Re: R23. Speech as an input on any application should be able to be optional (Tuesday, 23 November)
• RE: R23. Speech as an input on any application should be able to be optional (Tuesday, 23 November)

Dan Burnett

• R2. Application change from directed input to free form input. (Monday, 29 November)
• R20. Web author selected TTS service should be available both on device and in the cloud. (Monday, 29 November)
• R24. End user should be able to use speech in a hands-free mode (Monday, 22 November)
• R25. It should be easy to extend the standard without affecting existing speech applications (Monday, 22 November)
• Draft minutes 18 November 2010 (Friday, 19 November)
• R23. Speech as an input on any application should be able to be optional (Thursday, 18 November)
• R14. Web application authors need a way to specify and effectively create barge-in (interrupt audio and synthesis) (Thursday, 18 November)
• Re: Clairiifcation (Thursday, 18 November)
• Re: R26. There should exist a high quality default speech recognition visual user interface. (Thursday, 18 November)
• R5. Web application must be notified when speech recognition errors and other non-matches occur. (Tuesday, 16 November)
• R26. There should exist a high quality default speech recognition visual user interface. (Tuesday, 16 November)
• R7. Web application must be able to specify domain specific custom grammars. (Friday, 12 November)
• R28. Web application must not be allowed access to raw audio. (Friday, 12 November)
• irc channel (Friday, 12 November)
• telecon minutes 11 Nov 2010 (Thursday, 11 November)
• Re: R8. Web application must be able to specify language of recognition. (Thursday, 11 November)
• Re: Minutes from Nov 4 AM2 session (Thursday, 11 November)
• Re: [agenda] telecon 11 Nov. 2010 (Thursday, 11 November)
• [agenda] telecon 11 Nov. 2010 (Thursday, 11 November)
• R8. Web application must be able to specify language of recognition. (Wednesday, 10 November)
• R30. End users should not be forced to store anything about their speech recognition environment in the cloud. (Wednesday, 10 November)
• [f2f] compiled minutes (Wednesday, 10 November)
• Re: Weekly teleconference information (Tuesday, 9 November)
• Weekly teleconference information (Tuesday, 9 November)
• R6. Web application must be provided with full context of recognition. (Monday, 8 November)
• R17. User perceived latency of recognition must be minimized. (Monday, 8 November)
• R21. Any public interface for creating extensions should be speakable (Thursday, 4 November)
• R18. User perceived latency of synthesis must be minimized (Thursday, 4 November)
• [f2f] updated agenda (Thursday, 4 November)
• Fwd: minutes (Wednesday, 3 November)
• Re: TPAC meeting and confidentiality (Wednesday, 3 November)

Dave Burke

• "Prompting the user is a security failure" (Wednesday, 3 November)

David Bolter

• Re: Text to Speech proposal (Thursday, 4 November)

Deborah Dahl

• RE: R23. Speech as an input on any application should be able to be optional (Tuesday, 23 November)
• RE: R23. Speech as an input on any application should be able to be optional (Tuesday, 23 November)
• RE: R23. Speech as an input on any application should be able to be optional (Monday, 22 November)
• RE: R23. Speech as an input on any application should be able to be optional (Thursday, 18 November)
• RE: R26. There should exist a high quality default speech recognition visual user interface. (Tuesday, 16 November)
• RE: R26. There should exist a high quality default speech recognition visual user interface. (Tuesday, 16 November)
• RE: R26. There should exist a high quality default speech recognition visual user interface. (Tuesday, 16 November)

Eric S. Johansson

• Re: Requirement for UA / SS protocol (Monday, 22 November)
• Re: Requirement for UA / SS protocol (Friday, 19 November)
• Re: Requirement for UA / SS protocol (Friday, 19 November)
• Re: R26. There should exist a high quality default speech recognition visual user interface. (Wednesday, 17 November)
• Re: R21. Any public interface for creating extensions should be speakable (Friday, 5 November)

Jeremy Orlow

• Re: TPAC meeting and confidentiality (Monday, 1 November)

Marc Schroeder

• Re: R20. Web author selected TTS service should be available both on device and in the cloud. (Tuesday, 30 November)
• Re: R18. User perceived latency of synthesis must be minimized (Wednesday, 10 November)
• Re: R18. User perceived latency of synthesis must be minimized (Wednesday, 10 November)
• Re: R18. User perceived latency of synthesis must be minimized (Friday, 5 November)
• Re: R18. User perceived latency of synthesis must be minimized (Friday, 5 November)
• Re: Text to Speech proposal (Friday, 5 November)
• Minutes from Nov 4 first monring session (Thursday, 4 November)

Michael Bodell

• [agenda] telecon 18 Nov. 2010 (Thursday, 18 November)
• RE: R30. End users should not be forced to store anything about their speech recognition environment in the cloud. (Thursday, 18 November)
• RE: R26. There should exist a high quality default speech recognition visual user interface. (Thursday, 18 November)
• RE: R28. Web application must not be allowed access to raw audio. (Thursday, 18 November)
• RE: R7. Web application must be able to specify domain specific custom grammars. (Thursday, 18 November)
• RE: R5. Web application must be notified when speech recognition errors and other non-matches occur. (Thursday, 18 November)
• RE: R28. Web application must not be allowed access to raw audio. (Friday, 12 November)
• RE: R7. Web application must be able to specify domain specific custom grammars. (Friday, 12 November)
• Update requirements document (Thursday, 11 November)
• RE: R8. Web application must be able to specify language of recognition. (Thursday, 11 November)
• RE: R17. User perceived latency of recognition must be minimized. (Thursday, 11 November)
• RE: R6. Web application must be provided with full context of recognition. (Thursday, 11 November)
• RE: R30. End users should not be forced to store anything about their speech recognition environment in the cloud. (Thursday, 11 November)
• RE: R21. Any public interface for creating extensions should be speakable (Thursday, 11 November)
• RE: R18. User perceived latency of synthesis must be minimized (Thursday, 11 November)

Olli Pettay

• Re: R23. Speech as an input on any application should be able to be optional (Monday, 29 November)
• Re: Requirement for UA / SS protocol (Tuesday, 23 November)
• Re: Requirement for UA / SS protocol (Tuesday, 23 November)
• Re: R23. Speech as an input on any application should be able to be optional (Tuesday, 23 November)
• Re: R23. Speech as an input on any application should be able to be optional (Tuesday, 23 November)
• Re: R23. Speech as an input on any application should be able to be optional (Monday, 22 November)
• Re: R14. Web application authors need a way to specify and effectively create barge-in (interrupt audio and synthesis) (Monday, 22 November)
• Re: R24. End user should be able to use speech in a hands-free mode (Monday, 22 November)
• Re: R25. It should be easy to extend the standard without affecting existing speech applications (Monday, 22 November)
• Re: R26. There should exist a high quality default speech recognition visual user interface. (Tuesday, 16 November)
• Re: R5. Web application must be notified when speech recognition errors and other non-matches occur. (Tuesday, 16 November)
• Re: R26. There should exist a high quality default speech recognition visual user interface. (Tuesday, 16 November)
• Re: R7. Web application must be able to specify domain specific custom grammars. (Friday, 12 November)
• Re: Clairiifcation (Thursday, 11 November)
• Re: Clairiifcation (Thursday, 11 November)
• Re: R8. Web application must be able to specify language of recognition. (Thursday, 11 November)
• Re: Text to Speech proposal (Tuesday, 9 November)
• Re: R18. User perceived latency of synthesis must be minimized (Monday, 8 November)
• Re: R6. Web application must be provided with full context of recognition. (Monday, 8 November)
• Re: R17. User perceived latency of recognition must be minimized. (Monday, 8 November)
• Re: R21. Any public interface for creating extensions should be speakable (Friday, 5 November)
• Re: R18. User perceived latency of synthesis must be minimized (Friday, 5 November)
• Re: R18. User perceived latency of synthesis must be minimized (Friday, 5 November)
• Re: Offline webapps and speech UI (Wednesday, 3 November)
• Re: Offline webapps and speech UI (Wednesday, 3 November)
• Re: A study of various security prompts/user-permission scenarios (Wednesday, 3 November)
• Offline webapps and speech UI (Wednesday, 3 November)
• Re: [f2f] Agenda (Monday, 1 November)
• Re: TPAC meeting and confidentiality (Monday, 1 November)
• TPAC meeting and confidentiality (Monday, 1 November)

Raj\(Openstream\)

• Re: Minutes from Nov 4 AM2 session (Wednesday, 10 November)
• Minutes from Nov 4 AM2 session (Thursday, 4 November)
• Re: Minutes from Nov 4 first monring session (Thursday, 4 November)

Robert Brown

• RE: R23. Speech as an input on any application should be able to be optional (Monday, 29 November)
• RE: Requirement for UA / SS protocol (Wednesday, 24 November)
• RE: Requirement for UA / SS protocol (Tuesday, 23 November)
• RE: Requirement for UA / SS protocol (Tuesday, 23 November)
• RE: Requirement for UA / SS protocol (Tuesday, 23 November)
• RE: Requirement for UA / SS protocol (Tuesday, 23 November)
• RE: R24. End user should be able to use speech in a hands-free mode (Tuesday, 23 November)
• RE: Requirement for UA / SS protocol (Monday, 22 November)
• RE: Requirement for UA / SS protocol (Monday, 22 November)
• RE: Requirement for UA / SS protocol (Saturday, 20 November)
• RE: Requirement for UA / SS protocol (Friday, 19 November)
• RE: Requirement for UA / SS protocol (Friday, 19 November)
• RE: R26. There should exist a high quality default speech recognition visual user interface. (Tuesday, 16 November)
• RE: R30. End users should not be forced to store anything about their speech recognition environment in the cloud. (Thursday, 11 November)
• RE: R8. Web application must be able to specify language of recognition. (Thursday, 11 November)
• RE: R18. User perceived latency of synthesis must be minimized (Wednesday, 10 November)
• RE: Minutes from Nov 4 AM2 session (Tuesday, 9 November)
• RE: R18. User perceived latency of synthesis must be minimized (Friday, 5 November)
• RE: R21. Any public interface for creating extensions should be speakable (Friday, 5 November)
• RE: R18. User perceived latency of synthesis must be minimized (Thursday, 4 November)
• RE: R21. Any public interface for creating extensions should be speakable (Thursday, 4 November)

Satish Sampath

• Re: R24. End user should be able to use speech in a hands-free mode (Monday, 22 November)
• Re: R26. There should exist a high quality default speech recognition visual user interface. (Thursday, 18 November)
• Re: R5. Web application must be notified when speech recognition errors and other non-matches occur. (Tuesday, 16 November)
• Re: R28. Web application must not be allowed access to raw audio. (Tuesday, 16 November)
• Re: R18. User perceived latency of synthesis must be minimized (Monday, 8 November)
• Re: R18. User perceived latency of synthesis must be minimized (Thursday, 4 November)
• Re: R21. Any public interface for creating extensions should be speakable (Thursday, 4 November)
• Re: Offline webapps and speech UI (Wednesday, 3 November)
• Re: Offline webapps and speech UI (Wednesday, 3 November)
• Re: Offline webapps and speech UI (Wednesday, 3 November)
• Re: [f2f] Agenda (Wednesday, 3 November)
• A study of various security prompts/user-permission scenarios (Wednesday, 3 November)
• Re: [f2f] Minutes - Tue Nov 2 - PM2 (Wednesday, 3 November)

T.V Raman

• Re: Text to Speech proposal (Monday, 8 November)

Young, Milan

• RE: Requirement for UA / SS protocol (Tuesday, 23 November)
• RE: Requirement for UA / SS protocol (Tuesday, 23 November)
• RE: Requirement for UA / SS protocol (Tuesday, 23 November)
• RE: Requirement for UA / SS protocol (Tuesday, 23 November)
• RE: Requirement for UA / SS protocol (Monday, 22 November)
• RE: Requirement for UA / SS protocol (Saturday, 20 November)
• RE: Requirement for UA / SS protocol (Friday, 19 November)
• RE: Requirement for UA / SS protocol (Friday, 19 November)
• RE: Requirement for UA / SS protocol (Friday, 19 November)
• Requirement for UA / SS protocol (Friday, 19 November)
• RE: R18. User perceived latency of synthesis must be minimized (Wednesday, 10 November)
• RE: R18. User perceived latency of synthesis must be minimized (Wednesday, 10 November)
• RE: Weekly teleconference information (Tuesday, 9 November)
• RE: R18. User perceived latency of synthesis must be minimized (Monday, 8 November)
• RE: R18. User perceived latency of synthesis must be minimized (Monday, 8 November)
• RE: R18. User perceived latency of synthesis must be minimized (Monday, 8 November)
• RE: Text to Speech proposal (Friday, 5 November)

Last message date: Tuesday, 30 November 2010 12:49:16 UTC