DOCSLIB.ORG

Voice Extensible Markup Language (Voicexml) Version 2.0

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Voice Extensible Markup Language (Voicexml) Version 2.0 Voice Extensible Markup Language (VoiceXML) Version 2.0 Voice Extensible Markup Language (VoiceXML) Version 2.0 W3C Working Draft 24 April 2002 This Version: http://www.w3.org/TR/2002/WD-voicexml20-20020424/ Latest Version: http://www.w3.org/TR/voicexml20 Previous Version: http://www.w3.org/TR/2001/WD-voicexml20-20011023/ Editors: Scott McGlashan, PipeBeach <[email protected]> (Editor-in-Chief) Dan Burnett, Nuance Communications, <[email protected]> Peter Danielsen, Lucent <[email protected]> Jim Ferrans, Motorola <[email protected]> Andrew Hunt, SpeechWorks International <[email protected]> Gerald Karam, AT&T <[email protected]> Dave Ladd, Dynamicsoft <[email protected]> Bruce Lucas, IBM <[email protected]> Brad Porter, Tellme Networks <[email protected]> Ken Rehor, Nuance Communications <[email protected]> Steph Tryphonas, Tellme Networks <[email protected]> Copyright ©2002 W3C® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Abstract This document specifies VoiceXML, the Voice Extensible Markup Language. VoiceXML is 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. Its major goal is to bring the advantages of web-based development and content delivery to interactive voice response applications. Status of this Document This is a W3C Last Call Working Draft for review by W3C Members and other interested parties. Last call means that the working group believes that this specification is ready and therefore wishes this to be the last call for comments. If the feedback is positive, the working group plans to submit it for consideration as a W3C Candidate Recommendation. Comments can be sent until the 24th of May, 2002. To find the latest version of this working draft, please follow the "Latest version" link above, or visit the list of W3C Technical http://www.w3.org/TR/voicexml20/ (1 of 171) [03/12/2002 9:13:12] Voice Extensible Markup Language (VoiceXML) Version 2.0 Reports. It is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress". This specification describes markup for representing audio dialogs, and forms part of the proposals for the W3C Speech Interface Framework. This document has been produced as part of the W3C Voice Browser Activity, following the procedures set out for the W3C Process. The authors of this document are members of the Voice Browser Working Group (W3C Members only). This document is for public review, and comments and discussion are welcomed on the public mailing list <[email protected]>. To subscribe, send an email to <www-voice-request@w3. org> with the word subscribe in the subject line (include the word unsubscribe if you want to unsubscribe). The archive for the list is accessible online. The proposed XML-based media types used in this specification have been submitted to the IETF for registration. Please note that during the registration process, the proposed media types may be modified or removed. The Memorandum of Understanding between the W3C and the Voice XML Forum has paved the way for the publication of this working draft, with the VoiceXML Forum committing to abandoning trademark applications involving the name "VoiceXML". This document seeks Member and public comment on both the technical design and the patent licensing issues arising out of the disclosure and licensing statements that have been made. Our decision to publish this working draft does not imply that all questions of patent licensing have been resolved or clarified. They must be resolved or work on this document in W3C will stop. As things stand at the time of publication of this specification, implementations conforming to this specification may require royalty bearing licenses for essential IPR. Further information can be found in the patent disclosures page. The patent policy for W3C as a whole is under wide discussion. A set of commitments by all participants in the Voice Browser Activity to royalty free is a possibility for the future but has NOT been made at time of publication. Conventions of this Document In this document, the key words "must", "must not", "required", "shall", "shall not", "should", "should not", "recommended", "may", and "optional" are to be interpreted as described in [RFC2119] and indicate requirement levels for compliant VoiceXML implementations. Table of Contents Abbreviated Contents ● 1. Overview ● 2. Dialog Constructs ● 3. User Input ● 4. System Output ● 5. Control flow and scripting ● 6. Environment and Resources ● 7. Appendices Full Contents ● 1. Overview ❍ 1.1 Introduction ❍ 1.2 Background ■ 1.2.1 Architectural Model ■ 1.2.2 Goals of VoiceXML ■ 1.2.3 Scope of VoiceXML http://www.w3.org/TR/voicexml20/ (2 of 171) [03/12/2002 9:13:12] Voice Extensible Markup Language (VoiceXML) Version 2.0 ■ 1.2.4 Principles of Design ■ 1.2.5 Implementation Platform Requirements ❍ 1.3 Concepts ■ 1.3.1 Dialogs and Subdialogs ■ 1.3.2 Sessions ■ 1.3.3 Applications ■ 1.3.4 Grammars ■ 1.3.5 Events ■ 1.3.6 Links ❍ 1.4 VoiceXML Elements ❍ 1.5 Document Structure and Execution ■ 1.5.1 Execution within one Document ■ 1.5.2 Executing a Multi-Document Application ■ 1.5.3 Subdialogs ■ 1.5.4 Final Processing ● 2. Dialog Constructs ❍ 2.1 Forms ■ 2.1.1 Form Interpretation ■ 2.1.2 Form Items ■ 2.1.3 Form Item Variables and Conditions ■ 2.1.4 Directed Forms ■ 2.1.5 Mixed Initiative Forms ■ 2.1.6 Form Interpretation Algorithm ❍ 2.2 Menus ❍ 2.3 Form Items ■ 2.3.1 FIELD ■ 2.3.2 BLOCK ■ 2.3.3 INITIAL ■ 2.3.4 SUBDIALOG ■ 2.3.5 OBJECT ■ 2.3.6 RECORD ■ 2.3.7 TRANSFER ❍ 2.4 Filled ❍ 2.5 Links ● 3. User Input ❍ 3.1 Grammars ■ 3.1.1 Speech Grammars ■ 3.1.2 DTMF Grammars ■ 3.1.3 Scope of Grammars ■ 3.1.4 Activation of Grammars http://www.w3.org/TR/voicexml20/ (3 of 171) [03/12/2002 9:13:12] Voice Extensible Markup Language (VoiceXML) Version 2.0 ■ 3.1.5 Semantic Interpretation of Input ■ 3.1.6 Mapping Semantic Interpretation Results to VoiceXML forms ● 4. System Output ❍ 4.1 Prompt ■ 4.1.1 Speech Markup ■ 4.1.2 Basic Prompts ■ 4.1.3 Audio Prompting ■ 4.1.4 <value> Element ■ 4.1.5 Barge-in ■ 4.1.6 Prompt Selection ■ 4.1.7 Timeout ■ 4.1.8 Prompt Queueing and Input Collection ● 5. Control flow and scripting ❍ 5.1 Variables and Expressions ■ 5.1.1 Declaring Variables ■ 5.1.2 Variable Scopes ■ 5.1.3 Referencing Variables ■ 5.1.4 Standard Session Variables ■ 5.1.5 Standard Application Variables ❍ 5.2 Event Handling ■ 5.2.1 Throw ■ 5.2.2 Catch ■ 5.2.3 Shorthand Notation ■ 5.2.4 Catch Element Selection ■ 5.2.5 Default Catch Elements ■ 5.2.6 Event Types ❍ 5.3 Executable Content ■ 5.3.1 VAR ■ 5.3.2 ASSIGN ■ 5.3.3 CLEAR ■ 5.3.4 IF, ELSEIF, ELSE ■ 5.3.5 PROMPT ■ 5.3.6 REPROMPT ■ 5.3.7 GOTO ■ 5.3.8 SUBMIT ■ 5.3.9 EXIT ■ 5.3.10 RETURN ■ 5.3.11 DISCONNECT ■ 5.3.12 SCRIPT ■ 5.3.13 LOG http://www.w3.org/TR/voicexml20/ (4 of 171) [03/12/2002 9:13:12] Voice Extensible Markup Language (VoiceXML) Version 2.0 ● 6. Environment and Resources ❍ 6.1 Resource Fetching ■ 6.1.1 Fetching ■ 6.1.2 Caching ■ 6.1.3 Prefetching ■ 6.1.4 Protocols ❍ 6.2 Metadata Information ■ 6.2.1 META ■ 6.2.2 METADATA ❍ 6.3 Property ■ 6.3.1 Platform-Specific Properties ■ 6.3.2 Generic Speech Recognizer Properties ■ 6.3.3 Generic DTMF Recognizer Properties ■ 6.3.4 Prompt and Collect Properties ■ 6.3.5 Fetching Properties ■ 6.3.6 Miscellaneous Properties ❍ 6.4 Param ❍ 6.5 Time Designations ● 7. Appendices ❍ Appendix A. Glossary of Terms ❍ Appendix B. VoiceXML Document Type Definition ❍ Appendix C. Form interpretation Algorithm ❍ Appendix D. Timing Properties ❍ Appendix E. Audio File Formats ❍ Appendix F. Conformance ❍ Appendix G. Internationalization ❍ Appendix H. Accessibility ❍ Appendix I. Privacy ❍ Appendix J. Changes from VoiceXML 1.0 ❍ Appendix K. Reusability ❍ Appendix L. Acknowledgements ❍ Appendix M. References ❍ Appendix N. Media Type and File Suffix ❍ Appendix 0. Schema ❍ Appendix P. Builtin Grammar Types http://www.w3.org/TR/voicexml20/ (5 of 171) [03/12/2002 9:13:12] Voice Extensible Markup Language (VoiceXML) Version 2.0 1. Overview This document defines VoiceXML, the Voice Extensible Markup Language. Its background, basic concepts and use are presented in Section 1. The dialog constructs of form, menu and link, and the mechanism (Form Interpretation Algorithm) by which they are interpreted are then introduced in Section 2. User input using DTMF and speech grammars is covered in Section 3, while Section 4 covers system output using speech synthesis and recorded audio. Mechanisms for manipulating dialog control flow, including variables, events, and executable elements, are explained in Section 5. Environment features such as parameters and properties as well as resource handling are specified in Section 6. The appendices provide additional information including the VoiceXML Schema, a detailed specification of the Form Interpretation Algorithm and timing, audio file formats, and statements relating to conformance, internationalization, accessibility and privacy. Developers familar with VoiceXML 1.0 are particularly directed to Changes from Previous Public Version which summarizes how VoiceXML 2.0 differs from VoiceXML 1.0. 1.1 Introduction VoiceXML is 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. Its major goal is to bring the advantages of web-based development and content delivery to interactive voice response applications.
Load more

