Re: Speech input API proposal (from Google)


The Chrome team reviewed our speech input API proposal and based on
their feedback we have revised the first bullet in section 4
("Security and Privacy considerations") to the following:

1. User agents must only start speech input sessions with explicit,
informed user consent. User consent can include, for example:
  o  User clicks on a visible speech input element which has an
obvious graphical representation showing that it will start speech
  o  An upfront permission grant as part of the installation flow of
an installable web application or extension.
  o  Running in a trusted environment, e.g. such as a car information system.


On Mon, Feb 28, 2011 at 5:14 PM, Satish Sampath <> wrote:
> Hi all,
> I have attached the latest draft of our speech input API proposal with this mail. Please take a look and share your thoughts.
> The main additions since our previous proposal include methods for starting speech input from script, additional error codes and additional events fired at various stages of the session as brought up in the TPAC face-to-face discussions.
> Cheers
> Satish

Received on Friday, 4 March 2011 15:01:35 UTC