A METHOD AND SYSTEM FOR VOICE ACTIVATING WEB PAGES

Abstract: A method for providing a web page having an audio interface. The method including providing data specifying a web page, including in the data a first rule based grammar statement having a first phrase portion, a first command portion and a first tag portion, and including in the data a second rule based grammar statement having a second phrase portion, a second command portion, and a second tag portion.

Description: A METHOD AND SYSTEM FOR VOICE ACTIVATING WEB PAGES SPECIFICATION CROSS-REFERENCE TO RELATED APPLICATION This application claims priority based on U.S. Provisional Patent Application entitled "Hyper-Speech Markup Language/Hyper-Noice Markup Language (HSML/HVML), A Technology for Voice Activating Visual Web Pages," Serial No. 60/250,809, which was filed on December 1, 2000. BACKGROUND OF THE INVENTION Over the past decade Automated Speech Recognition (ASR) systems have progressed to the point where a high degree of recognition accuracy may be obtained by ASR systems installed on moderately priced personal computers and workstations. This has led to a rise in the number of ASR systems available for consumer and industry applications. ASR systems rely on voice grammars to recognize vocal commands input via a microphone and act on those commands. Voice grammars fall into two categories: rule based grammars and free speech grammars. Rule based grammars allow the recognition of a limited set of predefined phrases. Each rule based grammar, if invoked, causes an event or set of events to occur. A rule based grammar is invoked if an utterance, input via a microphone, matches a speech template corresponding to a phrase stored within the set of predefined phrases. For example the user may say "save file" while editing a document in a word processing program to invoke the save command. On the other hand, free speech grammars recognize large sets of words in a given domain such as Business English. These grammars are generally used for dictation applications, some examples of these systems are Dragon Naturally Speaking and IBM Viavoice 7 Millennium. ASR systems have also incorporated text to speech (TTS) capabilities which enable ASR systems to speak graphically rendered text using a synthesized voice. For example, an ASR system can read a highlighted paragraph within a word processor aloud through speakers. ASR systems have been integrated with web browsers to create voice enabled web browsers. Voice enabled web browsers allow the user to navigate the Internet by using voice commands which invoke rule based grammars. Some of the voice commands used by these browsers include utterances that cause the software to execute traditional commands used by web browsers. For example if the user says "home" into a microphone, a voice enabled browser would execute the same routines that the voice enabled web browser would execute if a user clicked on the "home" button of the voice enabled web browser. In addition, some voice enabled web browsers create rule based grammars based on web page content. As a web page is downloaded and displayed some voice enabled web browsers create rule based grammars based on the links contained within the web page. For example, if web page displayed a link "company home," such a voice enabled web browser would create a rule based grammar, effective while the web page is displayed, such that if a user uttered the phrase "company home" into a microphone the voice enabled web browser would display the web page associated with the link. One shortcoming of this approach is that the rules generated from web page content are fixed over long periods of time because web pages are not redesigned often. Additionally, the rule based grammars are generated from web page content, which is primarily intended for visual display. In effect, these systems limit the user to saying what appears on the screen. Web pages can also incorporate audio elements, which cause sound to be output. Currently web pages can incorporate audio elements into their web pages in two ways. The first way to incorporate an audio element is to use audio wave file content to provide a human sounding voice to a web page. Using audio wave files allows the web page designer to design the visual and audio portions of the web page independently, but this freedom and added functionality comes at a high price. The bandwidth required to transfer binary sound files over the Internet to the end user is large. The second way to incorporate an audio element is to leverage the functionaUty of an ASR system. Voice enabled web browsers may utilize the TTS functionality of an ASR system in such a way as to have the computer "speak" the content of a web page. Using this approach causes the bandwidth needed to view the page with or without the audio element be approximately the same but Hmits the subject matter of what the web browser can speak to the content of the web page. Voice XML (VXML) affords a web page designer with another option. VXML allows a user to navigate a web site solely through the use of audio commands typically used over the phone. VXML requires that a TTS translator read a web page to a user by translating the visual web page to an audio expression of the web page. The user navigates the web by speaking the links the user wants to follow. With this approach a user can navigate the Internet by using only the user's voice, but the audio content is typically generated from web page content that is primarily designed for visual interpretation; and the visual interface is removed from the user's experience. Accordingly, there exists a continuing need to independently create an audio component of a web page that does not demand a large amount of transmission bandwidth and exists in conjunction with the visual component of a web page. SUMMARY OF THE INVENTION The present invention in one aspect is a method for creating an audio interface for a visual web page. In accordance with a first exemplary embodiment of the method of the present invention, there is provided a method for providing a web page having an audio interface, including providing data specifying a web page; including in the data a first rule based grammar statement having a first phrase portion, a first command portion and a first tag portion; and including in the data a second rule based grammar statement having a second phrase portion, a second command portion, and a second tag portion. According to a second exemplary embodiment of the method of the present invention, a method for receiving a web page having an audio interface, including receiving data specifying a web page, the data including a first rule based grammar statement having a first phrase portion, a first command portion and a first tag portion, and a second rule based grammar statement having a second phrase portion, a second command portion, and a second tag portion; storing at least a portion of the first rule based grammar; storing at least a portion of the second rule based grammar; providing the data specifying the web page to a web browser; providing the first phrase portion and the first tag portion as a first recognition grammar to an automated speech recognition engine; and providing the second phrase portion and the second tag portion as a second recognition grammar to the automated speech recognition engine. In another aspect of the present invention there is provided a system for receiving a web page having an audio interface. According to an exemplary embodiment of the system of the present invention, there is provided a first input for receiving data specifying a web page, the data including a first rule based grammar statement having a first phrase portion, a first command portion, and a first tag portion, and including a second rule based grammar statement having a second phrase portion, a second command portion, and a second tag portion; a database for storing at least a portion of the first rule based grammar statement and for storing at least a portion of the second rule based grammar statement; a web browser for receiving the data specifying the web page; and an automated speech recognition engine for receiving the first phrase portion and the first tag portion as a first recognition grammar, and for receiving the second phrase portion and the second tag portion as a second recognition grammar. BRIEF DESCRIPTION OF THE DRAWINGS Further objects, features, and advantages of the invention will become apparent from the following detailed description taken in conjunction with the accompanying figures showing illustrative embodiments of the invention, in which: FIG. 1 is a block diagram illustrating a prior art system; FIG. 2 A is a flow chart illustrating a process of web page content generation in accordance with the present invention; FIG. 2B is a block diagram of a hyper-speech markup language (HSML) enabled web browser system in accordance with the present invention ; FIG. 3 A is a flow chart illustrating a thread that monitors messages sent to a particular port of a computer in accordance with the present invention; FIG. 3B is a table illustrating the conditions under which a header, boundary, or footer are appended or prepended to the data received from the web server in accordance with the present invention; FIG. 4 is a flow chart illustrating a thread that receives data from the web browser and data sent to the web browser associated with web pages which were invoked by the web browser in accordance with the present invention; FIG. 5 is a flow chart illustrating a thread which is the method through which the HSML engine reacts to receiving an array of tags from the ASR engine in accordance with the present invention; FIG. 6 is a flow chart illustrating a thread that receives sub-rule tags from the ASR engine and data sent to the web browser associated with web pages which were invoked by the ASR engine in accordance with the present invention; FIG. 7 is a flow chart illustrating a process for of creating, storing and transrmtting rule based grammars and TTS grammars in accordance with the present invention; FIG. 8 is a flow chart illustrating a process for parsing block-sets of hyper-speech markup language grammars in accordance with the present invention; FIG. 9 is a flow chart illustrating a process for parsing blocks of hyper- speech markup language grammars in accordance with the present invention; FIG. 10 is a flow chart illustrating a process for parsing hyper-speech markup language text-to-speech grammars in accordance with the present invention; FIG. 11 is a flow chart illustrating a process for parsing hyper-speech markup language rule based grammars in accordance with the present invention; Throughout the figures, unless otherwise stated, the same reference numerals and characters are used to denote like features, elements, components, or portions of the illustrated embodiments. Moreover, while the subject invention will now be described in detail with reference to the figures, and in connection with the illustrative embodiments, various changes, modifications, alterations and substitutions to the described embodiments will be apparent to those skilled in the art without departing from the true scope and spirit of the subject invention as defined by the appended claims. DETAILED DESCRIPTION OF THE INVENTION FIG. 1 illustrates a prior art system 100 for viewing and interacting with web pages stored on a web server 102. The web server 102 including a CPU 104, a network interface 106, and a data storage unit 108 is provided. The data storage unit 108 contains information describing one or more web pages. A network connection 109 connects the web server 102 to a communications network 110 via the network interface 106 allowing the web server 102 to communicate with other devices on the communications network 110. hi a certain embodiment, the communications network 110 is the Internet. A client computer 120 including a CPU 122, a network interface 124, and a data storage unit 126 is provided. In a certain embodiment, the data storage unit 126 can be memory. A network connection 111 connects the client computer 120 to the communications network 110 via the network interface 124 allowing the client computer 120 to communicate with other devices, on the communications network 110. The client computer 120 is also connected to various input / output devices such as a keyboard 128, a mouse 136, a microphone 130, a speaker 132, and a display 134 typically through a system bus 138. A personal digital assistant (PDA) 140, including a CPU 142 and a memory 144, is also provided. The PDA 140 is connected to and can communicate with other devices on the communications network 110 over a network connection 148, through a network interface 146. In order to view a web page a user opens a web browser, stored in a data storage unit in a computer or a memory in a PDA, for example the data storage unit 126 in the client computer 120. Once the web browser is open the user may key in a universal resource locator (URL) which causes the client computer 120 to issue a request over the communications network 110 for the data files describing the contents of the web page identified by the URL. A web server, which stores the data files for the web page identified by the URL, for example the web server 102, receives the request and sends the client computer 120 the data files which describe the contents of the web page. The data files may include hyper-text markup language (HTML) files, active server pages files, sound files, video files, etc. The web browser then displays the web page and plays any video or audio files on the client computer 120 as specified by the markup language. The markup language specifies where and when to place or play text, video, or audio content. FIG. 2A depicts a process 200 for designing a web page. The process 200 begins with a web page designer executing a web page design tool at step 202. The web page design tool assists the web page designer during the process of designing a web page. The web page design tool allows the web page designer to specify elements of the web page at a high level, then generates low level markup language based on the specified elements of the web page. The web page designer begins designing and testing the visual portion of a web page at step 204. If the visual portion of the web page already exists and does not need to be updated, the process 200 advances directly to step 206. Designing and testing the visual portion of the web page is well known in the art. After the visual portion of the web page is designed and tested, the process block 206 is executed. At step 206, the process of designing and testing an audio portion of the web page takes place. The web page designer may add hyper-speech markup language (HSML) to the web page markup language to augment the visual portion of the web page with an audio component. The web page designer may add HSML directly or specify it at a high level using a web page design tool. If the audio portion of the web page already exists and does not need to be updated, the process 200 advances directly to step 208. At step 208, the web pages can be made available to users connected to the communications network 110. Once the web pages are made available to the public, the process 200 ends. In an alternate embodiment, the audio portion of the web page could be designed before the visual portion of the web page is designed. In another alternate embodiment, the audio and visual portions of the web page could be designed at the same time. In yet another alternate embodiment, the audio and visual portions of the web page could be designed in lock step with each other. In an alternate embodiment, the audio and visual portions of the web page may be generated by a common gateway interface. According to the present invention, HSML specifies speech recognition rule based grammars and TTS grammars for the web page. Speech recognition rule based grammars allow the recognition of a limited set of predefined speech phrases input to the computer through a microphone or the hke which in turn invoke an event or set of events. TTS grammars define text that can be output as audible content through speakers associated with the computer displaying a web page. HSML rule based grammars may be related to, but need not be the same as, the text which appears on the screen. If HSML rule based grammars are added to the markup language of a web page that is displayed on the screen, users may speak about the text displayed on the screen rather then simply speaking the text, displayed on the screen, itself. A first exemplary HSML rule based grammar follows: <hsml:JSGFRule href="httρ:// www.columbia.edu" tag="reload" ID = "reload"><! [CD ATA[ public <reload> = ( reload ) {reload} ]] <hsml: JSGFRule>. The first exemplary HSML rule based grammar defines a command, "http://www.columbia.edu", to be executed if a speech phrase input to the computer matches the phrase "reload." Each HSML rule based grammar has three portions which can be configured: the command portion, the tag portion, and the phrase portion. The command portion defines the command to be executed once the HSML rule based grammar is invoked. In the first exemplary HSML rale based grammar, the command portion is as follows: href="http:// www.columbia.edu". The command for the first exemplary HSML rule based grammar is "http://www.columbia.edu". The tag portion defines a unique way of identifying the particular HSML rule based grammar rule. In the first exemplary HSML rule based grammar, the tag portion is as follows: tag="reload". The tag for the first exemplary HSML rule based grammar is "reload". The phrase portion defines the set of phrases that will invoke the HSML rule based grammar. In the first exemplary HSML rule based grammar, the phrase portion is as follows: "CDATA[ public <reload> = ( reload ) {reload}". The phrase for the first exemplary HSML rule based grammar is "reload". Another, more complicated, set of HSML rule based grammars is as follows: <hsml:block> <hsml:JSGFRule href=="http://www.columbia.edu/scripts/cgi test.cgi" tag="examprep" ID = "examprep"x![CDATA[public <examprep> = [please] (go to | example) ( <rad> | <lab> ) report {examρrep};]]x/hsml:JSGFRule> <hsml: JSGFRule tag="RAD"x![CDATA[public <rad> = radiology {RAD};]]> </hsml: JSGFRule> <hsml: JSGFRule tag = "LAB"><! [CDATAfpublic <lab> = (laboratory ] chemistry) {LAB } ;]]x/hsml: JSGFRule> </hsml:block>. This grammar provides a nested set of rules. This HSML rule based grammar defines a set of commands, one of which will be executed if a speech phrase input to the computer matches an associated one of a set of phrases. The top level command is defined by the HSML rule "<hsml:JSGFRule href="http://www.columbia.edu/scripts/cgi/test.cgi" tag="examprep" ID = "examprep"> <![CDATA[public <examprep> = [please] (go to | example) ( <rad> | <lab> ) report {examprep};]]x/hsml:JSGFRule>", which defines the set of phrases and the top level command "http://www.columbia.edu/scripts/cgi test.cgi" . The set of phrases is defined by the following portion of the phrase portion of the second exemplary HSML rule based grammar: [please] (go to | example) ( <rad> I <lab> ). The phrase starts off with the word "please" within square brackets. A word within square brackets denotes an optional word. The rale will be invoked whether or not the speech phrase begins with the word "please." The optional "please" is followed by (go to | example). The parentheses group words together. The words "go to" and "example" are separated by an "|" symbol. The "I" symbol is an "OR" symbol, which indicates that either "go to" or "example" may be used to invoke the rale. Therefore the optional word "please" must be followed by "go to" or "example" to invoke this HSML rale. The mandatory words "go to" or "example" are followed by ( <rad> | <lab> ). This portion of the phrase contains variables. The variables are defined in sub- rales elsewhere within the HSML block. The variable <rad> is defined by the sub-rule <hsml: JSGFRule tag="RAD"x![CDATA[public <rad> = radiology {RAD};]]> </hsml: JSGFRule>. Therefore the variable <rad> is defined as radiology. If the word "radiology" follows either "go to" or "example," a separator, here an "?", is concatenated onto the top level command then the sub-rule tag RAD is concatenated onto the top level command, such that the command becomes "http://www.columbia.edu/scripts/cgi test.cgi7RAD". In an alternate exemplary embodiment, the separator can be a "/". The variable <lab> is defined by the sub-rule <hsml: JSGFRule tag = "LAB"> <![CDATA[ public <lab> = (laboratory | chemistry) {LAB};]]x/hsml:JSGFRule>. The variable <lab> is defined as "laboratory" or "chemistry." If the word "laboratory" or "chemistry" follows either "go to" or "example," a separator, here an "?", is concatenated onto the top level command then the sub-rale tag LAB is concatenated onto the end of the top level command, such that the command becomes "http://www.columbia.edu/ scripts/ cgi/test.cgi examprep?LAB". TTS grammars define text which can be output as synthetic speech through speakers. One such HSML TTS grammar is as follows: <hsml: JSML> <! [CDATA[ reloading ]]> </hsml: JSML>. This TTS grammar provides for outputting the phrase "reloading" as synthetic speech through speakers. The TTS grammar can be invoked when an HSML rale based grammar is invoked, when a page is loaded, when a web site is loaded, when a page is exited, or when a web site is exited. FIG. 2B illustrates a functional block diagram of a system 200 for viewing and interacting with web pages having HSML content. In order to view a web page having HSML content, a user can execute an HSML processor 254, which in turn executes a web browser 256 and an ASR engine 258 on the computer 120. The HSML processor 254 acts as a proxy for the web browser 256. The web browser 256 should have all caching disabled and should support x-mixed replace markup. In an exemplary embodiment, the web browser 256 can be Netscape Navigator. In the present exemplary embodiment the ASR engine 258 can be IBM Viavoice Version 7 Millennium. Other ASR engines that conform to the Java Speech Application Program Interface standard may also be substituted for IBM Viavoice Version 7 Millennium. In a certain embodiment, a script can be used to executed the HSML processor 254 and the web , browser 256 individually. In an alternate embodiment, the web browser 256 can be Microsoft Internet Explorer. In another alternate embodiment, the HSML processor 254 communicates with the web browser 256, such that x-mixed replace markup is not needed to convey control information. A visual monitor may also be included with the voice enabled browser. The visual monitor aids in the user's interaction with voice activated pages. The visual monitor advantageously includes a status bar displaying an output audio level, an input audio level, a speech engine status indicator, a speech synthesis indicator, a rale identifier, a data status indicator, an error indicator, a page grammar active line, an active grammars area, etc. This allows the user to receive feedback as to how or why his or her speech is or is not recognized. The visual monitor can be implemented in a window separate from the browser or it can be integrated as part of the browser itself. This monitor extends the browser media environment from a graphical and text content environment to a cross platform, dynamically generated, graphical, text and voice interactive environment. The output audio level informs the user of the setting of the output volume. The input audio level indicates the current volume of the user's voice as the user speaks into the microphone 130 (shown in Fig. 1). The speech engine status indicator informs the user as to the status of the HSML processor 254. The HSML processor 254 can be hstening, sleeping or off. If the HSML processor 254 is listening, it is accepting all system and page commands. If the HSML processor 254 is sleeping, it is waiting for a specific system command "wake up" to activate the HSML processor 254 which will cause the speech engine status indicator to change to listening. If the HSML processor 254 is off, no speech commands are accepted. The speech synthesis indicator informs the user whether the HSML processor 254 will react to the HSML TTS grammars associated with the active web page and the system commands, only the system speech output commands, or no speech output commands. The rule identifier displays an invoked HSML rule for a short time after the HSML grammar has been invoked. The data status indicator informs the user whether the HSML processor 254 is loading data, whether the HSML processor 254 is loading speech data, whether the HSML processor 254 has already loaded the visual portion of the web page, or whether the HSML processor 254 has already loaded the web page and speech data. The error indicator informs the user of any error that have been detected by the HSML processor 254. The page grammar active line informs the user whether a current page grammar exists and is active. The active grammars area lists the HSML grammar rales that are currently active up to a certain maximum number of HSML grammars. The appearance of these rules in the active grammars area allows users to easily understand the function and layout of a page. The entire sets of rules for large rale sets do not need to be displayed in their entirety. A graphical menu does not need to name every HSML rule or HSML rule based grammar. The individual HSML rules or the HSML grammars can indicate the importance level for each rule or grammar such that the visual monitor can intelligently select which rules and grammars are important and should be displayed. When a rale is displayed, the display shows the phrase or phrases that would invoke the rule. For example, if the HSML rule based grammar <hsml:block> <hsml:JSGFRule href="http:// www.columbia.edu " tag="reload" ID = "reload"x! [CDATA[ public <reload> = ( reload ) {reload} ]] </hsml: JSGFRule></hsml:block> was displayed, the display would show the phrase "reload" . If more than one phrase could invoke the HSML rule based grammar, the display shows all the phrases that could invoke the HSML rule based grammar. In an alternate embodiment, the display shows the phrases that could invoke the HSML rule based grammar, but does not display optional words. For example, if the phrase "please reload" invoked an HSML rule based grammar, but the word please was optional, the display would only display the phrase "reload", not "please reload" and "reload". In an alternate embodiment, the HSML processor 254 can be executed separately from the web browser 256, and can interact with a web browser that is already running. A request for a web page may be initiated by the ASR engine 258 in conjunction with the HSML processor, or the web browser 256. If the ASR engine 258 initiates the request, at least one speech recognition rule based grammar will have been invoked in the ASR engine 258. The ASR engine 258 transmits an array of tags to the HSML processor 254, which in turn issues a request to the web server 102 (shown in Fig. 1). This process is shown in more detail in FIGs. 3A, 3B and 5. Referring to Fig. 2B, the web browser 256 initiates the request, it transmits the URL to the HSML processor 254. The HSML processor 254 receives the URL from the web browser 256 and issues a request to the web server 102 (shown in Fig. 1). This process is shown in more detail in FIGs. 3 A, 3B and 4. The computer 120 (shown in Fig. 1) receives a response to the request issued by the HSML processor 254 in the form of data representing the web page corresponding to the URL. The computer 120 communicates the data, including markup data, representing the web page corresponding to the URL to the HSML processor 254. The HSML processor 254 processes the markup data and creates, stores and transmits to the ASR engine 258 the rule based grammars and TTS grammars based on the markup data. The process of creating, storing and sending rule based grammars and TTS grammars is described in more detail below in reference to FIGs. 3 A and 3B. In an alternate embodiment, the functionality of the HSML processor 254 may be incorporated into the web browser 256. In another alternate embodiment, the functionality of the HSML processor 254 may be incorporated into the web browser 256 as a module or subroutines. In yet another alternate embodiment, the functionality of the ASR engine 258 may be incorporated into the web browser 256. FIG. 3 A illustrates a thread 300 that monitors messages sent to a particular port of a computer. A thread is not an independent process, but is a thread of execution that belongs to a particular process; here the thread 300 belongs to the HSML processor 254. A single process may have multiple threads. The thread 300 monitors the particular port for a new connection from either the web browser 256 or a thread 400 of the HSML processor 254, shown in Fig. 5. Once the thread 300 receives the new connection from either the web browser 256 or the thread 500, the thread 300 determines whether the new connection includes a data stream. If the new connection includes a data stream, the thread 300 reads the server address from the data stream and issues a request to the web server 102 (shown in Fig. 1). After the request is issued, the thread 300 waits for Hie data describing the web page from the web server. If the thread 300 receives data from the web server, the thread 300 processes the data extracting any HSML grammars and transmitting the data to the web browser 256. The thread 300 begins at step 302 where the thread 300 initializes a recognizer, a temporary variable PREV_VOICE and a temporary variable CUR_VOICE. The thread 300 uses a class library called International Business Machines Java Speech Library (IBMJS Library), version 1.0, which is an implementation of the Java Speech Application Program Interface standard, to interface with the ASR engine 258. In an alternate embodiment, the thread 300 may^se a class library other than IBMJS to communicate with the ASR engine. Other class libraries that conform to the Java Speech Application Program Interface standard may also be substituted for the IBMJS Library. The thread 300 initializes the recognizer using the method createrecognizer of a class used to implement the IBMJS Library interface Recognizer. After the recognizer is initialized, the temporary variable PREV VOICE is initialized to FALSE, and the temporary variable CUR_VOICE is initialized to FALSE. Once the temporary variables are initialized the thread 300 advances to step 304. At step 304, the thread 300 waits for a new connection from the web browser 256 (shown in Fig. 2B) or a thread 500 (shown in Fig. 5). The thread 500 is described in greater detail in relation to FIG. 5. The new connection received by the thread 300 will be a data stream. Once the thread 300 receives a new connection from the web browser 256 or the thread 500, the thread 300 advances to step 306. At step 306, the thread 300 determines if it has received any data from the new connection. If the thread 300 has received data, the thread 300 advances to step 308. If the thread 300 has not received data, the thread 300 advances to step 304. At step 308, the thread 300 sets a temporary variable DNSTR_COMP to an appropriate value. The temporary variable DNSTR__COMP should be set equal a value representing the socket associated with the web browser 256 or the thread 500 that initiated the new connection with the thread 300. Having the value of the socket associated with the initiator of the new connection with the thread 300 allows the thread 300 to transmit data to and read data from the initiator of the new connection. Once the temporary variable DNSTR_COMP is set, the thread 300 advances to step 312. At step 312, the thread 300 disables the current rule based grammars and TTS grammars within the ASR engine 258 (shown in Fig. 2B). Rule based grammars that are associated with any web page and specified in the ASR engine 258 are disabled using a method deleteRuleGrammar of the instance recognizer of a class implementing the IBMJS Library interface Recognizer. Once the existing grammars are disabled, the thread 300 advances to step 314. At step 314, the server address is read from the data stream received by the thread 300 during the new connection. After the server address is read from the data stream, the thread 300 formats and issues a connection request to the web server 102 (shown in Fig. 1) specifying the server address. Once the request is sent to the web server 102, the thread 300 advances to step 316. At step 316, the thread 300 begins the parallel execution of a separate thread 400 of the HSML processor 254. The thread 400 is described in greater detail with reference to FIG. 4. As the thread 300 begins the execution of the thread 400, the thread 300 passes the server name read from the data stream to the thread 400. Once the server name is passed to the thread 400, the thread 300 advances to step 318. At step 318, the thread 300 determines whether the connection to the web server 102 (shown in Fig. 1) is open, h order to read from the web server 102 the connection has to be open. The thread 300 performs a read from the eb server 102. If an error is returned, the connection is closed; otherwise the connection is open. If the connection to the web server is open, the thread 300 advances to step 320. If the connection to the web server is not open, the thread 300 advances to step 304. At step 320, the thread 300 performs a read from the web server 102 (shown in Fig. 1). The thread 300 receives the data describing the requested web page during the read from the web server 102. Once the thread 300 performs the read from the web server 102, the thread 300 advances to step 322. At step 322, the thread 300 appends or prepends the appropriate header, boundary, or footer to the data read from the web server 102 and sends the information including an appropriate header, boundary or footer to the socket defined by the temporary variable DNSTR_COMP. The conditions under which the thread 300 appends or prepends a header, boundary, or footer are graphically illustrated in a table 350 illustrated in FIG. 3B. Referring to FIG. 3B, the table 350 includes a group of columns: a current page column 352, a previous page column 354, a current page initiation column 356, a first directive column 358, a second directive column 360, and an append/prepend column 361. The table 350 also includes a group of entries: a first entry 362, a second entry 364, a third entry 366, a fourth entry 368, a fifth entry 370, a sixth entry 372, a seventh entry 374, and an eighth entry 376. The entries in the current page column 352 can be either a Yes or a No. Having a Yes in the current page column 352 indicates that the current page includes at least one HSML grammar. Having a No in the current page column 352 indicates that the current page does not include any HSML grammars. The entries in the previous page column 354 can be either a Yes or a No. Having a Yes in the previous page column 354 indicates that the previous page includes at least one HSML grammar. Having a No in the previous page column 354 indicates that the previous page does not include any HSML grammars. The entries in the current page initiation column 356 can be either Voice or Mouse Click. Having Voice in the current page initiation column 356 indicates that the current page was initiated by a grammar rale. Having Mouse Chck in the current page initiation column 356 indicates that the current page was initiated by a mouse chck. The entries in the first directive column 358 and the second directive column 360 can have values equal to Header, Boundary, Footer, Close Socket, and Nothing. Each value stored in the first directive column 358 and the second directive column 360 indicate a particular directive that the thread 300 must transmit to the downstream component specified by the temporary variable DNSTR_COMP. The directive specified in the first directive column 358 should be transmitted before the directive specified in the second directive column 360. For example, the first entry 362 indicates that if the current page has a grammar, the previous page has a grammar and the current page was initiated by voice, a boundary then nothing should be appended to the data before it is transmitted to the downstream component specified by the temporary variable DNSTR COMP. A header, as specified in the first directive column 358 of the second entry 364, the third entry 366, and the fourth entry 368 is a hyper-text transfer protocol (HTTP) header. The HTTP header should include an initial boundary. The HTTP header defines the start of x-mixed replace data. An exemplary HTTP header follows: HTTP/1.1 200 Content-Type: multipart/x-mixed-replace;boundary=123456789 Cache-Control: no-cache -123456789 A boundary, as specified in the first directive column 358 of the first entry 362, and in the second directive column 360 of the second entry 364, the third entry 366, and the fourth entry 368, is an HTTP boundary. The HTTP boundary defines the end of a given section of x-mixed replace data. An exemplary HTTP boundary follows: -123456789 A footer, as specified in the first directive column 358 of the fifth entry 370, is an HTTP footer. The HTTP footer defines the end of all x-mixed replace data. An exemplary HTTP footer follows: -123456789- The exemplary HTTP header may define the beginning of x-mixed replace data, the exemplary HTTP boundary may define the end of a portion of the x- mixed replace data, and the exemplary HTTP footer may define the end of all x-mixed replace data. The exemplary HTTP header , the exemplary HTTP boundary, and the exemplary HTTP footer are associated with each other by the number 123456789, which appears in the second line of the exemplary HTTP header, in the exemplary HTTP boundary, and in the exemplary HTTP footer. The web browser 256 renders the display 134 (shown in Fig. 1) attached to the computer 120. (shown in Fig. 1) according to the data describing the web site, which appears after the exemplary HTTP header. If the web browser 256 receives new data from the HSML processor 254, the web browser 256 renders the display 134 according to the new data. If the web browser 256 receives an HTTP boundary, the web browser 256 "wipes" the display 134 attached to the computer 120 upon receipt of new data, and repaints the display 134 according to the data which follows the HTTP boundary. The web browser may also close its socket once it receives an HTTP footer. If the web browser 256 receives an indication that new information needs to be obtained, for example, if a user clicks on a hyper-link, the web browser 256 transmits a URL to the HSML processor 254 (shown in Fig. 2B), and it closes the old socket before opening a new connection. A close socket, as specified in the second directive column 360 of the fifth entry 370, closes the socket to the web browser. The HSML processor 254 may not contact the web browser 256 once the socket is closed. The socket is closed by using a method close of the instance socket of the class Socket of the JAVA 2 Platform, Standard Edition, vl .2.2. The entries in the append/prepend column 361 can have values equal to "before" and "after". Each value stored in the append/prepend column 361 indicate whether the associated first directive should be appended or prepended to the data being sent to the downstream component specified by the temporary variable DNSTR_COMP. If the entry in the append/prepend column 361 is "after", the first directive should be appended to the data received from the web server 102 (shown in Fig. 1), if however, the entry in the append/prepend column 361 is "before", the first directive should be prepended to the data received from the web server 102. The second directive should always be appended to the data received from the web server 102 (shown in Fig. 1). The thread 300 determines whether the data received by the thread 300 during the new connection includes any HSML grammars. The thread 300 reads data from the data stream, without removing any data from the data stream, looking for an HSML grammar. After the thread 300 has reviewed the data received from the web server 102, the thread 300 appends or prepends the directives specified in the table 350 onto the data received from the web server 102 depending on whether the previous page contained an HSML grammar, the current page contained an HSML grammar, and how the current page was initiated. Once the directives are appended or prepended, the thread 300 advances to step 324. At step 324, the thread 300 determines whether the temporary variable CUR VOICE is equal to TRUE. If the temporary variable CUR_VOICE is equal to TRUE, the thread 300 advances to step 328. If the temporary variable CUR_VOICE is not equal to TRUE, the thread 300 advances to step 326. At step 326, the thread 300 sets the temporary variable PREV_VOICE equal to FALSE. Once the temporary variable PREV_VOICE is set equal to FALSE, the thread 300 advances to step 330. At step 328, the thread 300 sets the temporary variable PREN_NOICE equal to TRUE. Once the temporary variable PREV VOICE is set equal to TRUE, the thread 300 advances to step 330. At step 330, the thread 300 sets the temporary variable CURJVOICE equal to FALSE. Once the temporary variable CURJVOICE is set equal to FALSE, the thread 300 advances to step 332. At step 332, the thread 300 determines whether the data stream, received by the thread 300 during the new connection, includes any HSML grammars. The thread 300 reads data from the data stream, without removing any data from the data stream, looking for an HSML grammar. If the thread 300 finds the beginning of any HSML grammar, HSML grammars are present in the data stream, and the thread 300 advances to step 334. The step 334 is shown in more detail in FIG. 7. Once the step 334 is completed, the thread 300 advances to step 304. If the thread 300 does not find the beginning of any HSML grammar, there are no HSML grammars in the data stream, and the thread 300 advances to step 304. FIG. 4 illustrates the thread 400 which begins parallel execution with thread 300 at step 316. Thread 400 receives data from the web browser 256 (shown in Fig. 2B). The thread 400 begins at step 401 by sending a request to the server address including the URL and any parameters. Once the request is sent to the server, the thread 400 advances to step 402. At step 402, the thread 400 performs a read from the web browser 256. By reading from the web browser, the thread 400 can determine if any additional arguments are specified by the web browser 256. Once the thread 400 performs a read from the web browser 256, the thread 400 advances to step 404. At step 404, the thread 400 determines whether an interrupt has been received by the thread 400 from thread 500, which is explained in greater detail in connection with Fig. 5. If an interrupt has been received, the thread 400 advances to step 406. If an interrupt has not been received, the thread 400 advances to step 410. At step 406, the thread 400 closes its connection with the web server 102. Once the thread 400 closes its connection with the web server 102, the thread 400 advances to step 408. At step 408, the thread 400 ceases further communication with the web browser 256 (shown in Fig. 2B). The thread 400 does not close the connection with the web browser 256. The connection with the web browser 256 remains open and waits for another contact from the HSML processor 254 (shown in Fig. 2B). Once the thread 400 ceases communication with the web browser 256, the thread 400 exits. At step 410, the thread 400 determines whether additional data has been received from the web browser 256. If data has been read from the web browser 256, the thread 400 advances to step 412. If no data was received from the web browser 256, the thread 400 advances to step 402. At step 412, the thread 400 transmits the additional arguments received from the web browser 256 to the web server 102 (shown in Fig. 1). The additional arguments should be sent to the web server 102 as arguments associated with the server name that was sent to the web server by the thread 300. After the thread 400 transmits the arguments received from the web browser 256 to the web server 102, the thread 400 advances to step 402. FIG. 7 illustrates the procedure 334 for creating, storing and sending rule based grammars and TTS grammars in greater detail. The procedure 334 in conjunction with its sub-procedures parse the markup language of a web page extracting the HSML grammars which define the rule based grammars and the TTS grammars for that web page, which store the rule based grammars and TTS grammars, and which transmit the rale based grammars to the ASR engine 258. The procedure 334 itself, parses the markup language of the web page searching for an HSML blockset. The HSML blockset is the top level statement of any HSML grammar. The procedure 334 begins at step 702 by initializing a temporary variable SPEECH, a temporary variable HREF, and a temporary variable ASRCMDS to null. Once the temporary variables SPEECH, HREF, and ASRCMDS are initialized the procedure 334 advances to step 704. At step 704 the procedure 334 begins reading the markup language included in the data describing the web page. If the procedure 334 reads a string "<hsml:blockset>", the procedure 334 advances to step 706. The step 706 is shown in more detail in FIG. 8. Once the step 706 has completed, the procedure 334 advances to step 704. If the procedure 334 does not read a string "<hsml:blockset>", the procedure 334 advances to step 708. At step 708, the procedure 334 compares what the procedure 334 has read to EOF or end of file. EOF designates when a file has come to an end. If the procedure 334 has read the EOF character, the procedure 334 advances to step 710. If the procedure 334 has not read the EOF character, the procedure 334 advances to step 704. At step 710, the procedure 334 transmits the rule based grammars to the ASR engine 258 (shown in Fig. 2B). The process 700 uses a class library called International Business Machines Java Speech Library (IMBJS Library), version 1.0, to interface with the ASR engine 258. The procedure 334 then initializes a reader, which is a JANA superclass, as a stringreader. The stringreader is a JANA class and a member of the JANA superclass reader. The reader is provided with the rale based grammars that shall be supplied to the ASR engine 258. The rale based grammars are stored in the temporary variable ASRCMDS. Once the rule based grammars are stored, the procedure 334 initializes an instance rgGram of the class Rule Grammar, which is a IBMJS class. The instance rgGram is initialized as equal to the output of the method loadJSGF which is a method of the instance recognizer of a class which implements the IBMJS Library interface Recognizer. The temporary variable ASRCMDS is provided as an argument to the method loadJSGF. The method loadJSGF transmits the rale based grammars to the ASR engine 258. Once the rule based grammars are sent to the ASR engine 258, the procedure 334 advances to the step 712. At step 712, the procedure 334 specifies a result listener which receives output from the ASR engine 258. The result listener is bound by using the method addResultListener, which is a method of the instance rgGram of a class which implements the IBMJS Library interface Rule Grammar. Once the result listener is initialized, the procedure 334 utilizes the method commitChanges of the class which implements the IBMJS Library interface Recognizer to complete the changes specified to the ASR engine 258 and exits. FIG. 8 illustrates the procedure 706 for parsing block-sets of HSML grammars in greater detail. The procedure 706 begins at step 802 by reading the markup language included in the data describing the web page. If the procedure 706 reads a string "<hsml:JSML>", the procedure 706 advances to step 804. The step 804 is shown in more detail in FIG. 10. Once the step 804 has completed, the procedure 706 advances to step 802. If the procedure 706 does not read a string "<hsml:JSML>", the procedure 706 advances to step 806. At the step 806, the procedure 706 compares what the procedure 706 has read to the string "<hsml:JSGFRule>". If the procedure 706 has read the string "<hsml:JSGFRule>", the procedure 706 advances to step 808. The step 808 is shown in more detail in FIG. 11. Once the step 808 has completed, the procedure 706 advances to step 802. If the procedure 706 has not read the string "<hsml:JSGFRule>", the procedure 706 advances to step 810. At the step 810, the procedure 706 compares what the procedure 706 has read to the string "<hsml:block>". If the procedure 706 has read the string "<hsml:block>", the procedure 706 advances to step 812. The step 812 is shown in more detail in FIG. 9. Once the step 812 is completed, the procedure 706 advances to step 802. If the procedure 706 has not read the string "<hsml:block>", the procedure 706 advances to step 814. At the step 814, the procedure 706 compares what the procedure 706 has read to the string "</hsml:blockset>". If the procedure 706 has read the string "</hsml:blockset>", the procedure 706 is complete and the procedure 706 exits. If the procedure 706 has not read the string "</hsml:blockset>", the procedure 706 advances to step 816. At the step 816 the procedure 706 reports an error in the markup language of the data describing the web page. If the string "</hsml:blockset>" does not appear at this point, an error should be reported. Once the error is reported, the procedure 706 exits, and in turn the procedure 334 exits. FIG. 9 illustrates the procedure 812 for parsing blocks of HSML grammars in greater detail. The procedure 812 begins at step 901 where the procedure 812 initializes the temporary variable NOICE_GRAM to FALSE. Once the temporary variable NOICE_GRAM is initialized, the procedure 812 advances to step 902. At step 902, the procedure 812 reads the markup language included in the data describing the web page. If the procedure 812 reads a string "<hsml:JSML>", the procedure 812 advances to step 804. The step 804 is shown in more detail in FIG. 10. Once the step 804 is completed, the procedure 812 advances to step 902. If the procedure 812 does not read the string "<hsml:JSML>", the procedure 812 advances to step 904. At step 904, the procedure 812 continues to read the markup data included with the data. If the procedure 812 has read a string matching the string "<hsml:JSGFRule>", the procedure 812 advances to step 905. If the procedure 812 has not read a string matching the string "<hsml:JSGFRule>", the procedure 812 advances to step 906. At step 905, the procedure 812 sets the temporary variable NOICE_GRAM equal to TRUE to signify that a rule based grammar is present in the HSML block. Once the temporary variable NOICE_GRAM is set, the procedure 812 advances to step 808. The step 808 is shown in more detail in FIG. 10. Once the step 808 is completed, the procedure 812 advances to step 902. At step 906, the procedure 812 compares what the procedure 812 has read to the string "</hsml:block>". If the procedure 812 has read a string matching the string "</hsml:block>", the procedure 812 advances to step 910. If the procedure 812 has not read a string matching the string "</hsml:block>", the procedure 812 advances to step 908. " At the step 908 the procedure 812 reports an error in the markup language of the data describing the web page. If the string "</hsml:block>" does not appear at this point, an error in the markup language should be reported. Once the error is reported, the procedure 812 exits, and in turn the processes 334 and 706 exit. At step 910, the procedure 812 determines whether the temporary variable NOICE_GRAM is equal to TRUE. If the temporary variable NOICE_GRAM is equal to FALSE, the procedure 812 advances to step 912. If the temporary variable NOICE_GRAM is not equal to FALSE, the procedure 812 exits. At step 912, the procedure 812 transmits a Java speech grammar format rales (JSGF rales) corresponding to the string stored in the temporary variable SPEECH to the ASR engine 258. The string stored in the temporary variable SPEECH is provided to a method speak of the instance synthesizer of a class which implements the IBMJS Library interface Synthesizer. Once the JSGF rule is transmitted to the ASR engine 258 (shown in Fig. 2B), the procedure 812 exits. FIG. 10 illustrates the procedure 804 for parsing HSML TTS grammars in greater detail. The procedure 804 begins at step 1002 by reading the markup language included in the data describing the web page. If the procedure 804 reads a string "<!CDATA[", the procedure 804 advances to step 1006. If the procedure 804 does not read a string "<!CDATA[", the procedure 804 advances to step 1004. At the step 1004 the procedure 804 reports an error in the markup language of the data describing the web page. If the string "<hsml:JSML>" is not followed by the string "<!CDATA[" an error should be reported. Once the error is reported, the procedure 804 exits, and in turn the processes 334 and 706 exit, and, if running, the procedure 812 exits. At step 1006, the procedure 804 captures the text of the markup language included in the data describing the web page until the procedure 804 reads a "]". The captured markup language is stored in the temporary variable SPEECH as a string. Once captured markup language is stored in the temporary variable SPEECH, the procedure 804 advances to step 1008. At step 1008, the procedure 804 continues to read the markup language included with the data describing the web site. If the procedure 804 has read a string matching the string "]x/hsml:JSML>", the procedure 804 is complete and the procedure 804 exits. If the procedure 804 has not read a string matching the string "]x/hsml:JSML>", the procedure 804 advances to step 1010. At the step 1010 the procedure 804 reports an error in the markup language of the data describing the web page. If the string "]" is not followed by the string "]>< hsml: JSML>" an error should be reported. Once the error is reported, the procedure 804 exits, and in turn the processes 334 and 706 exit, and, if running, the procedure 812 exits. FIG. 11 illustrates the procedure 808 for parsing HSML rule based grammars in greater detail. The procedure 808 begins at step 1102 by reading the markup language included in the data describing the web page. If the procedure 808 reads a string "href =", the procedure 808 advances to step 1104. If the procedure 808 does not read a string "href =", the procedure 808 advances to step 1106. At step 1104, the procedure 808 captures the text of the markup language included in the data describing the web page until the procedure 808 reads an entire string bounded by double quotes, for example, in the first example HSML rule based grammar, "www.columbia.edu". The captured markup language included in the data describing the web page is stored in the temporary variable HREF as a string. Once the captured markup language is stored in the temporary variable HREF, the procedure 808 advances to step 1106. At step 1106, the procedure 808 continues to read the markup language included with the data describing the web site. If the procedure 808 has read a string matching the string "tag - ', the procedure 808 advances to step 1110. If the procedure 808 has not read a string matching the string "tag=", the procedure 808 advances to step 1108. At the step 1108 the procedure 808 reports an error in the markup language of the data describing the web page. If the string "tag =" is not present in the markup language at this point an error should be reported. Once the error is reported, the procedure 808 exits, and in turn the processes 334 and 706 exit, and, if running, the procedure 812 exits. At step 1110, the procedure 808 captures the text of the markup language included in the data describing the web page until the procedure 808 reads an entire string bounded by double quotes, for example, in the first example HSML rule based grammar, "reload". The captured markup language included in the data describing the web page is stored in the temporary variable TAG as a string. After the captured markup language is stored in the temporary variable TAG, the procedure 808 creates a new record in a database located on the data storage unit 126 (shown in Fig. 1). The new record includes a first field, a second field and a third field. The first field is populated with the string stored in the temporary variable TAG, the second field is populated with the string "HREF", and the third field is populated with the string stored in the temporary variable HREF. After the first database record is populated, the procedure 808 advances to step 1112. h an alternate embodiment, the string "tag=" and associated tag may be eliminated from the HSML rale, but there should be at least one srting "tag=" and associated tag per grammar. At step 1112, the procedure 808 continues to read the markup language included with the data describing the web site. If the procedure 808 has read a string matching the string "x![CDATA[", the procedure 808 advances to step 1116. If the procedure 808 has not read a string matching the string "x![CDATA[", the procedure 808 advances to step 1114. At the step 1114 the procedure 808 reports an error in the markup language of the data describing the web page. If the string "x! [CDATA[" is not present in the markup language at this point an error should be reported. Once the error is reported, the procedure 808 exits, and in turn the processes 334 and 706 exit, and, if running, the procedure 812 exits. At step 1116, the procedure 808 captures the text of the markup language included in the data describing the web page until the procedure 808 reads "]". The captured markup language included in the data describing the web page is stored in the temporary variable ASRCMDS as text, and a carriage return character is appended to the end of the captured text. Once the text is stored in the temporary variable ASRCMDS, the procedure 808 advances to step 1118. At step 1118, the procedure 808 continues to read the markup language included with the data describing the web site. If the procedure 808 has read a string matching the string "]]x/hsml: JSGFRule>", the procedure 808 advances to step 1122. If the procedure 808 has not read a string matching the string "]]></hsml:JSGFRule>", the procedure 808 advances to step 1120. At the step 1120 the procedure 808 reports an error in the markup language of the data describing the web page. If the string "]]></hsml:JSGFRule>" is not present in the markup language at this point an error should be reported. Once the error is reported, the procedure 808 exits, and in turn the processes 334 and 706 exit, and, if running, the procedure 812 exits. At step 1122, the procedure 808 compares the temporary variable SPEECH to NULL. If the temporary variable SPEECH is equal to NULL, the procedure 808 advances to step 1126. If the temporary variable SPEECH is not equal to NULL, the procedure 808 advances to the step 1124. At step 1124, the procedure 808 creates another new record in the database located on the data storage unit 126 (shown in Fig. 1). This new record includes a first field, a second field, and a third field. The first field is populated with the string stored in the temporary variable TAG, the second field is populated with the string "SPEECH", and the third field is populated with the string stored in the temporary variable SPEECH. After this new record is populated, the procedure 808 advances to step 1126. At step 1126, the procedure 808 resets some of the temporary variables. The temporary variables SPEECH, TAG and HREF are set equal to NULL. Once these temporary variables are set equal to NULL, the procedure 808 is complete and it exits. FIG. 5 illustrates the thread 500 that receives arrays of tags from the ASR engine 258 (shown in Fig. 2B). More particularly, the thread 500 receives arrays of tags from the ASR engine 258, constructs full URLs based upon the arrays of tags received from the ASR engine 258, and transmits the full URLs to the web server. Each tag of an array corresponds to a grammar rule that has been invoked within the ASR engine 258. The thread 500 begins at step 502 by determining whether any system commands exist within the array of tags received from the ASR engine 258. If any system commands have been received, the thread 500 advances to step 504. If no system commands have been received, the thread 500 advances to step 506. At step 504, the thread 500 executes any system commands received by the thread 500. System commands are system level commands that are invoked by rale based grammars stored in the ASR engine 258, for example, exit. The rule based grammars, associated with system commands are always active in the ASR engine 258 no matter which web page is currently active. In the case of the system command exit, the ASR engine 258 will attempt to match any utterance to the string "exit", regardless of which web page is currently being viewed. If the rule based grammar associated with the string "exit" is invoked, the ASR engine 258 issues an array of tags, one of which is associated with the system command exit, and the thread 500 executes the system commands. Once the system commands have been executed, the thread 500 advances to step 502. At step 506, the thread 500 searches the database located on the data storage device 126 (shown in Fig. 1) for database records with a first tag of the list of tags stored in the first field of the database records. If the database contains no records where the first field of the database record matches the first tag of the array of tags, or more than-two records where the first field of the database records matches the first tag of the array of tags, the database contains an inappropriate number of database records and the thread 500 advances to step 508. If the database contains one or two records where the first field of the database records matches the first tag of the array of tags, the database contains an appropriate number of database records and the thread 500 advances to step 510. At the step 508 the thread 500 reports an error in the markup language of the data describing the web page. If the database does not contain any records corresponding to the first tag of the array of tags or the database contains more than two records corresponding to the first tag of the array of tags, an error should be reported. Once the error is reported, the thread 500 exits, and in turn the thread 300 exits. At step 510, the thread 500 searches the database located on the data storage device 126 (shown in Fig. 1) for a database record with a string matching the first tag of the array of tags stored in the first field of the database record and the string "SPEECH" stored in the second field of the database record. If the thread 500 finds such a database record, the thread 500 advances to step 512. If the thread 500 does not find such a database record, the thread 500 advances to step 514. At step 512, the thread 500 transmits a JSGF rule corresponding to the string stored in the third field of the of the database record found during the step 510 to the ASR engine 258 (shown in Fig. 2B). The string stored in the third field of the database record found during the step 510 is provided to a method speak of the instance synthesizer of a class which implements the IBMJS Library interface Synthesizer. Once the JSGF rale is transmitted to the ASR engine 258, the thread 500 advances to step 514. At step 514, the thread 500 determines whether the temporary variable PREN_NOICE is set equal to TRUE. If the temporary variable PRENJVOICE is set equal to TRUE, the thread 500 advances to step 518. If the temporary variable PREV_VOICE is not set equal to TRUE, the thread 500 advances to step 516. At step 516, the thread 500 assigns the value of a temporary variable DNSTR_COMP_2 equal to the value of the temporary variable DNSTR_COMP. The temporary variable DNSTR_COMP_2 now represents the socket of the downstream component, which will be used by a thread 600, described in greater detail in relation to FIG. 6, to transmit data to the web browser. Once the value of the temporary variable DNSTR_COMP_2 is updated, the thread 500 advances to step 518. At step 518, the thread 500 sets the temporary variable CUR_VOICE equal to TRUE. Once the temporary variable CURJVOICE is set equal to TRUE, the thread 500 advances to step 520. At step 520, the thread 500 determines whether the thread 400 is currently running. If the thread 400 is currently running, the thread 500 advances to step 522. If the thread 400 is not currently running, the thread 500 advances to step 524. At step 522, the thread 500 transmits an interrupt to thread 400. The interrupt will cause the thread 400 to exit without closing its connection with the web browser 256. Once the interrupt is sent to the thread 400, the thread 500 advances to step 524. At step 524, the thread 500 searches the database located on the data storage device 126 (shown in Fig. 1) for a database record with the first tag of the array of tags stored in the first field of the database record and the string "HREF" stored in the second field of the database record. If the thread 500 finds such a database record, the thread 500 stores the string stored in the third field of the database record in a temporary variable and appends any tags received from the ASR engine 258 onto the string stored in the temporary variable. Once the tags are appended, the thread 500 transmits the string stored in the temporary variable to the thread 300. After the string is sent to thread 300, the thread 500 advances to step 526. At step 526, the thread 500 causes the thread 600 to begin execution. Once the thread 600 begins execution, the thread 500 exits. FIG. 6 illustrates a thread 600 that receives and transmits data sent to the web browser 256 (shown in Fig. 2B) associated with web pages which were invoked by the ASR engine 258. The thread 600 begins at step 602 by determining whether a data stream has been received by the thread 600. If a data stream has been received, the thread 600 advances to step 604. If a data stream has not been received, the thread 600 advances to step 608. At step 604, the thread 600 must transmit the data contained within the data stream received from thread 300 to the socket specified in the temporary variable DNSTR_C MP_2. Once the data received by the thread 600 is transmitted to the web browser 256, the thread 600 advances to step 606. At step 606, the thread 600 determines whether the browser socket specified by the temporary variable DNSTR_COMP_2 is closed. If the thread 600 receives an error when it attempts to transmit data to the value of the browser socket variable at step 604, the browser socket is closed and the thread 600 must exit. If the thread 600 does not receive an error, the browser socket is open and the thread 600 advances to step 602. At step 608, the thread 600 ceases further communication with the web browser 256. The thread 600 does not close the connection with the web browser 256. The connection with the web browser 256 remains open and waits for contact from another process. Once the thread 600 ceases communication with the web browser 256, the thread 600 exits. In an alternate embodiment, the HSML processor 254 (shown in Fig. 2B) may receive data describing a web page with multiple frames included within that web page. Each frame may include a different set of HSML rule based grammars and HSML TTS grammars. The HSML processor 254 can be configured to monitor multiple sets of HSML rule based grammars and HSML TTS grammars.

