Raised by: Dominic in mail.
Discussion: Dominic: The spec for both reco and TTS now allow the user to specify a service URL. Could you clarify what the value would be if the developer wishes to use a local (client-side) engine, if available? Some of the spec seems to assume a network speech implementation, but client-side reco and TTS are very much possible and quite desirable for applications that require extremely low latency, like accessibility in particular. Is there any possibility the spec could specify how a user agent could choose to offer local TTS and reco, or to give the user or developer a choice of multiple TTS or reco engines, which might be local or remote?
Michael: The serviceURI does not need to be remote. We've discussed that in the group. We should add clarifying text specifying this.
Resolution: Add clarification that serviceURI can point to local services. UA defaults can be local (and can allow user cpoice even).