Confirmed users
24
edits
No edit summary |
|||
| Line 5: | Line 5: | ||
*Speech Input API | *Speech Input API | ||
*Text to Speech API | *Text to Speech API | ||
== 1.Speech Input API == | == 1.Speech Input API == | ||
| Line 17: | Line 15: | ||
*A streaming API to asynchronously stream microphone data to a speech recognition server and to get the results back. This will be similar to how XMLHttpRequest is implemented. The api should be able to support both local and remote engines or a combination of both depending on the network connection available. | *A streaming API to asynchronously stream microphone data to a speech recognition server and to get the results back. This will be similar to how XMLHttpRequest is implemented. The api should be able to support both local and remote engines or a combination of both depending on the network connection available. | ||
==== | ==== Security/Privacy issues ==== | ||
*A speech input session should be allowed only with the user's consent. This could be provided using a doorhanger notification. | *A speech input session should be allowed only with the user's consent. This could be provided using a doorhanger notification. | ||
*The user should be notified when audio is being recorded possibly using a record symbol somewhere in the web browser UI itself like the URL bar or status bar. | *The user should be notified when audio is being recorded possibly using a record symbol somewhere in the web browser UI itself like the URL bar or status bar. | ||
==== | ==== API Design - ==== | ||
The API will look like the interface described in the SpeechRequest proposal. | The API will look like the interface described in the SpeechRequest proposal. | ||
| Line 31: | Line 29: | ||
*The developer should be able to start, stop, handle errors and multiple requests as required. | *The developer should be able to start, stop, handle errors and multiple requests as required. | ||
== | == 2.Text To Speech API == | ||
The text to speech API will be based on google's proposal(http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Feb/att-0022/htmltts-draft.html).This API can be used for speech translation, turn by turn navigation, dialog systems etc. | The text to speech API will be based on google's proposal(http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2011Feb/att-0022/htmltts-draft.html).This API can be used for speech translation, turn by turn navigation, dialog systems etc. | ||
| Line 42: | Line 40: | ||
*The API should itself be independent of the underlying speech synthesizer. If speech synthesis is not supported, appropriate text should be displayed. <br> | *The API should itself be independent of the underlying speech synthesizer. If speech synthesis is not supported, appropriate text should be displayed. <br> | ||
*What speech engines is yet to be decided. | *What speech engines is yet to be decided. | ||
==Additional Resources== | |||
===Demos and Examples=== | |||