Claims: CLAIMS 1. A method for providing a visual web page having an audio interface, comprising: providing data specifying a web page; including in said data a first rale based grammar statement, the first rule based grammar statement having a first phrase portion, a first command portion and a first tag portion; and including in said data a second rule based grammar statement, the second rule based grammar statement having a second phrase portion, a second command portion, and a second tag portion. 2. The method of claim 1, wherein the data specifying the web page includes markup language. 3. The method of claim 1, wherein the first rale based grammar statement is specified by markup language of the data specifying the web page. 4. The method of claim 1, wherein the second rale based grammar statement is specified within the markup language of the data specifying the web page. 5. The method of claim 1, further comprising the step of including in said data a first speech grammar statement, the first speech grammar having a first speech phrase portion. 6. The method of claim 5, wherein the first speech grammar statement is associated with the first rule based grammar statement. 7. The method of claim 1 , wherein the first rale based grammar statement includes a first display priority portion. 8. The method of claim 7, wherein the second rule based grammar statement includes a second display priority portion. 9. A method for interacting with a web page having an audio interface, comprising: receiving data specifying a web page, said data including a first rale based grammar Statement, the first rale based grammar statement having a first phrase portion, a first command portion and a first tag portion, and a second rale based grammar statement, the second rale based grammar statement having a second phrase portion, a second command portion, and a second tag portion; storing at least a portion of the first rale based grammar; storing at least a portion of the second rale based grammar; providing the data specifying the web page to a web browser; providing the first phrase portion and the first tag portion as a first recognition grammar to an automated speech recognition engine; and providing the second phrase portion and the second tag portion as a second recognition grammar to the automated speech recognition engine. 10. The method of claim 9, wherein the data specifying the web page includes markup language. 11. The method of claim 9, wherein the first rale based grammar statement is specified within the markup language of the data specifying the web page. 12. The method of claim 9, wherein the second rule based grammar statement is specified within the markup language of the data specifying the web page. 13. The method of claim 9, further comprising the step of creating a first speech grammar from a first speech grammar statement contained within the data specifying the web page, the first speech grammar having a first speech phrase portion; 14. The method of claim 13, wherein the first speech grammar statement is associated with the first rale based grammar. 15. The method of claim 14, further comprising the steps of: . receiving an indication that the first recognition grammar has been invoked; and . transmitting the first speech grammar to the automated speech recognition engine to be output as speech. 16. The method of claim 13, further comprising the step of transmitting the first speech grammar to the automated speech recognition engine to be output as speech. 17. The method of claim 9, further comprising the steps of: receiving from the automated speech recognition engine an indication that the first recognition grammar has been invoked; reading the first command portion of the first rule based grammar from the first record of the database; and , transmitting the first command portion to a web server. 18. The method of claim 9, further comprising the step of displaying an output audio level. 19. The method of claim 18, further comprising the step of receiving an indication that the first recognition grammar has been invoked, and displaying the first phrase portion of the first rule based grammar. 20. The method of claim 18, further comprising the step of receiving an indication that the second recognition grammar has been invoked, and displaying the second phrase portion of the second rule based grammar. 21. The , method of claim 18, further comprising the step of displaying the first phrase portion of the first rale based grammar and the second phrase portion of the second rale based grammar. 22. The method of claim 18, wherein the first rale based grammar includes a first display priority portion. 23. The method of claim 22, wherein the second rule based grammar includes a second display priority portion. 24. The method of claim 23, further comprising the step of displaying the first phrase portion of the first rule based grammar because the first priority portion is greater than the second priority portion, and refraining from displaying the second phrase portion of the second rule based grammar. 25. A system for receiving a visual web page having an audio interface, comprising: a fιr_t input for receiving data specifying a web page, said data including a first rule based grammar statement having a first phrase portion, a first command portion, and a first tag portion, and including a second rale based grammar statement having a second phrase portion, a second command portion, and a second tag portion; a database for storing at least a portion of said first rule based grammar statement -'and for storing at least a portion of said second rule based grammar statement; a web browser for receiving said data specifying the web page; and an automated speech recognition engine for receiving the first phrase portion and the first tag portion as a first recognition grammar, and for receiving the second phrase portion and the second tag portion as a second recognition grammar. 26. The system of claim 25, wherein the data specifying the web page includes markup language. 27. The system of claim 25, wherein the first rule based grammar statement is specified within the markup language of the data specifying the web page. 28. The system of claim 25, wherein the second rale based grammar statement is specified within the markup language of the data specifying the web page. 29. The 1 system of claim 25, wherein said data specifying the web page includes a first speech grammar statement, the first speech grammar statement having a first speech phrase portion. 30. The system of claim 29, wherein the first speech grammar statement is associated with the first rule based grammar. 31. The system of claim 30, further comprising an hyper-speech markup language processor responsive to the automated speech recognition engine invoking the first recognition grammar, the hyper-speech markup language processor providing the first speech phrase portion to the automated speech recognition engine to be output as speech. . 32. The " system of claim 29, wherein a hyper-speech markup language processing unit transmitting the first speech phrase portion to the automated speech recognition engine to be output as speech. 33. The, system of claim 25, further comprising an hyper-speech markup language processor. responsive to the automated speech recognition engine invoking the first recognition grammar, the hyper-speech markup language processor transmitting the first command portion to a web server.

Inventors: CHARNEY MICHAEL L, STARREN JUSTIN, CHARNEY, MICHAEL, L., STARREN, JUSTIN
Applicants: CHARNEY MICHAEL L, STARREN JUSTIN, UNIV COLUMBIA, CHARNEY, MICHAEL, L., STARREN, JUSTIN, THE TRUSTEES OF COLUMBIA UNIVERSITY IN THE CITY OF NEW YORK
Application year: 2001
Main classification: G06F3
IPC codes: G06F3, G10L15, H04M3