Appeal 2007-0338
Application 09/870,223
claimed. Rather, Osder is said to generate prompts as needed at runtime by
(1) expanding dynamic elements <DYN3> and <DYN5>, and (2)
concatenating the computed dynamic elements with static elements. Simply
put, Appellant contends that Osder’s prompts do not exist until runtime (i.e.,
when the actual values for the dynamic elements are computed). Therefore,
Osder’s prompts do not exist in a database as claimed (Br. 7; Reply Br. 4-6,
8-10). The Examiner responds that Osder’s static and dynamic elements are
pre-recorded prompt elements in tables stored in the SPIN1 database
(Answer 5-6).
Appellant also argues that Osder does not teach an assignment table
that assigns a value to the variable to provide an entry point to the database
as claimed (Br. 7). The Examiner argues that Osder’s SPIN Application
Table assigns the values of the identifiers (e.g., UV10AE, etc.) that point to
prompt element sets shown in Tables 2-5 that contain the pre-recorded
prompts (Answer 6). Appellant responds that even if the SPIN Application
Table corresponds to the claimed assignment table as the Examiner
contends, Osder does not disclose a “variable” to which the values UV10AE,
etc. are assigned and which can be read from outside the compiled code of
the application program as claimed (Reply Br. 11).
We will sustain the Examiner’s rejection of independent claim 1. In
our view, Osder’s stored static elements alone fully meet a “voice prompt”
giving the term its broadest reasonable interpretation. It is undisputed that
the static and dynamic elements in Osder are pre-recorded and stored in a
database. See Reply Br. 5, ll. 17-19 (noting that the static and dynamic
1 SPIN is an acronym for “Speech Interface to Network Application Platform.” See Osder, abstract.
4
Page: Previous 1 2 3 4 5 6 7 8 9 Next
Last modified: September 9, 2013