W3C home > Mailing lists > Public > www-voice@w3.org > April to June 2004

Re: Proposal to W3C Voice Browser Working Group for VXML

From: James A. Larson <jim@larson-tech.com>
Date: Thu, 17 Jun 2004 12:12:59 -0700
Message-ID: <40D1ED3B.9000903@larson-tech.com>
To: Alex Robin M <arobin5@hotmail.com>
Cc: www-voice@w3.org
Robin,

Thanks for your suggestions for a PromptConfig.XML document.  I will bring this suggestion to the Voice Browser 
Working Group as they define the requirements and architecture for the the the follow on to VoiceXML 2.0.  
If we need any clarification about your proposal, I'll contact you.

Regards,

Jim Larson
Co-chair, Voice Browser Workin Group



Alex Robin M wrote:

> I have worked on 2 VXML projects as a software Engineer, and having 
> experienced the nightmarish issues with maintaining the Speech prompts 
> and wav files matched and in good directory structure for use in the 
> voice portals, it had me thinking if there could be a easier way.
>  
>
> The number of prompts (and wav files) is directly proportional to the 
> size of the voice portal being developed, and it's on the development 
> team to maintain a code base with properly devised directory structure 
> to store these wav files. It is also burdened on them to maintain 
> separate pieces of config/properties file for the in-numerable text 
> dialogs to be used.
>
>  
>
> Good development practice rules against hardcoded values and also 
> about maintaining a single properties file, but that in turn does 
> increase the complexity of maintaining all the prompt details/links in 
> one file. With the innumerable prompts in a Custom voice application, 
> if a single prompt has to be changed, it would required the developer 
> to go thru the whole application, trying to decipher the call flow and 
> the associated prompts for it. Even after accomplishing the task, a 
> doubt still lingers in the mind.
>
>  
>
> Well, this did make me think about what would make it easier to 
> maintain it. Thus I came up with this solution that could decrease the 
> complexity of understanding the code and retrieving the prompts (and 
> wav files) by mapping the prompts in a specific XML file, we will call 
> this PromptConfig.XML Document.
>
>  
> Please find my proposal attached.
>  
> Regards,
> Alex Robin Marian
>  
Received on Thursday, 17 June 2004 15:12:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 30 October 2006 12:48:59 GMT