Much of the efforts concentrate on using the telephone as the first voice browsing device. 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. 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. The information that the system uses (for either domain data or dialog flow) is dynamic and comes somewhere from the Internet. 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"?
0 Comments
Leave a Reply. |