- From: Rain Michaels <rainb@google.com>
- Date: Thu, 15 Apr 2021 12:03:41 -0700
- To: Deborah Dahl <Dahl@conversational-technologies.com>
- Cc: Lisa Seeman <lisa1seeman@gmail.com>, public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>, Michael Cooper <cooper@w3.org>, Ruoxi Ran <ran@w3.org>, Rachael Bradley Montgomery <rachael@accessiblecommunity.org>
- Message-ID: <CAJO5HuuKZd_Pj-Csk6L+Tnh38Np-+jqee2vsMtAz=hOscNT2-g@mail.gmail.com>
+1 to Debbie's suggested updates On Thu, Apr 15, 2021 at 11:27 AM Deborah Dahl < Dahl@conversational-technologies.com> wrote: > HI Rain, > > Thank you for the clarification. That makes sense. How about this? I > think it captures the clarification. > > Debbie > > > > *Voice user interfaces (VUIs)* > > Sometimes known as: Conversational interfaces. > > Voice user interfaces (VUIs) allow the user to interact with a computer > system based on *audio input and/or output. Audio input can include > speech, non-speech vocalizations or audio produced by AAC or other devices.* > Audio-based interaction may include both input from the user, and output > from the system in response to the input. Examples include: Siri, Google > Assistant, and Alexa. > > > > *Interactive voice response (IVR)* > > Interactive voice response (IVR) systems allow the user to interact with > a computer system through the use of a telephone keypad *and/or audio > input. Audio input can include speech, non-speech vocalizations or audio > produced by AAC or other devices*. Interactive voice response systems > are often used to automate tasks by phone and in call centers. IVR systems > often use standards such as VoiceXML <https://www.w3.org/TR/voicexml20/>. > > > > > > *From:* Rain Michaels <rainb@google.com> > *Sent:* Thursday, April 15, 2021 12:24 PM > *To:* Deborah Dahl <Dahl@conversational-technologies.com> > *Cc:* Lisa Seeman <lisa1seeman@gmail.com>; public-cognitive-a11y-tf < > public-cognitive-a11y-tf@w3.org>; Michael Cooper <cooper@w3.org>; Ruoxi > Ran <ran@w3.org>; Rachael Bradley Montgomery < > rachael@accessiblecommunity.org> > *Subject:* Re: Responce needed. definitions for voice user interface and > Integrated Voice Menus > > > > Deborah, thank you for raising your questions. > > > > Thinking about the difference between speech and voice: an individual may > not be able to vocalize a sound that would be considered "speech," but > might be able to vocalize sounds that can still have meaning. Another > individual may not have the ability to make their own sounds, but might use > AAC or other sound outputs to provide responses. > > > > Do you have proposed rewording that might clarify points you raised? > > > > Thank you, > > > > Rain > > > > On Thu, Apr 15, 2021 at 8:42 AM Deborah Dahl < > Dahl@conversational-technologies.com> wrote: > > I’m still not clear what is the intention behind distinguishing “voice” > and “speech” in the VUI definition. The minutes say that “there is a reason > for having voice and speech”, but they don’t say what the reason is. > > Also, can we clarify, in ” voice, speech, or sound input”, what kind of > sound input is to be covered other than speech? Non-speech audio input > would be very unusual in an IVR. This is so unusual that I think it would > be confusing without an example. Conceivably, non-speech audio input could > be used in a music identification service, or a medical diagnosis system > that diagnoses illnesses from coughs. Are those the kinds of applications > that non-speech input is supposed to cover? > > > > *From:* Rain Michaels <rainb@google.com> > *Sent:* Thursday, April 15, 2021 11:15 AM > *To:* Deborah Dahl <Dahl@conversational-technologies.com> > *Cc:* Lisa Seeman <lisa1seeman@gmail.com>; public-cognitive-a11y-tf < > public-cognitive-a11y-tf@w3.org>; Michael Cooper <cooper@w3.org>; Ruoxi > Ran <ran@w3.org>; Rachael Bradley Montgomery < > rachael@accessiblecommunity.org> > *Subject:* Re: Responce needed. definitions for voice user interface and > Integrated Voice Menus > > > > Hello all, > > > > *(Please respond by tomorrow, April 16, 2021)* > > > > We tried to wrap this up on our call today, but a number of concerns were > brought up about the suggested revision, along with a concern that we were > leaving out important future proofing considerations in the first proposal. > > > > *This is high priority as we need to get our feedback in right away. *Please > take a minute to look at the proposed revision based on our conversation > during the meeting, and +1 if you agree so that Lisa can submit the > response. > > > > *Voice user interfaces (VUIs)* > > Sometimes known as: Conversational interfaces. > > Voice user interfaces (VUIs) allow the user to interact with a computer > system through voice, speech, and sound. This may include both input from > the user, and output from the system in response to the input. Examples > include: Siri, Google Assistant, and Alexa. > > > > *Interactive voice response (IVR)* > > Interactive voice response (IVR) systems allow the user to interact with > a computer system through the use of a telephone keypad and/or voice, > speech, or sound input. Interactive voice response systems are often > used to automate tasks by phone and in call centers. IVR systems often use > standards such as VoiceXML <https://www.w3.org/TR/voicexml20/>. > > > > Please send a +1 if you agree and can live with these changes. Send a -1 *along > with your reason and proposed correction* if you cannot. > > > > Thank you, > > > > Rain > > > > On Tue, Apr 13, 2021 at 12:56 PM Deborah Dahl < > Dahl@conversational-technologies.com> wrote: > > +1 but I would propose a couple of small edits – > > On VUI’s, I would just say “interact with a computer system through voice > input and output”, if by “voice” you mean “voice output”. > > On IVR, I would say “interact with a computer system through the use of a > telephone keypad and/or voice input” because IVR’s often support both > keypad and voice input. > > > > > > *From:* Lisa Seeman <lisa1seeman@gmail.com> > *Sent:* Tuesday, April 13, 2021 11:26 AM > *To:* public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>; Michael > Cooper <cooper@w3.org>; Ruoxi Ran <ran@w3.org>; Rachael Bradley > Montgomery <rachael@accessiblecommunity.org> > *Subject:* Responce needed. definitions for voice user interface and > Integrated Voice Menus > > > > Hi Folks > > > > We were asked to have references ordefinitions for voice user interface > and Integrated Voice Menus > > > > Can you let us know if you want changes to the following (+1 if you can > live it): > > > > *Voice user interfaces (VUIs) * > Sometimes known as: Conversational interfaces. > Voice user interfaces (VUIs) allow the user to interact with a computer > system through voice and speech recognition. Examples include: Siri, Google > Assistant, and Alexa. > > > > *Interactive voice response (IVR)* > > Interactive voice response (IVR) systems allow the user to interact with > a computer system through the use of a telephone keypad or voice and speech > recognition. Interactive voice response systems are often used to > automate tasks by phone and in call centers. IVR systems often use > standards such as VoiceXML <https://www.w3.org/TR/voicexml20/>. > > > > Please send your response by 11.30 am Boston time on the 15th April 2022. > Silence will be taken as an agreement. Minor edits may continue. > > > > All the best > > Lisa > >
Received on Thursday, 15 April 2021 19:04:32 UTC