Re: Additional parameters to SpeechRecognition (was "Speech API: first editor's draft posted")

On Fri, Apr 27, 2012 at 8:02 PM, Jerry Carter <jerry@jerrycarter.org> wrote:

> I'm inclined to agree with you on #4.
>
> Assuming that the audience is primarily individuals with limited
> experience building speech applications, simplicity is admirable.  My
> experience has been that for the vast majority of cases, the recognition
> scores are bimodal (i.e. very high or very low).  Intermediate values are
> of limited utility outside of application development teams within
> recognition vendors and experienced speech applications teams.  This does
> not mean that recognition thresholds are useless, because they aren't.  A
> talented and experienced speech scientist can optimize settings to tailor
> the 'false acceptance' / 'false rejection' rates according to satisfy
> business objectives, but in most cases, the cost of doing so is not
> justified.  Providing an outlet such as a custom parameter seems
> appropriate for a first version.
>

+1 to that.