W3C home > Mailing lists > Public > public-speech-api@w3.org > May 2012

RE: Revised SpeechRecognitionResult

From: Young, Milan <Milan.Young@nuance.com>
Date: Wed, 30 May 2012 15:16:23 +0000
To: Satish S <satish@google.com>
CC: Hans Wennborg <hwennborg@google.com>, "public-speech-api@w3.org" <public-speech-api@w3.org>
Message-ID: <B236B24082A4094A85003E8FFB8DDC3C1A45D952@SOM-EXCH04.nuance.com>
A "dumb" interface is one that withholds functionality, and yes, we want to avoid that.  We want an interface that is both intuitive and minimizes boilerplate syntax, hence my suggestion.

From: Satish S [mailto:satish@google.com]
Sent: Wednesday, May 30, 2012 7:43 AM
To: Young, Milan
Cc: Hans Wennborg; public-speech-api@w3.org
Subject: Re: Revised SpeechRecognitionResult

I'd argue that 90% of developers will not even think about the second item on the nbest list.  So why complicate their mental model let alone syntax with SpeechRecogntionAlternatives?

In another thread you mentioned "I want to be careful not to dumb it down to the point where we impact the mainstream speech industry". The above statement seems to contradict that. We should realise developers are smart and would have no problem understanding speech primitives. Also I don't understand how adding more attributes for accessing the same data and making an API with a larger surface area simplifies the mental model for developers.

This is similar to the proposal for adding emmaXml and emmaText - where the suggestion is to just add emmaXml and let developers generate the text format if required. Lets not add multiple attributes for accessing the same data.

Received on Wednesday, 30 May 2012 15:17:00 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:02:26 UTC