index.html
20.6 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
<?xml version="1.0" encoding="utf-8"?>
<!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-US" lang="en-US">
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8"/>
<title>W3C Ubiquitous Web Domain</title>
<link href="http://www.w3.org/Guide/pubrules-style.css" rel="stylesheet"
type="text/css"/>
<link href="http://www.w3.org/Consortium/about-style.css" rel="stylesheet"
type="text/css"/>
</head>
<body>
<div id="navblock">
<p class="invisible">
<a href="#endnav" shape="rect">Skip navigation</a>
</p>
<ul id="nav">
<li>
<a href="/" shape="rect">W3C Home</a>
<ul class="level1">
<li id="current">Ubiquitous Web Domain<ul class="level2">
<li>
<a href="http://www.w3.org/Consortium/activities#UbiquitousWebDomain">Activities</a>
<ul class="level2">
<li>
<a href="http://www.w3.org/Mobile/">Mobile Web Initiative Activity</a>
</li>
<li>
<a href="http://www.w3.org/2002/mmi/">Multimodal Interaction Activity</a>
</li>
<li>
<a href="http://www.w3.org/2007/uwa/">Ubiquitous Web Applications Activity</a>
</li>
<li>
<a href="http://www.w3.org/Voice/">Voice Browser Activity</a>
</li>
<li>
<a href="http://www.w3.org/XML/">Extensible Markup Language (XML) Activity</a>
</li>
<li>
<a href="http://www.w3.org/2011/webtv/Activity.html">Web and TV Activity</a>
</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
</ul>
<p id="endnav"/>
</div>
<p>
<a href="http://www.w3.org/" shape="rect">
<img alt="W3C" width="72" height="48" src="http://www.w3.org/Icons/w3c_home"/>
</a>
<img alt="Ubiquitous Web" width="212" height="48"
src="http://www.w3.org/Icons/ubi212"/>
</p>
<h1 class="title">Ubiquitous Web Domain</h1>
<p>
<a href="#Mission" shape="rect">Mission</a> | <a href="#structure" shape="rect">Activities</a>
</p>
<p>Nearby: <a href="http://www.w3.org/People/domain?domain=Ubiquitous+Web" shape="rect">People of the Ubiquitous Web Domain</a>.</p>
<h2>
<a name="Mission" id="Mission" shape="rect">Mission</a>
</h2>
<p>W3C's Ubiquitous Web Domain is focusing on technologies to enable Web access
for anyone, anywhere, anytime, using any device. This includes Web access from
mobile phones as well as other emerging environments such as consumer
electronics, interactive television, and even automobiles. To enable the next
generation of Web user interfaces, we are working on device APIs, best
practices for mobile Web content and applications, VoiceXML and technologies
for multimodal interaction (EMMA, InkML). The device- and
application-independence of the Extensible Markup Language (XML) is a key
ingredient to the mission of the Domain, and the Ubiquitous Web Domain is
responsible for the ongoing development of XML and related specifications.</p>
<blockquote>
<p>"The Web is becoming more and more pervasive as an applications platform,
and effective standards are crucial for reducing the costs of deploying
applications across a wide range of devices and environments, whether in the
office, at home or on the move. The Ubiquitous Web will provide people with
access whenever and wherever they find themselves, with applications that
dynamically adapt to the user's needs, device capabilities and environmental
conditions. " <em>-- Philipp Hoschka, Ubiquitous Web Domain Leader</em>
</p>
</blockquote>
<div id="structure"><!--
This div @id=structure was generated; do not edit manually.
See http://www.w3.org/2007/05/domain/
--><h2>Activities</h2>
<ul>
<li>
<a href="#d7e0">Mobile Web Initiative Activity</a>
</li>
<li>
<a href="#d7e22">Multimodal Interaction Activity</a>
</li>
<li>
<a href="#d7e44">Ubiquitous Web Applications Activity</a>
</li>
<li>
<a href="#d7e75">Voice Browser Activity</a>
</li>
<li>
<a href="#d7e97">Extensible Markup Language (XML) Activity</a>
</li>
<li>
<a href="#d7e134">Web and TV Activity</a>
</li>
</ul>
<h3 id="d7e0">Mobile Web Initiative Activity</h3>
<p>From the introduction of the
<a href="http://www.w3.org/2005/MWI/Activity.html">Mobile Web Initiative Activity
Statement</a>:</p>
<blockquote>
<p>W3C’s Mobile Web Initiative addresses issues of interoperability and usability for the mobile Web through a concerted effort of key players in
the mobile production chain, including authoring tool vendors, content
providers, handset manufacturers, browser vendors and mobile operators.</p>
<p>Mobile Web access has many advantages. Unlike the fixed Web, the mobile
Web goes where you go. No longer do you have to remember to do something
on the Web when you get back to your computer. You can do it immediately,
within the context that made you want to use the Web in the first place.</p>
<p>With mobile devices, the Web reaches a much wider audience, and at all
times in all situations. It has the opportunity to reach into places where
wires cannot go, to places previously unthinkable (e.g., providing medical
information to mountain rescue scenes) and to accompany everyone as easily as
they carry the time in their wristwatches.</p>
<p>Moreover, today, many more people have access to mobile devices than
access to a desktop computer. This is very significant in
developing countries, where Web-capable mobile devices may play a similar
role for deploying widespread Web access as the mobile phone has played for
providing “plain old telephone service”.</p>
<p>Currently, the Mobile Web Initiative is focusing on the usage of the mobile Web for social development, and the supervision of work related to mobile devices across W3C groups.</p>
</blockquote>
<p>Read more on the <a href="http://www.w3.org/Mobile/">Mobile Web Initiative Activity home page</a>.</p>
<p>Dominique Hazaël-Massieux is the Activity Lead.</p>
<p>The Activity includes
this group: </p>
<ul>
<li>
<a href="http://www.w3.org/2008/MW4D/">Mobile Web For Social Development (MW4D) Interest Group</a>
</li>
</ul>
<h3 id="d7e22">Multimodal Interaction Activity</h3>
<p>From the introduction of the
<a href="http://www.w3.org/2002/mmi/Activity.html">Multimodal Interaction Activity
Statement</a>:</p>
<blockquote>
<p class="firstelement">The Multimodal Interaction Activity seeks to extend
the Web to allow users to dynamically select the most appropriate mode
of interaction for their current needs including any disabilities in
order to enable Web application developers to provide an effective user
interface for whichever modes the user selects.
With multimodal Web applications, users can provide input via speech,
handwriting and keystrokes, with output presented via displays,
pre-recorded and synthetic speech, audio, and tactile mechanisms such
as mobile phone vibrators and Braille strips.</p>
<p>The goal of the Multimodal Interaction Activity is to clearly
define how to author concrete multimodal Web applications, for
example, coupling a local GUI (e.g., HTML user agent) with a remote
Speech I/F (e.g., VoiceXML user agent).
The Multimodal Interaction Working Group is important as a central
point of coordination within W3C for multimodal activities, and
the group collaborates with other related Working Groups, e.g.
Voice Browser,
Scalable Vector Graphics,
Compound Document Formats,
Web Applications and
Ubiquitous Web Applications.
</p>
</blockquote>
<p>Read more on the <a href="http://www.w3.org/2002/mmi/">Multimodal Interaction Activity home page</a>.</p>
<p>Kazuyuki Ashimura is the Activity Lead.</p>
<p>The Activity includes
this group: </p>
<ul>
<li>
<a href="http://www.w3.org/2002/mmi/Group/">Multimodal Interaction Working Group</a>
</li>
</ul>
<h3 id="d7e44">Ubiquitous Web Applications Activity</h3>
<p>From the introduction of the
<a href="http://www.w3.org/2007/uwa/Activity.html">Ubiquitous Web Applications Activity
Statement</a>:</p>
<blockquote>
<p class="firstelement">The Ubiquitous Web Applications Activity
was launched on 30 March 2007 with the vision of enabling value-added
services and business models for ubiquitous networked devices, based
upon W3C's strengths in declarative representations. The Activity
includes the <a href="/2008/geolocation/" shape="rect">Geolocation Working
Group</a>, the <a href="/2007/uwa/" shape="rect">Ubiquitous Web Applications
Working Group</a> (closed), the <a href="/2009/dap/" shape="rect">Device APIs and Policy
Working Group</a>, the <a href="/2010/POI/" shape="rect">Points of Interest Working Group</a> and the <a href="/2011/04/webrtc/" shape="rect">Web Real-Time Communications Working Group
</a>.</p>
<ul>
<li>The <a href="/2008/geolocation/" shape="rect">Geolocation Working Group</a>
is defining a secure and privacy-sensitive interface for using
client-side location information in location-aware Web applications.
A geolocation API for accessing device location is under development,
and in addition, the Working Group may explore exposing location
information via markup or HTTP headers. The Working Group is tasked
with identifying and addressing requirements for security and
privacy protection.</li>
<li>The <a href="/2010/POI/" shape="rect">Points of Interest Working
Group</a> is developing technical specifications for the
representation of "Points of Interest" (POI) information on the Web.
POI data is used in many types of applications including Augmented
Reality, map navigation, and location based social-networking games.
</li>
<li>The <a href="/2009/dap/" shape="rect">Device APIs and Policy Working Group</a>
is creating client side programming interfaces to enable Web
applications and widgets to access device services, including the
calendar, contacts, camera, etc. The group will also provide
a framework for expressing security policies to govern access
to these APIs.
</li>
<li>The <a href="/2011/04/webrtc/" shape="rect">Web Real-Time Communications Working Group's</a> goal is to define client-side APIs to enable Real-Time Communications in Web browsers. These APIs will enable applications that can be run directly inside the browser, to communicate in real-time, directly with other Web applications.
</li>
</ul>
</blockquote>
<p>Read more on the <a href="http://www.w3.org/2007/uwa/">Ubiquitous Web Applications Activity home page</a>.</p>
<p>Matt Womer is the Activity Lead.</p>
<p>The Activity includes
these groups: </p>
<ul>
<li>
<a href="http://www.w3.org/2009/dap/">Device APIs Working Group</a>
</li>
<li>
<a href="http://www.w3.org/2008/geolocation/">Geolocation Working Group</a>
</li>
<li>
<a href="http://www.w3.org/2010/POI/">Points of Interest Working Group</a>
</li>
<li>
<a href="http://www.w3.org/2011/04/webrtc/">Web Real-Time Communications Working Group</a>
</li>
<li>
<a href="http://www.w3.org/2011/mbui/">Model-Based User Interfaces Working Group</a>
</li>
</ul>
<h3 id="d7e75">Voice Browser Activity</h3>
<p>From the introduction of the
<a href="http://www.w3.org/Voice/Activity.html">Voice Browser Activity
Statement</a>:</p>
<blockquote>
<p class="firstelement">
The telephone was invented in the 1870s and continues to be a very
important means for people to communicate with each other.
The Web by comparison is very recent, but is rapidly becoming a
competing communications channel.
The convergence of telecommunications and the Web is now bringing the
benefits of Web technology to the telephone, enabling Web developers
to create applications that can be accessed via any telephone, and
allowing people to interact with these applications via speech and
telephone keypads.
Historically
<a href="/Voice/Group/#Documents_and_Technical_Reports" shape="rect">
W3C's standardization work on Voice technology</a> of
<a href="/Voice/Group/" shape="rect">
the Voice Browser Working Group</a> was driven by the needs of call center
telephony.
However, today's mobile devices use not only the visual user interface
but also the speech interface for accessing the Web, so the work is
now driven by mobile device needs as well.
Visual interfaces are very useful for accessing the Web but there are
several possible barriers of communication only with the visual
interface on small devices, and Voice technology could be a promising
solution to the barriers.
For example, Voice is available on any kind of phones and in all kinds
of languages. Also it requires much less training to use since it is
more natural than usual visual user interfaces.
</p>
</blockquote>
<p>Read more on the <a href="http://www.w3.org/Voice/">Voice Browser Activity home page</a>.</p>
<p>Matt Womer is the Activity Lead.</p>
<p>The Activity includes
this group: </p>
<ul>
<li>
<a href="http://www.w3.org/Voice/Group/">Voice Browser Working Group</a>
</li>
</ul>
<h3 id="d7e97">Extensible Markup Language (XML) Activity</h3>
<p>From the introduction of the
<a href="http://www.w3.org/XML/Activity.html">Extensible Markup Language (XML) Activity
Statement</a>:</p>
<blockquote>
<p class="firstelement">The Extensible Markup Language
(<a href="http://www.w3.org/XML/" shape="rect">XML</a>)
is a simple, flexible text format derived from SGML (ISO 8879).
The W3C created and maintais the XML specification.
The W3C is also the primary center for developing other
cross-industry specifications that are based on XML.
Some of these are done within the XML Activity, such as XML
Query and XML Schema, and some (such sa SVG) in other W3C areas.
The XML Activity tries to keep a balance between maintaining
stability and backwards
compatibility, making improvements that help to encourage
interoperability, and bringing new communities into the world of XML.
</p>
</blockquote>
<p>Read more on the <a href="http://www.w3.org/XML/">Extensible Markup Language (XML) Activity home page</a>.</p>
<p>Liam Quin is the Activity Lead.</p>
<p>The Activity includes
these groups: </p>
<ul>
<li>
<a href="http://www.w3.org/XML/EXI/">Efficient XML Interchange Working Group</a>
</li>
<li>
<a href="http://www.w3.org/XML/Group/">XML Coordination Group</a>
</li>
<li>
<a href="http://www.w3.org/XML/Core/">XML Core Working Group</a>
</li>
<li>
<a href="http://www.w3.org/XML/Processing/">XML Processing Model Working Group</a>
</li>
<li>
<a href="http://www.w3.org/XML/Query/">XML Query Working Group</a>
</li>
<li>
<a href="http://www.w3.org/XML/Schema">XML Schema Working Group</a>
</li>
<li>
<a href="http://www.w3.org/Style/XSL/">XSLT Working Group</a>
</li>
<li>
<a href="http://www.w3.org/XML/XPPL/">XML Print and Page Layout Working Group</a>
</li>
</ul>
<h3 id="d7e134">Web and TV Activity</h3>
<p>From the introduction of the
<a href="http://www.w3.org/2011/webtv/Activity.html">Web and TV Activity
Statement</a>:</p>
<blockquote>
<p>The main goal of this activity is to clarify the relationship between Web and TV, with a view to identifying work items either in the form of new W3C Working Groups, or specific work that should be done in existing Working Groups.</p>
<p>TV is a mature but rapidly-changing market. With the advent of IP-based devices, connected TVs are progressing at a fast pace and traditional TV broadcasting is quickly evolving into a more immersive experience where users can interact with rich applications that are at least partly based on Web technologies. There is strong growth in the deployment of devices that integrate regular Web technologies such as HTML, CSS, and SVG, coupled with various device APIs.</p>
<p>There is huge potential for the future to create an interoperable platform where Web and TV benefit from each other, for instance through the introduction of additional device APIs specifically targeted at TVs, or by bringing Web accessibility guidelines to TVs.</p>
</blockquote>
<p>Read more on the <a href="http://www.w3.org/2011/webtv/Activity.html">Web and TV Activity home page</a>.</p>
<p>Kazuyuki Ashimura is the Activity Lead.</p>
<p>The Activity includes
this group: </p>
<ul>
<li>
<a href="http://www.w3.org/2011/webtv/">Web and TV Interest Group</a>
</li>
</ul>
</div>
<h2>Support</h2>
<p>The activities of the Ubiquitous Web Domain are partially supported by
the follwing EU commission projects:</p>
<ul>
<li>
<a href="http://mobiweb.eu" shape="rect">MobiWebApp (Mobile Web Applications)</a>
</li>
<li>
<a href="http://openmediaweb.eu" shape="rect">OMWeb (Open Media Web)</a>
</li>
<li>
<a href="http://www.serenoa-fp7.eu" shape="rect">Serenoa</a>
</li>
<li>
<a href="http://webinos.org" shape="rect">Webinos</a>
</li>
</ul>
<hr/>
<address>
<a href="http://www.w3.org/People/all#ph" shape="rect">Philipp Hoschka</a>,
Ubiquitous Web Domain Leader<br/>
$Date: 2011/10/19 05:00:37 $
</address>
<p class="copyright">
<a rel="Copyright" href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright"
shape="rect">Copyright</a> © 2001-<span class="endyear">2011</span>
<a href="http://www.w3.org/" shape="rect">
<acronym title="World Wide Web Consortium">W3C</acronym>
</a>
<sup>®</sup> (<a href="http://www.lcs.mit.edu/" shape="rect">
<acronym title="Massachusetts Institute of Technology">MIT</acronym>
</a>, <a href="http://www.ercim.org/" shape="rect">
<acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym>
</a>, <a href="http://www.keio.ac.jp/" shape="rect">Keio</a>), All Rights
Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer"
shape="rect">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks"
shape="rect">trademark</a>, <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/copyright-documents"
shape="rect">document use</a> and <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/copyright-software"
shape="rect">software licensing</a> rules apply. Your interactions with this
site are in accordance with our <a href="http://www.w3.org/Consortium/Legal/privacy-statement#Public" shape="rect">public</a> and <a href="http://www.w3.org/Consortium/Legal/privacy-statement#Members"
shape="rect">Member</a> privacy statements.</p>
</body>
</html>