Reducing the Description Amount in Authoring MMI Applications
Reducing the Description Amount in Authoring MMI Applications
Kouichi Katsurada, Kazumine Aoki, Hirobumi Yamada and Tsuneo Nitta
Graduate School of Knowledge-based Information Engineering Toyohashi University of Technology, Japan {katurada, nitta}@tutkie.tut.ac.jp, {aoki, yamada}@vox.tutkie.tut.ac.jp
Abstract describes outline of XISL2.0 and comparison with XISL1.1. Although an MMI description language XISL1.1 (eXtensible After discussing some future issues in section 4, we conclude Interaction Scenario Language) developed for web-based our work and show some future work in section 5. MMI applications has some desirable features such as high extensibility and controllability of modalities, it has some 2. XISL1.1 and Its Issues issues concerning capabilities for describing slot-filling style dialogs, a large amount of description for modality 2.1. Outline of XISL1.1 combination of inputs, and complicated authoring when handling XML contents. In this paper we provide a new XISL1.1 [5][6] is an XML-based language for describing version of XISL (XISL2.0) that resolves these issues by using MMI between a user and a system. In XISL1.1, a scenario is VoiceXML-based syntax, modality-independent input composed of a sequence of exchanges that contains a set of description, and XForms-like data model. The results of prompts for a user, a set of user's multimodal inputs and a set comparison between XISL1.1 and XISL2.0 showed that of system's actions. Actions include outputs to a user, simple XISL2.0 reduced the amount of description by 40% as arithmetic operations, conditional branches, dialog transition, compared with XISL1.1, and XISL2.0 succeeded to mitigate and so on. the difficulties in the authoring work of developing MMI Figure 1 shows a fragment of an XISL1.1 document for applications. an online shopping system. This example describes a scene in which the system asks a user which item to buy and asks how 1. Introduction many items to buy. The user can reply with some input patterns (selecting modalities from speech and pointing, and There has been proposed various types of multimodal whether inputs both the item and quantity or inputs only the interaction (MMI) systems and fundamentals for constructing item first). Hereinafter, we outline the syntax of XISL1.1 MMI applications. The WWW consortium organized a along this example. multimodal working group [1], and has standardized some An element and a multimodal input combination in MMI systems. As shown figure 1, the description becomes very long if all the types of modality combinations are described. One solution is to make input descriptions modality-independent so as to avoid this Figure 1: An example of MMI description with XISL1.1 difficulty. The third issue is that XISL1.1 needs a complicated CGI 2.2. Issues concerning XISL1.1 program for handling contents used in application. In figure 1, some elements are used to activate server-side CGI Although XISL1.1 has some desirable features in its that modifies XML contents. If some XML description and its extensibility and controllability of modalities, some issues control methods are introduced into XISL, the heavy load of became clear through developing many applications. The first CGI description is reduced, as well as the amount of server- issue is the problem appeared at describing slot-filling style client communication is decreased. dialogs. In the example shown in figure 1, the first is waiting for both an item and its quantity, while the second one is waiting for only an item. Although these Table 1: Amount of description for online shopping XISL1.1 XISL2.0 Orange Elements/attributes 412 246 2 File size (byte) 14442 7202 Table 2: Contribution of each factor Figure 3: EMMA result for application shown in figure 2 VoiceXML syntax 9.5% Modality independent description 25.7% XForms data-model -4.1% Other modification 9.2% Total 40.3% Table 3: CGI programs XISL1.1 XISL2.0 Number of programs 7 2 1.05 modalities/media in the MMI system. Then, an element ((4) in figure 2) is selected and a prompt is output. The element ((5) in figure 2) is an input slot that accepts a user’s input. In this example two elements are prepared for inputs concerning an item and its quantity. If : a is filled, the element ((6) in figure 2) in the is executed. The element ((7) in figure 2) is an XISL2.0 original tag which plays the same role as the Figure 4: A data-model for online shopping application element in XISL1.1. It is renamed because XISL2.0 introduces a new element which is used in