Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

Method and Procedure for Maintaining VoiceXML documents in a small and optimized object model

IP.com Disclosure Number: IPCOM000020219D
Original Publication Date: 2003-Nov-03
Included in the Prior Art Database: 2003-Nov-03
Document File: 2 page(s) / 14K

Publishing Venue



A method and procedure of maintaining VoiceXML documents in a very small object model (25 to 50% of the size of currently available solutions) that is optimized for use in a reusable VoiceXML Browser that can either run embedded in a small device or in a high-available server environment.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

  Method and Procedure for Maintaining VoiceXML documents in a small and optimized object model

    VoiceXML (Voice Extensible Markup Language) is an XML-based designed for creating audio dialogs that feature synthesized speech, digitized audio, recognition of spoken and DTMF key input, recording of spoken input, telephony and mixed initiative conversations. Application developers create speech-based applications using this XML-based markup language and VoiceXML browsers are responsible for interpreting VoiceXML documents to allow users interact with applications. At a high-level, VoiceXML Browsers retrieve VoiceXML documents in its original format and through a process of parsing (compilation), transform the markup source into data structures and/or objects in order to use them (possibly using an object model).

The market currently provides several solutions for compiling XML documents into models (eg. W3C's DOM), but they are too generic (have properties and features not used by VoiceXML documents) and heavyweight (require additional memory and processing on creation and access to information).

Handling VoiceXML only (not any other type of XML documents), creates an opportunity for improvement and optimization. There isn't a need for a generic and character based structure. These are the aspects to be focused:

1) Lightweight Object Model - improving on footprint.

XML documents are basically formed of elements, their attributes and character data. When defined as strings, elements and attributes can reach a considerable size. VoiceXML is an XML document that has a definite number of elements and attributes. Instead of storing these as strings, we chose to enumerate them and store a number representation (eg. <vxml>==1, <form>==2, <field==3> and so on).

Figure 1 - example of numeric representation

XML documents by nature can be composed and contain several characters (blank spaces). These are necessary to turn them a little more human-readable for programmers. Generic object models may maintain these characters in the model since they...