Posted By:
Unknown
on Tuesday, May 28, 2013
A
Voice Browser is a "device which interprets a (voice) markup language and
is capable of generating voice output and/or interpreting voice input, and
possibly other input/output modalities." The definition of a voice
browser, above, is a broad one. The fact that the system deals with speech is
obvious given the first word of the name, but what makes a software system that
interacts with the user via speech a "browser"? The information that
the system uses (for either domain data or dialog flow) is dynamic and comes
somewhere from the Internet. From an end-user's perspective, the impetus is to
provide a service similar to what graphical browsers of HTML and related
technologies do today, but on devices that are not equipped with full-browsers
or even the screens to support them. This situation is only exacerbated by the
fact that much of today's content depends on the ability to run scripting
languages and 3rd-party plug-ins to work correctly.
Much
of the efforts concentrate on using the telephone as the first voice browsing
device. This is not to say that it is the preferred embodiment for a voice
browser, only that the number of access devices is huge, and because it is at
the opposite end of the graphical-browser continuum, which high lights the
requirements that make a speech interface viable. By the first meeting it was
clear that this scope-limiting was also needed in order to make progress, given
that there are significant challenges in designing a system that uses or
integrates with existing content, or that automatically scales to the features
of various access devices.
0 comments:
Post a Comment