Recommended publications
  • Genesys Voice Platform 7.6 Voicexml 2.1 Reference Manual
    Genesys Voice Platform 7.6 VoiceXML 2.1 Reference Manual The information contained herein is proprietary and confidential and cannot be disclosed or duplicated without the prior written consent of Genesys Telecommunications Laboratories, Inc. Copyright © 2006–2010 Genesys Telecommunications Laboratories, Inc. All rights reserved. About Genesys Alcatel-Lucent's Genesys solutions feature leading software that manages customer interactions over phone, Web, and mobile devices. The Genesys software suite handles customer conversations across multiple channels and resources—self-service, assisted-service, and proactive outreach—fulfilling customer requests and optimizing customer care goals while efficiently using resources. Genesys software directs more than 100 million customer interactions every day for 4000 companies and government agencies in 80 countries. These companies and agencies leverage their entire organization, from the contact center to the back office, while dynamically engaging their customers. Go to www.genesyslab.com for more information. Each product has its own documentation for online viewing at the Genesys Technical Support website or on the Documentation Library DVD, which is available from Genesys upon request. For more information, contact your sales representative. Notice Although reasonable effort is made to ensure that the information in this document is complete and accurate at the time of release, Genesys Telecommunications Laboratories, Inc., cannot assume responsibility for any existing errors. Changes and/or corrections to the information contained in this document may be incorporated in future versions. Your Responsibility for Your System’s Security You are responsible for the security of your system. Product administration to prevent unauthorized use is your responsibility. Your system administrator should read all documents provided with this product to fully understand the features available that reduce your risk of incurring charges for unlicensed use of Genesys products.
    [Show full text]
  • Bibliography of Erik Wilde
    dretbiblio dretbiblio Erik Wilde's Bibliography References [1] AFIPS Fall Joint Computer Conference, San Francisco, California, December 1968. [2] Seventeenth IEEE Conference on Computer Communication Networks, Washington, D.C., 1978. [3] ACM SIGACT-SIGMOD Symposium on Principles of Database Systems, Los Angeles, Cal- ifornia, March 1982. ACM Press. [4] First Conference on Computer-Supported Cooperative Work, 1986. [5] 1987 ACM Conference on Hypertext, Chapel Hill, North Carolina, November 1987. ACM Press. [6] 18th IEEE International Symposium on Fault-Tolerant Computing, Tokyo, Japan, 1988. IEEE Computer Society Press. [7] Conference on Computer-Supported Cooperative Work, Portland, Oregon, 1988. ACM Press. [8] Conference on Office Information Systems, Palo Alto, California, March 1988. [9] 1989 ACM Conference on Hypertext, Pittsburgh, Pennsylvania, November 1989. ACM Press. [10] UNIX | The Legend Evolves. Summer 1990 UKUUG Conference, Buntingford, UK, 1990. UKUUG. [11] Fourth ACM Symposium on User Interface Software and Technology, Hilton Head, South Carolina, November 1991. [12] GLOBECOM'91 Conference, Phoenix, Arizona, 1991. IEEE Computer Society Press. [13] IEEE INFOCOM '91 Conference on Computer Communications, Bal Harbour, Florida, 1991. IEEE Computer Society Press. [14] IEEE International Conference on Communications, Denver, Colorado, June 1991. [15] International Workshop on CSCW, Berlin, Germany, April 1991. [16] Third ACM Conference on Hypertext, San Antonio, Texas, December 1991. ACM Press. [17] 11th Symposium on Reliable Distributed Systems, Houston, Texas, 1992. IEEE Computer Society Press. [18] 3rd Joint European Networking Conference, Innsbruck, Austria, May 1992. [19] Fourth ACM Conference on Hypertext, Milano, Italy, November 1992. ACM Press. [20] GLOBECOM'92 Conference, Orlando, Florida, December 1992. IEEE Computer Society Press. http://github.com/dret/biblio (August 29, 2018) 1 dretbiblio [21] IEEE INFOCOM '92 Conference on Computer Communications, Florence, Italy, 1992.
    [Show full text]
  • Voice and Multimodal Technology for the Mobile Worker Kondratova, Irina
    NRC Publications Archive Archives des publications du CNRC Voice and Multimodal Technology for the Mobile Worker Kondratova, Irina This publication could be one of several versions: author’s original, accepted manuscript or the publisher’s version. / La version de cette publication peut être l’une des suivantes : la version prépublication de l’auteur, la version acceptée du manuscrit ou la version de l’éditeur. Publisher’s version / Version de l'éditeur: Itcon, Special Issue Mobile Computing in Construction, 9, 2004 NRC Publications Record / Notice d'Archives des publications de CNRC: https://nrc-publications.canada.ca/eng/view/object/?id=b869a897-8fb9-4e04-b50b-6e652aee9661 https://publications-cnrc.canada.ca/fra/voir/objet/?id=b869a897-8fb9-4e04-b50b-6e652aee9661 Access and use of this website and the material on it are subject to the Terms and Conditions set forth at https://nrc-publications.canada.ca/eng/copyright READ THESE TERMS AND CONDITIONS CAREFULLY BEFORE USING THIS WEBSITE. L’accès à ce site Web et l’utilisation de son contenu sont assujettis aux conditions présentées dans le site https://publications-cnrc.canada.ca/fra/droits LISEZ CES CONDITIONS ATTENTIVEMENT AVANT D’UTILISER CE SITE WEB. Questions? Contact the NRC Publications Archive team at [email protected]. If you wish to email the authors directly, please see the first page of the publication for their contact information. Vous avez des questions? Nous pouvons vous aider. Pour communiquer directement avec un auteur, consultez la première page de la revue dans laquelle son article a été publié afin de trouver ses coordonnées.
    [Show full text]
  • An Architecture of Mobile Web 2.0 Context-Aware Applications in Ubiquitous Web
    JOURNAL OF SOFTWARE, VOL. 6, NO. 4, APRIL 2011 705 An Architecture of Mobile Web 2.0 Context-aware Applications in Ubiquitous Web I-Ching Hsu Department of Computer Science and Information Engineering National Formosa University 64, Wenhua Rd., Huwei Township, Yunlin County 632, Taiwan [email protected] Abstract—The rapid development of the wireless an uniformly access to cope with the heterogeneous communication technologies, including wireless sensors, effects, including various context presentation, context intelligent mobile devices, and communication protocols, information, mobile device constraints, and context has led to diverse mobile devices of accessing various middleware [4]. To allow interoperability among the context-aware systems. Existing context-aware systems only various context-aware systems and mobile devices, a focus on characterize the situation of an entity to exhibit the advantage of contextual information association. The common standard is needed to uniformly access context contextual information can represent semantic implications information provided via a fundamental infrastructure. to provide decidable reasoning services, but it has no The Web 2.0 technologies provide a catalytic solution to mechanism to facilitating the interoperability and this problem. reusability among heterogeneous context-aware systems and Within the last two to three years, the Internet has various mobile devices. This study addresses these issues greatly changed our way of sharing resources and developing a Multi-layer Context Framework (MCF) that information. As well known, Web 2.0 is recognized as integrates Web 2.0 technologies into context-aware system the next generation of web applications proposed by T. for supporting ubiquitous mobile environment. The O’Reilly [5].
    [Show full text]
  • Dialogic Powermedia XMS Voicexml Reference Guide
    Dialogic® PowerMedia™ XMS VoiceXML Reference Guide October 2014 05-2710-005 www.dialogic.com Copyright and Legal Notice Copyright © 2012-2014 Dialogic Inc. All Rights Reserved. You may not reproduce this document in whole or in part without permission in writing from Dialogic Inc. at the address provided below. All contents of this document are furnished for informational use only and are subject to change without notice and do not represent a commitment on the part of Dialogic Inc. and its affiliates or subsidiaries ("Dialogic"). Reasonable effort is made to ensure the accuracy of the information contained in the document. However, Dialogic does not warrant the accuracy of this information and cannot accept responsibility for errors, inaccuracies or omissions that may be contained in this document. INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH DIALOGIC® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN A SIGNED AGREEMENT BETWEEN YOU AND DIALOGIC, DIALOGIC ASSUMES NO LIABILITY WHATSOEVER, AND DIALOGIC DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF DIALOGIC PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY INTELLECTUAL PROPERTY RIGHT OF A THIRD PARTY. Dialogic products are not intended for use in certain safety-affecting situations. Please see http://www.dialogic.com/company/terms-of-use.aspx for more details. Due to differing national regulations and approval requirements, certain Dialogic products may be suitable for use only in specific countries, and thus may not function properly in other countries.
    [Show full text]
  • Interactive Topographic Web Mapping Using Scalable Vector Graphics
    University of Nebraska at Omaha DigitalCommons@UNO Student Work 12-1-2003 Interactive topographic web mapping using scalable vector graphics Peter Pavlicko University of Nebraska at Omaha Follow this and additional works at: https://digitalcommons.unomaha.edu/studentwork Recommended Citation Pavlicko, Peter, "Interactive topographic web mapping using scalable vector graphics" (2003). Student Work. 589. https://digitalcommons.unomaha.edu/studentwork/589 This Thesis is brought to you for free and open access by DigitalCommons@UNO. It has been accepted for inclusion in Student Work by an authorized administrator of DigitalCommons@UNO. For more information, please contact [email protected]. INTERACTIVE TOPOGRAPHIC WEB MAPPING USING SCALABLE VECTOR GRAPHICS A Thesis Presented to the Department of Geography-Geology and the Faculty of the Graduate College University of Nebraska in Partial Fulfillment of the Requirements for the Degree Master of Arts University of Nebraska at Omaha by Peter Pavlicko December, 2003 UMI Number: EP73227 All rights reserved INFORMATION TO ALL USERS The quality of this reproduction is dependent upon the quality of the copy submitted. In the unlikely event that the author did not send a complete manuscript and there are missing pages, these will be noted. Also, if material had to be removed, a note will indicate the deletion. Dissertation WWisMng UMI EP73227 Published by ProQuest LLC (2015). Copyright in the Dissertation held by the Author. Microform Edition © ProQuest LLC. All rights reserved. This work is protected against unauthorized copying under Title 17, United States Code ProQuest LLC. 789 East Eisenhower Parkway P.O. Box 1346 Ann Arbor, Ml 48106-1346 THESIS ACCEPTANCE Acceptance for the faculty of the Graduate College, University of Nebraska, in Partial fulfillment of the requirements for the degree Master of Arts University of Nebraska Omaha Committee ----------- Uf.A [JL___ Chairperson.
    [Show full text]
  • Data Submission
    Data Submission A component of the rich web application backplane What is submission? • First, serialise some data to send… • …then send it to some end-point… • …and get various events to track progress… • …before receiving some data back. Typical uses • Send data using HTML and VoiceXML forms: – Usually replaces the ‘current form’. • Send and receive data in Ajax: – Try not to replace current page. Current use: HTML and VoiceXML <submit next="log_request" method="post" namelist="name rank serial_number" fetchtimeout="100s" fetchaudio="audio/brahms2.wav" /> Current use: Ajax (1) • var req; • • function loadXMLDoc(url) { • // native XMLHttpRequest object • if (window.XMLHttpRequest) •{ • req = new XMLHttpRequest(); • req.onreadystatechange = readyStateChange; • // IE/Windows ActiveX version • } else if (window.ActiveXObject) • req = new ActiveXObject("Microsoft.XMLHTTP"); • • if (req) •{ • req.onreadystatechange = readyStateChange; • req.open("GET", url, true); • req.send(); •} •} …Ajax (2) • function readyStateChange() { • // '4' means document "loaded" • if (req.readyState == 4) •{ • // 200 means "OK" • if (req.status == 200) •{ • // do something here •} else •{ • // error processing here •} •} •} XForms Submission • Abstract layer with one element. • Data and submission separate: – serialisation…validation…relevance. • Events for start, done, and error: – one submission triggered by the success of another. Submission element <xf:submission id="sub" method="get" action= "http://example.com/customers" /> Submission element <xf:submission
    [Show full text]
  • Session 2: Markup Language Technologies
    XML for Java Developers G22.3033-002 Session 2 - Main Theme Markup Language Technologies (Part II) Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Agenda Summary of Previous Session / Review New Syllabus XML Applications vs. Applications of XML!? History and Current State of XML Standards Advanced Applications of XML XML’s eXtensible Style Language (XSL) Character Encodings and Text Processing XML and DBMSs Course Approach ... XML Application Development XML References and Class Project Readings Assignment #1a (due today - reminder?) 2 Assignment #1b (due next week) 1 Summary of Previous Session XML Generics Course Logistics, Structure and Objectives History of Meta-Markup Languages XML Applications: Markup Languages XML Information Modeling Applications XML-Based Architectures XML and Java XML Development Tools (XML, DTD and Schema Editors) Summary Class Project Readings Assignment #1a 3 Old History Formatting Markups Rendition notations (e.g., LaTeX, TeX, RTF, MIF) Compatible with standard text editors Processed into presentations (printout, or electronic display) WYSIWYG What You See Is “ALL” You Get Meta-Markup Language GML (Goldfarb, Mosher, Lorie - IBM 1969) Generalized (i.e., indep. of systems, devices, applications) Markups (i.e., information related to struct. & content Language (i.e., methodology with formal syntax) Validation capabilities (1974) 4 2 SGML SGML (1978 - 10/15/86) Used by DoD for Continuous Acquisition and Lifecycle Support (CALS) http://www.oasis-open.org/cover/general.html SGML DTD or Schema <!DOCTYPE tutorials [ <!ELEMENT tutorials – (tutorial+)> <!ELEMENT tutorial – (title, intro, chap+)> <!ELEMENT title – O (#PCDATA)> <!ELEMENT intro – O (para+)> <!ELEMENT chap – O (title, para+)> <!ELEMENT para – O (#PCDATA)> ]> 5 SGML Markup <tutorials> <tutorial> <title>XML TUTORIAL <intro> <para>Required first paragraph of intro.
    [Show full text]
  • Voice and Multimodal Technology for the Mobile Worker
    VOICE AND MULTIMODAL TECHNOLOGY FOR THE MOBILE WORKER SUBMITTED: October 2003 REVISED: April 2004 PUBLISHED: August 2004 at http://www.itcon.org/2004/24/ EDITOR: D. Rebolj and K. Menzel Irina Kondratova, Group Leader, Human Web Group National Research Council of Canada, Institute for Information Technology e-Business, Canada email: [email protected] SUMMARY: The availability of real time, complete information exchange with the project information repository is critical for decision-making in construction, as information frequently has to be transmitted to and received from the project repository right on site. Information and Communication Technology, specifically wireless communications through mobile device, is seen as a key enabler of leading edge, innovative and powerful field solutions. However, the widespread usage of mobile devices is limited by antiquated and cumbersome interfaces. Speech recognition, along with VoiceXML technology on handheld smart device, should play a major role in overcoming user interface limitations for mobile devices and improve their usability for industrial field applications. This paper discusses the advantages of using VoiceXML technology for voice- enabled, construction field applications. It presents a pilot application of voice technology for inventory management, and outlines the direction of future research in the area of voice and multimodal communications that enable information mobility in AEC industry. KEYWORDS: mobile worker, multimodal interactions, speech recognition, VoiceXML,
    [Show full text]
  • W3C TAG Perspectives
    The future of applications: W3C TAG perspectives Henry S. Thompson School of Informatics University of Edinburgh W3C Technical Architecture Group 28 March 2011 * help? contents? restart? Copyright (C) 2011 Henry S. Thompson slide 1/23 The World Wide Web Consortium Founded by Tim Berners-Lee to sustain the value of the Web for everyone and "lead the Web to its full potential" Hosted by MIT in US, Keio University in Japan and ERCIM in Europe ~60 employees, about half working remotely Over 300 members: organisations and companies Recently awarded substantial support from ISOC Standards work carried out by Working Groups made up of member representatives and invited experts 100s of existing Recommendations, dozens in progress from >50 WGs Mostly 'horizontal' technologies HTML (itself, Forms, CSS) XML (itself, XSLT, Schema, Query, Processing Model, Linking) * help? contents? restart? Copyright (C) 2011 Henry S. Thompson slide 2/23 Multimedia (PNG, SVG, SMIL, VoiceXML) Mobile (Mobile Web Initiative ('one web'), Mobile CSS, Geospatial (!)) Semantic Web (RDF, OWL, Rules) Accessibility Internationalisation * help? contents? restart? Copyright (C) 2011 Henry S. Thompson slide 2/23 The Technical Architecture Group of the W3C Originally the Director (Tim B-L) was responsible for maintaining consistency across activities As the Consortium grew and the scope of its activities enlarged, this task became impossible The TAG was established eight years ago to pick up and broaden this task Identify and promote core principles of Web Architecture Look backwards at what has made the Web succeed And forwards to what must be done to protect that success While embracing as much as possible that emerges And, perhaps most importantly for tonight's panel * help? contents? restart? Copyright (C) 2011 Henry S.
    [Show full text]
  • Xml Based Framework for Contact Center Applications
    XML BASED FRAMEWORK FOR CONTACT CENTER APPLICATIONS Nikolay Anisimov, Brian Galvin and Herbert Ristock Genesys Telecommunication Laboratories (an Alcatel-Lucent company) 2001 Junipero Serra, Daly City, CA, USA Keywords: Call center, contact center application, VoiceXML, Call Control XML, organizational structure. Abstract: W3C languages, VoiceXML and CCXML all play an important role in contact centers (CC) by simplifying the creation of CC applications. However, they cover only a subset of contact center functions, such as simple call control and interactive voice response (IVR) with automatic speech recognition. We discuss ways to complement VoiceXML and CCXML in order to cover all necessary contact center functions required to script end-to-end interactions in a consistent and seamless way. For this purpose we introduce an XML forms-based framework called XContact comprising the CC platform and applications, multi-script and multi-browsing, and interaction data processing. We also discuss how routing as a key CC capability can be scripted/captured within such framework in order to demonstrate the overall approach. 1 INTRODUCTION center product cannot be easily transferred to another one. Contact centers (CC) play a very important role in A proven way of achieving application contemporary business. According to some uniformity, platform independence, and estimations (Batt et al, 2005, Brown et al, 2005, simplification of the task of creating business Gans et al, 2003) 70% of all business interactions applications is to employ XML-based standards and are handled in contact centers. In the U.S., the related technologies. XML is increasingly used as a number of all contact center workers is about 4 basis for building applications in different vertical million or 2.5-3% of the U.S.
    [Show full text]
  • Voicexml (VXML) 2.0
    Mobile Internet Applications─ XML-based Languages Lesson 03 XML based Standards and Formats for Applications © Oxford University Press 2018. All rights reserved. 1 Markup Language Format Stand- ardized For Specific Application • The tags, attributes, and XML-based language use the extensible property of XML • Defines a specific standardized sets of instances of the tags, attributes, their representation and behaviour, and other characteristics for using in that application. © Oxford University Press 2018. All rights reserved. 2 XForm • An XML format standardized for Specific Application needing UIs (user interfaces) like text area fields, buttons, check- boxes, and radios • Xform the fields (keys) which are initially specified • Fields either have no initial field values or default field values © Oxford University Press 2018. All rights reserved. 3 XForm • Presented to a user using a browser or presentation software and user interactions take place • The user supplies the values for these fields by entering text into the fields, checking the check-boxes, and selecting the radio © Oxford University Press 2018. All rights reserved. 4 XForm • The user then submits the XForm which is transmitted from client to server for carrying out the needed form processing • The server program can be at remote web server or at the device computing system © Oxford University Press 2018. All rights reserved. 5 XML for Forms─ XForms • An application may generate a form for answering the queries at server end, which needs to be filled and submitted by the client end • XForms is a form in XML format which specifies a data processing model for XML data and UIs for the XML data © Oxford University Press 2018.
    [Show full text]