[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

speech recognition air and apology with long-winded explanation Re: [Acc

From: Eric S. Johansson
Subject: speech recognition air and apology with long-winded explanation Re: [Accessibility] Call to Arms
Date: Wed, 28 Jul 2010 18:28:46 -0400
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20100713 Thunderbird/3.1.1

 On 7/28/2010 5:22 PM, Eric S. Johansson wrote:

I don't believe I was arguing against your goals. I was arguing against your lack of path to them or choices of innocence but I'll respect your request to express things in a more constructive fashion. I will try to find a better way to point out when you are on a potential path to failure like you are now as well as potential paths to success.

bloody recognition errors

choices of innocence was a misrecognition. I can't remember what I was saying but is probably something about lack of compassion to the disabled or putting concern for the disabled first. I'm only guessing because I really don't remember. Illustrates the need for a significant audio log in conjunction with application use with speech recognition and content spoken. You see, we're talking about is seriously different environment than the classic GUI. Can you imagine instant messenger/IRC environment where you go back in time to correct a line? You need to do that if using speech recognition to fix mistakes. Let them implies others have the right to go back and change what they said in response to your correction thereby erasing whole sequences of writing from the memory of channel. Very cool user interface/user interaction. Gives you a chance to retract a statement and make an apology thereby creating a chain where communications that may have been close by anger/testosterone can be reopened and the harsh bits are expunged. Imagine the same thing applied to e-mail. That the sender can send a second message to overwrite the first while leaving an audit trail. That's very cool in my book. It's constructive social engineering. It's also cool way to sneak in cryptography.

the error above highlights one of the problems with speech recognition, you can get a statement which sounds completely correct[1] but is not what the person said giving an entirely wrong impression. The biggest errors I'm finding here are on vacation, wrong verb tense, and a version of sense (negation, and inversion of sense (sentence meaning).

--- eric

[1] in NaturallySpeaking the word correct is used to invoke of right correction sequences. So if you say something like completely correct but not what the person said and put a space after correct, the subsequent phrase is used as a search key. Very annoying and yet another reason why short phrases are bad

I'm sure there are other misrecognition errors lurking in my text

reply via email to

[Prev in Thread] Current Thread [Next in Thread]