We have looked at this again and believe you need to make an improvement here. Your implementation puts the hotlinks into the root document which is fine, no problem however this goes against the VoiceXML 2.0 standard.
Why?
Because the VoiceXML 2.0 standard states the hotlinks can also be included on a per page/dialogue basis. Your model does not address this and thus needs to be implemented.
All Audium does is put a hotlink handler in the root document!
In a situation where "hotlink behaviour" can change within certain pages (and believe me clients expect these things) we need something more here.
Therefore we would strongly urge you to create a "Local hotlinks hander" that when included on the page is implemented on selected per page basis. A Global handler clearly does what it does on a global scale but has uses and short comings and again causes us headaches which is why the W3C decided on local and global hot link handler options.
Thoughts!
Subject: RE: Local Hotlinks Handler Replied by: null on 13-02-2007 10:46:06 PM Hello Karl,
Note that Call Services currently allows the functionality of a grammar with a local scope only.
A Form element with the modal setting set to true, and including any desired keywords in one of the Formâ¿¿s grammars will simulate a document scope link. An X_Option_Menu element with one of the option DTMF and/or option Voice set to the desired keypress sequence/ keywords will also achieve the same functionality of a local hotlink. Per the VoiceXML 2.0 specification , local grammars take precedence over global grammars.
To accomplish true document scope links, you can create a custom voice element or use a VoiceXML Insert element.
Regards, Tam
Subject: RE: Local Hotlinks Handler Replied by: null on 14-02-2007 04:57:29 PM My question now is since the other components Currency, Date, Time, Digits, Yes/No are all derived from form why is modal not in these options? This might have actually solved our problem.
As you know modal type is an attribute of field so why the missing parameter.
I still say there is a need for local and global handlers, doing it through the form is a cludge, treating it like a form grammar result is not a true local hotlink.
And yes writing a component is fine, but this is a little bit basic and we should not have to workaround the issue.
Subject: RE: Local Hotlinks Handler Replied by: null on 14-02-2007 09:00:56 PM Hello Karl,
Regarding your query about the modal setting for other elements such as Currency, Date, Time, and Digits please see our reply to your feature request. So that we can consolidate all discussion on this issue into one thread for easy tracking, please continue discussion regarding the modal setting in that other thread.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
