multimodal
25.4 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><!-- Generated from data/head.php, ../../smarty/{head.tpl} --><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><title>Multimodal Web Applications Current Status - W3C</title><link rel="stylesheet" href="/2008/site/css/minimum" type="text/css" media="handheld, all" /><style type="text/css" media="print, screen and (min-width: 481px)" xml:space="preserve">
@import url("/2008/site/css/advanced");
</style><link href="/2008/site/css/minimum" rel="stylesheet" type="text/css" media="handheld, only screen and (max-device-width: 480px)" /><meta name="viewport" content="width=device-width" /><link rel="stylesheet" href="/2008/site/css/print" type="text/css" media="print" /><link rel="shortcut icon" href="/2008/site/images/favicon.ico" type="image/x-icon" /></head><body id="www-w3-org" class="w3c_public"><div id="w3c_container">
<!-- Generated from data/mast.php, ../../smarty/{mast.tpl} -->
<div id="w3c_mast">
<!-- #w3c_mast / Page top header -->
<h1 class="logo">
<a tabindex="2" accesskey="1" href="/"><img src="/2008/site/images/logo-w3c-mobile-lg" width="90" height="53" alt="W3C" /></a>
<span class="alt-logo">W3C</span>
</h1>
<div id="w3c_nav">
<!-- Search form and media selection -->
<form action="/Help/search" method="get" enctype="application/x-www-form-urlencoded"><div class="w3c_sec_nav"><!-- --></div><ul class="main_nav"><li class="first-item">
<a href="/standards/">Standards</a>
</li><li>
<a href="/participate/">Participate</a>
</li><li>
<a href="/Consortium/membership">Membership</a>
</li><li class="last-item">
<a href="/Consortium/">About W3C</a>
</li><li class="search-item">
<div id="search-form">
<input tabindex="3" class="text" name="q" value="" title="Search" type="text" />
<button id="search-submit" name="search-submit" type="submit"><img class="submit" src="/2008/site/images/search-button" alt="Search" width="21" height="17" /></button>
</div>
</li></ul></form>
</div>
<!-- /end #w3c_nav -->
</div>
<!-- /end #w3c_mast -->
<div id="w3c_main">
<!-- Generated from data/crumbs.php, ../../smarty/{crumbs.tpl} -->
<div id="w3c_logo_shadow" class="w3c_leftCol">
<img height="32" alt="" src="/2008/site/images/logo-shadow" />
</div>
<div class="w3c_leftCol"><h2 class="offscreen">Site Navigation</h2>
<br /></div>
<div class="w3c_mainCol">
<div id="w3c_crumbs">
<div id="w3c_crumbs_frame">
<ul class="bct"> <!-- .bct / Breadcrumbs -->
<li class="skip"><a tabindex="1" accesskey="2" title="Skip to content (e.g., when browsing via audio)" href="#w3c_content_body">Skip</a></li>
<li><a href="/">W3C</a> <span class="cr">»</span> </li>
<li><a href="/standards/">Standards</a> <span class="cr">»</span> </li>
<li><a href="/TR/">All Standards and Drafts</a> <span class="cr">»</span> </li>
<li class="current">Multimodal Web Applications Current Status</li>
</ul>
</div>
</div>
<h1 class="title">Multimodal Web Applications Current Status</h1>
<ul class="w3c_toc">
<li>
<a href="#completed">completed work</a>
— including <a href="#stds">standards</a>
<span class="bullet">• </span>
</li>
<li>
<a href="#drafts">drafts</a>
</li>
</ul>
<div id="w3c_content_body">
<div id="w3c_generated_status">
<p id="w3c_toggle_include" class="default_open intro tPadding">This page summarizes the relationships among specifications, whether they are finished standards or drafts. Below, each title
links to the most recent version of a document.
For related introductory information, see: <a href="http://www.w3.org/standards/webofdevices/multimodal">Multimodal Access</a>.</p>
<h2 id="completed">Completed Work</h2>
<p>
<a href="/TR/tr-technology-stds">W3C Recommendations</a> have
been reviewed by W3C Members, by software developers, and by other
W3C groups and interested parties, and are endorsed by the
Director as Web Standards. Learn more about the <a href="/Consortium/Process/tr#rec-advance">W3C Recommendation
Track</a>.</p>
<p>
<a href="/2005/10/Process-20051014/tr.html#q75">Group Notes</a> are <em>not</em> standards and do not
have the same level of W3C endorsement.</p>
<h3 id="stds">Standards</h3>
<div class="data lMargin rMargin">
<table class="w3c_spec_summary_table">
<tbody>
<tr class="lastRow">
<td class="table_datecol">
<a href="../history/emma" title="EMMA: Extensible MultiModal Annotation markup language publication history">2009-02-10</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is REC" href="http://www.w3.org/TR/2009/REC-emma-20090210/">EMMA: Extensible MultiModal Annotation markup language</a>
</h4>
<p class="rec_support_data">
<a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=emma">translations</a>
·
<a href="http://www.w3.org/2009/02/emma-errata.html">errata</a>
</p>
<div class="expand_description">
<p>The W3C Multimodal Interaction Working Group aims to develop
specifications to enable access to the Web using multimodal
interaction. This document is part of a set of specifications for
multimodal systems, and provides details of an XML markup language
for containing and annotating the interpretation of user input.
Examples of interpretation of user input are a transcription into
words of a raw signal, for instance derived from speech, pen or
keystroke input, a set of attribute/value pairs describing their
meaning, or a set of attribute/value pairs describing a gesture.
The interpretation of the user's input is expected to be generated
by signal interpretation processes, such as speech and ink
recognition, semantic interpreters, and other types of processors
for use by components that act on the user's inputs such as
interaction managers.</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<h3 id="notes">Group Notes</h3>
<div class="data lMargin rMargin">
<table class="w3c_spec_summary_table">
<tbody>
<tr>
<td class="table_datecol">
<a href="../history/mmi-mcbp" title="Best practices for creating MMI Modality Components publication history">2011-03-01</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2011/NOTE-mmi-mcbp-20110301/">Best practices for creating MMI Modality Components</a>
</h4>
<div class="expand_description">
<p>
This document describes Modality Components in the MMI Architecture which
are responsible for controlling the various input and output modalities
on various devices by providing guidelines and suggestions for designing
Modality Components. Also this document shows several possible examples
of Modality Components, (1) face identification, (2) form-filling using
handwriting recognition and (3) video display.
</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/emma-usecases" title="Use Cases for Possible Future EMMA Features publication history">2009-12-15</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2009/NOTE-emma-usecases-20091215">Use Cases for Possible Future EMMA Features</a>
</h4>
<div class="expand_description">
<p>This is a sample short description for this specification;
over time we will replace this description with a real one.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/mmi-auth" title="Authoring Applications for the Multimodal Architecture publication history">2008-07-02</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2008/NOTE-mmi-auth-20080702/">Authoring Applications for the Multimodal Architecture</a>
</h4>
<div class="expand_description">
<p>This document describes a multimodal system which implements
the W3C Multimodal Architecture and gives an example of a
simple multimodal application authored using various W3C markup
languages, including SCXML, CCXML, VoiceXML 2.1 and HTML.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/mmi-suggestions" title="Common Sense Suggestions for Developing Multimodal User Interfaces publication history">2006-09-11</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2006/NOTE-mmi-suggestions-20060911/">Common Sense Suggestions for Developing Multimodal User Interfaces</a>
</h4>
<div class="expand_description">
<p>This document is based on the accumulated experience of several
years of developing multimodal applications. It provides a
collection of common sense advice for developers of multimodal
user interfaces.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/mmi-dev-feedback" title="Multimodal Application Developer Feedback publication history">2006-04-14</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2006/NOTE-mmi-dev-feedback-20060414/">Multimodal Application Developer Feedback</a>
</h4>
<div class="expand_description">
<p>Several years of multimodal application development in
various business areas and on various device platforms has
provided developers enough experience to provide detailed
feedback about what they like, dislike, and want to see
improve and continue. This experience is provided here as
an input to the specifications under development in the W3C
Multimodal Interaction
and Voice Browser
Activities.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/modality-interface" title="Modality Component to Host Environment DOM Requirements and Capabilities Assessment publication history">2004-05-10</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2004/NOTE-modality-interface-20040510/">Modality Component to Host Environment DOM Requirements and Capabilities Assessment</a>
</h4>
<div class="expand_description">
<p>This document describes the DOM capabilities needed to support a
heterogeneous multimodal environment and the current state of DOM
interfaces supporting those capabilities. These DOM interfaces are
used between modality components and their host environment in the
W3C Multimodal
Interaction Framework as proposed by the W3C Multimodal Interaction
Activity.</p>
<p>The Multimodal Interaction Framework separates multimodal
systems into a set of functional units, including Input and Output
components, an Interaction Mananger, Session Components, System and
Environment, and Application Functions. In order for those
functional components to interact with each other to form an
application interpreter, the browser implementation must allow for
communication and coordination between those components. This DOM
interface identifies the DOM APIs used to communicate and
coordinate at the browser implemention level. Multimodal browsers
can be stand-alone or distributed systems.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/mmi-framework" title="W3C Multimodal Interaction Framework publication history">2003-05-06</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2003/NOTE-mmi-framework-20030506/">W3C Multimodal Interaction Framework</a>
</h4>
<div class="expand_description">
<p>This document introduces the W3C Multimodal Interaction
Framework, and identifies the major components for multimodal
systems. Each component represents a set of related functions. The
framework identifies the markup languages used to describe
information required by components and for data flowing among
components. The W3C Multimodal Interaction Framework describes
input and output modes widely used today and can be extended to
include additional modes of user input and output as they become
available.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/EMMAreqs" title="Requirements for EMMA publication history">2003-01-13</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2003/NOTE-EMMAreqs-20030113">Requirements for EMMA</a>
</h4>
<div class="expand_description">
<p>This document describes requirements for the Extensible
MultiModal Annotation language (EMMA) specification under
development in the W3C Multimodal Interaction
Activity. EMMA is intended as a data format for the interface
between input processors and interaction management systems. It will
define the means for recognizers to annotate application specific
data with information such as confidence scores, time stamps, input
mode (e.g. key strokes, speech or pen), alternative recognition
hypotheses, and partial recognition results, etc. EMMA is a target
data format for the semantic interpretation specification being
developed in the Voice Browser Activity, and
which describes annotations to speech grammars for extracting
application specific data as a result of speech recognition. EMMA
supercedes earlier work on the natural language semantics markup
language in the Voice Browser Activity.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/mmi-reqs" title="Multimodal Interaction Requirements publication history">2003-01-08</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2003/NOTE-mmi-reqs-20030108/">Multimodal Interaction Requirements</a>
</h4>
<div class="expand_description">
<p>This document describes fundamental requirements for the
specifications under development in the W3C Multimodal Interaction
Activity. These requirements were derived from use case studies
as discussed in Appendix A. They have been
developed for use by the Multimodal Interaction
Working Group (W3C Members
only), but may also be relevant to other W3C working groups and
related external standard activities.</p>
<p>The requirements cover general issues, inputs, outputs,
architecture, integration, synchronization points, runtimes and
deployments, but this document does not address application or
deployment conformance rules.</p>
</div>
</td>
</tr>
<tr class="lastRow">
<td>
<a href="../history/mmi-use-cases" title="Multimodal Interaction Use Cases publication history">2002-12-04</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is NOTE" href="http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/">Multimodal Interaction Use Cases</a>
</h4>
<div class="expand_description">
<p>The W3C Multimodal
Interaction Activity is developing specifications as a basis
for a new breed of Web applications in which you can interact using
multiple modes of interaction, for instance, using speech, hand
writing, and key presses for input, and spoken prompts, audio and
visual displays for output. This document describes several use
cases for multimodal interaction and presents them in terms of
varying device capabilities and the events needed by each use case
to couple different components of a multimodal application.</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<h2 id="drafts">Drafts</h2>
<p>Below are draft documents:
<a href="/2005/10/Process-20051014/tr.html#RecsCR">Candidate Recommendations</a>, <a href="/2005/10/Process-20051014/tr.html#last-call">Last Call Drafts</a>, <a href="/2005/10/Process-20051014/tr.html#RecsWD">other Working Drafts</a>.
Some of these may become Web Standards through the <a href="/Consortium/Process/tr#rec-advance">W3C Recommendation Track
process</a>. Others may be published as Group Notes or
become obsolete specifications.</p>
<h3 id="cr">Candidate Recommendations</h3>
<div class="data lMargin rMargin">
<table class="w3c_spec_summary_table">
<tbody>
<tr class="lastRow">
<td class="table_datecol">
<a href="../history/mmi-arch" title="Multimodal Architecture and Interfaces publication history">2012-01-12</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is CR" href="http://www.w3.org/TR/2012/CR-mmi-arch-20120112/">Multimodal Architecture and Interfaces</a>
</h4>
<div class="expand_description">
<p>This document describes a loosely coupled architecture for
multimodal user interfaces, which allows for co-resident and
distributed implementations, and focuses on the role of markup and
scripting, and the use of well defined interfaces between its
constituents.</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<h3 id="lcwd">Last Call Drafts</h3>
<div class="data lMargin rMargin">
<table class="w3c_spec_summary_table">
<tbody>
<tr class="lastRow">
<td class="table_datecol">
<a href="../history/emotionml" title="Emotion Markup Language (EmotionML) 1.0 publication history">2011-04-07</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is LCWD" href="http://www.w3.org/TR/2011/WD-emotionml-20110407/">Emotion Markup Language (EmotionML) 1.0</a>
</h4>
<div class="expand_description">
<p>
As the web is becoming ubiquitous, interactive, and multimodal,
technology needs to deal increasingly with human factors, including
emotions. The present draft specification of Emotion Markup Language
1.0 aims to strike a balance between practical applicability and basis
in science. The language is conceived as a "plug-in" language suitable
for use in three different areas: (1) manual annotation of data; (2)
automatic recognition of emotion-related states from user behavior;
and (3) generation of emotion-related system behavior.
</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<h3 id="wd">Other Working Drafts</h3>
<div class="data lMargin rMargin">
<table class="w3c_spec_summary_table">
<tbody>
<tr class="lastRow">
<td class="table_datecol">
<a href="../history/emotion-voc" title="Vocabularies for EmotionML publication history">2011-04-07</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2011/WD-emotion-voc-20110407/">Vocabularies for EmotionML</a>
</h4>
<div class="expand_description">
<p>
This document represents a public collection of emotion vocabularies
that can be used with EmotionML. It was originally part of an earlier
draft of the EmotionML specification, but was moved out of it so that
we can easily update, extend and correct the list of vocabularies as
required.
</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
</div>
</div><!-- Generated from data/footer.php, ../../smarty/{footer-block.tpl} --><div id="w3c_footer">
<div id="w3c_footer-inner">
<h2 class="offscreen">Footer Navigation</h2>
<div class="w3c_footer-nav">
<h3>Navigation</h3>
<ul class="footer_top_nav"><li>
<a href="/">Home</a>
</li><li>
<a href="/standards/">Standards</a>
</li><li>
<a href="/participate/">Participate</a>
</li><li>
<a href="/Consortium/membership">Membership</a>
</li><li class="last-item">
<a href="/Consortium/">About W3C</a>
</li></ul>
</div>
<div class="w3c_footer-nav">
<h3>Contact W3C</h3>
<ul class="footer_bottom_nav"><li>
<a href="/Consortium/contact">Contact</a>
</li><li>
<a accesskey="0" href="/Help/">Help and FAQ</a>
</li><li>
<a href="/Consortium/sponsor/">Sponsor / Donate</a>
</li><li>
<a href="/Consortium/siteindex">Site Map</a>
</li><li>
<address id="w3c_signature">
<a href="mailto:site-comments@w3.org">Feedback</a> (<a href="http://lists.w3.org/Archives/Public/site-comments/">archive</a>)</address>
</li></ul>
</div>
<div class="w3c_footer-nav">
<h3>W3C Updates</h3>
<ul class="footer_follow_nav"><li>
<a href="http://twitter.com/W3C" title="Follow W3C on Twitter">
<img src="/2008/site/images/twitter-bird" alt="Twitter" width="78" height="83" class="social-icon" />
</a>
<a href="http://identi.ca/w3c" title="See W3C on Identica">
<img src="/2008/site/images/identica-logo" alt="Identica" width="91" height="83" class="social-icon" />
</a>
</li></ul>
</div>
<p class="copyright">Copyright © 2012 W3C <sup>®</sup> (<a href="http://www.csail.mit.edu/">
<acronym title="Massachusetts Institute of Technology">MIT</acronym>
</a>, <a href="http://www.ercim.eu/">
<acronym title="European Research Consortium for Informatics and Mathematics"> ERCIM</acronym>
</a>, <a href="http://www.keio.ac.jp/">Keio</a>) <a href="/Consortium/Legal/ipr-notice">Usage policies apply</a>.</p>
</div>
</div><!-- /end #footer --><!-- Generated from data/scripts.php, ../../smarty/{scripts.tpl} --><!-- At the bottom for performance reasons --><!-- Generated from data/scripts.php, ../../smarty/{scripts.tpl} --><!-- At the bottom for performance reasons --><div id="w3c_scripts">
<script type="text/javascript" src="/2008/site/js/main" xml:space="preserve"><!-- --></script>
</div></body></html>