When you are looking to take your application to the proverbial Next Level, and modify it to run on the Prophecy VoiceXML platform, then this appendix will be your best friend, drinking partner, and Bible all rolled into one. There will be significant changes that you will need to make when making your existing code ready for a certified-compliant platform, and this guide will ease the pain for you considerably. Every issue, element change, and modification that you will need to perform on your code is covered in full, eye-popping detail in the below sub categories.
Overview
DTD and Version Changes : Covering the initial changes that will need to be performed when you bring your existing VoiceXML code up to Prophecy standards, this section is a must-read.
Fetchhint Modifications: Most people are satisfied using the default fetchhint parameters of the VoiceXML browser, but if you like to specify this attribute in your code, then you will want to take a look at how fetchhint values are implemented in newer, compliant platforms.
Universal Grammar Modifications : The W3C makes another big change in the 2.0 platform and this section will make you ready for the tweaks that they have made to the universal grammars. If your code uses the universal grammars, or you just use the 'help' error-catching shorthand, then we advise you to take a looksee!
Subdialog Modifications: As this change could cause major problems when porting, an entire subsection has been dedicated to describing how you can get your subdialog constructs ready for deployment on the Prophecy platform.
1.3 to 2.0 Element Porting Table : Covering the small tweaks made to the VoiceXML elements that we know and love, this guide details the minor changes made to the existing elements on a case-by-case basis, and shows you the best methods for porting your application to be ready for the exciting 2.1 standard.
ANNOTATIONS: EXISTING POSTS
0 posts - click the button below to add a note to this page
