Re: [w3ctag/design-reviews] Dusting off Web Speech API? (#214)

There are several issues with the current implementation of Web Speech API that have encountered; which can list here, if that contribution is welcome; in brief:

- SpeechRecognition
>From perspective here, the most egregious current issue is Chromium/Chrome recording the user and sending that recording to a remote server relevant to the browsers' implementation of `SpeechRecognition` https://bugs.chromium.org/p/chromium/issues/detail?id=816095. Not sure how to address that specification-wise other than to make it clear that the STT should occur within code shipped with the browser or not at all; not at a potentially undisclosed third-party external web service; where the service could very well be retaining and using users' recorded voices to further the parent company proprietary aims; without any compensation for the use of users' voice, if such retention and further use is occurring at all (silent as to that at the filed issue); while simultaneously marketing and promoting their "assistant"  service to compete with *mazon services.

- SSML parsing
Another issue is the implementation of SSML parsing, where the technological capability is present to achieve SSML parsing at the browser, though not implemented, for reasons attributed to other priorities. https://bugs.chromium.org/p/chromium/issues/detail?id=806592, https://bugs.chromium.org/p/chromium/issues/detail?id=88072, https://bugs.chromium.org/p/chromium/issues/detail?id=795371. 

- Web Platform Tests
And tests not being incorporated into WPT. The first of several which can include at WPT https://github.com/w3c/web-platform-tests/pull/9642, based on testing done while composing https://github.com/guest271314/SpeechSynthesisSSMLParser, when it became clear that SSML parsing was not a priority for Web Speech API implementation, while simultaneously a priority as to companies marketing products which do parse SSML as an external web service.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/214#issuecomment-380842375