Re: Setting grammars programmatically

I agree with Titus von der Malsburg comments on 8/10/06.
With the addition of the <data> tag in v2.1 there seems to be some
acknowlegement that VXML needed more client processing ablility (this
reduces the number of complete VXML page transitions in an application).
This is somewhat like the AJAX paradigm.

As an alternative, maybe using a <value> tag within <grammar> tags to
dynamically specify the grammar content would be a bit less ambiguous?
For example:

	<value expr="GenerateSomeGrammar()"/>

On 8/10/06, Titus von der Malsburg wrote <>

From: Titus von der Malsburg <
&References=%253C20061008132740.GC6013%40mother%253E> > 
Date: Sun, 8 Oct 2006 15:27:41 +0200
Message-ID: <20061008132740.GC6013@mother> 

Hi list,

maybe I'm doing something wrong but my VoiceXML code tends to get a hell
of a lot redundant.  I use subdialogs, event-handling and XML macros
(courtesy of a nice XSLT hack) to factor out common code as much as
possible.  Unfortunately there are many cases where I could use
subdialogs when it was possible to parameterize them with grammars.
Whereas it's possible to pass a grammar to a subdialog, the grammar
element doesn't provide means for defining grammars programmatically.
(Srcexpr is applicable in some situations but in others the grammar
cannot be determined until runtime, so that srcexpr isn't very helpful.)
What's missing here is an expr attribute as provided by other elements.

I can think of many situations beyond subdialogs where expr could be
beneficially used.  Since VoiceXML 2.1 already introduced the srcexpr
attribute for the grammar element, I suspect that there are no technical
reasons that rule out a expr attribute.  Therefore I humbly propose to
add it in some future version of VoiceXML.


    Titus v.d. Malsburg


Greg Inglis

Software Engineer


Telephonetics - Making Sound Business Sense

Hamilton House, 111 Marlowes, Hemel Hempstead, Herts. HP1 1BB



(T): +44 (0) 1442 242 242

(F): +44 (0) 1442 242 123


The disclaimer available at
<blocked::BLOCKED::>  or by
sending email to
<>  applies
to this email.

Received on Thursday, 12 October 2006 21:56:42 UTC