index.html 46.5 KB

Raw Blame History Permalink

<!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>Web of Devices - W3C</title><link rel="Help" href="/Help/" /><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" /><link rel="alternate" type="application/atom+xml" title="W3C News" href="news.xml" /></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">
<form action="/Help/search" method="get" enctype="application/x-www-form-urlencoded"><!-- w3c_sec_nav is populated through js --><div class="w3c_sec_nav"><!-- --></div><ul class="main_nav"><!-- Main navigation menu --><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>
</div>
<!-- /end #w3c_mast -->
<div id="w3c_main">
<div id="w3c_logo_shadow" class="w3c_leftCol"><img width="100%" height="32" alt="" src="/2008/site/images/logo-shadow" /></div>
<div class="w3c_leftCol"><h2 class="offscreen">Site Navigation</h2>
    <h3 class="category"><span class="ribbon"><a href="/standards/" title="Up to Standards">Standards <img src="/2008/site/images/header-link" alt="Header link" width="13" height="13" class="header-link" /></a></span></h3>
       <ul class="theme">
        <li><a href="/standards/webdesign/">Web Design and Applications</a></li>
        <li><a href="/standards/webarch/">Web Architecture</a></li>
        <li><a href="/standards/semanticweb/">Semantic Web</a></li>
        <li><a href="/standards/xml/">XML Technology</a></li>
        <li><a href="/standards/webofservices/">Web of Services</a></li>
        <li><a class="current">Web of Devices</a></li>
        <li><a href="/standards/agents/">Browsers and Authoring Tools</a></li>
        <li><a href="/TR/">All Standards and Drafts</a></li>
        <li><a href="/standards/about.html">About W3C Standards</a></li>
       </ul>
       <br /></div>
<div class="w3c_mainCol">
<!-- Generated from data/crumbs.php, ../../smarty/{crumbs.tpl} -->
<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>&#xA0;<span class="cr">&#xBB;</span>&#xA0;</li>
          <li><a href="/standards/">Standards</a>&#xA0;<span class="cr">&#xBB;</span>&#xA0;</li>
          <li class="current">Web of Devices</li>
        </ul>
     </div>
    </div>
<h1 class="title">
   <img src="/2008/site/images/theme-devices" alt="" />Web of Devices</h1>
<ul class="w3c_toc"><li class="toc_prefix">On this page &#x2192; </li><li>
    <a href="#w3c_overview">technology&#xA0;topics</a>
    <span class="bullet">&#x2022;</span>
  </li><li>
    <a href="#recent">news</a>
    <span class="bullet">&#x2022;</span>
  </li><li>
    <a href="#upcomingevents">upcoming&#xA0;events&#xA0;and&#xA0;talks</a>
      </li></ul>
<div id="w3c_content_body">
<div class="line">
<div class="intro">
<p>W3C is focusing on technologies to enable Web access anywhere, anytime, using any device. This includes Web access from mobile phones and other mobile devices as well as use of Web technology in consumer electronics, printers, interactive television, and even automobiles.</p>
</div>
</div>
<!-- Generated from data/bucket_1_on_3.php, ../../smarty/{bucket_1_on_n.tpl} -->
<div id="w3c_overview">
   <div class="line">
      <div class="unit size1on3">
         <h2 class="w3c_topic">
            <a href="/standards/webdesign/mobilweb">Mobile Web <img src="/2008/site/images/header-link" alt="Header link" width="13" height="13" class="header-link" />
            </a>
         </h2>
         <p class="tPadding0">
	  W3C promotes &#x201C;One Web&#x201D; that is available on any device.
	  W3C&#x2019;s Mobile Web Initiative helps ensure the
	  best user experience on mobile devices, taking into
	  account device capabilities, location, and other context information.
      </p>
      </div>
      <div class="unit size1on3">
         <h2 class="w3c_topic">
            <a href="/standards/webofdevices/voice">Voice Browsing <img src="/2008/site/images/header-link" alt="Header link" width="13" height="13" class="header-link" />
            </a>
         </h2>
         <p class="tPadding0">
The W3C Speech Interface Framework is a suite of specifications (e.g. VoiceXML) integrating Web technology and speech interaction. VoiceXML, PLS, SISR, SRGS, SCXML, and CCXML all contribute
	to the Speech Interface Framework.
      </p>
      </div>
      <div class="unit size1on3 lastUnit">
         <h2 class="w3c_topic">
            <a href="/standards/webofdevices/independence">Device Independence and Content Adaptation <img src="/2008/site/images/header-link" alt="Header link" width="13" height="13" class="header-link" />
            </a>
         </h2>
         <p class="tPadding0">
Devices come in many shapes, capabilities and sizes which define constraints on the content these devices can handle. Device descriptions, content transformation guidelines, device APIs and CC/PP help developers to optimize the user experience.
      </p>
      </div>
   </div>
   <div class="line">
      <div class="unit size1on3">
         <h2 class="w3c_topic">
            <a href="/standards/webofdevices/multimodal">Multimodal Access <img src="/2008/site/images/header-link" alt="Header link" width="13" height="13" class="header-link" />
            </a>
         </h2>
         <p class="tPadding0">
Increasingly, interactions with devices doesn&#x2019;t only happen with a keyboard, but also through voice, touch and gestures. The W3C Multimodal architecture and its components (EMMA, InkML) allow developers to adapt applications to new interaction modes.
      </p>
      </div>
      <div class="unit size1on3">
         <h2 class="w3c_topic">
            <a href="/standards/webofdevices/tv">Web and TV <img src="/2008/site/images/header-link" alt="Header link" width="13" height="13" class="header-link" />
            </a>
         </h2>
         <p class="tPadding0">
	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>
      </div>
   </div>
</div>
<div class="line">
<div id="recentnews" class="hierarchy hentry_list">
<h2 id="recent">News
<a title="Subscribe to News" href="http://www.w3.org/standards/webofdevices/news.xml" class="feedlink">
<img width="30" height="30" alt="Atom" src="/2008/site/images/icons/atom30" />
</a></h2>
<div class="hentry expand_block">
<div class="headline">
<h3 class="tPadding0 bPadding0 entry-title">
<span class="expand_section">
<a class="uri url" href="http://mobiwebapp.eu/2012/01/06/early-bird-deadline-to-end-soon-for-mwabp/">
Early bird rate ends soon for the MWABP course</a>
</span>
</h3>
<p class="date">
<abbr class="published" title="2012-01-06">06
January 2012</abbr>
</p>
<p class="author vcard">from
<a class="fn org url" href="http://www.w3.org/Mobile/">Mobile Web @
W3C - W3C</a></p>
</div>
<div class="expand_description entry-content"><p>Just a quick reminder that the early bird rate for the W3C
&#x201C;Mobile Web and Application Best Practices&#x201D; (MWABP) acclaimed
course is expiring next Monday. Do
<a href="http://www.w3techcourses.com/login/index.php">
register</a>before 9 January 2012 eod, and save 60 Euros!</p><p>This 3rd edition of the MWABP course will start on 30 January,
and will last 8 weeks. Participants are expected to spend an
average of 4-6 hours per week to both learn the course material and
work on&#xA0; the assignments.</p><p>The course will be lead by trainers Frances de Waal and Phil
Archer. Read the
<a href="http://www.w3devcampus.com/mobile-web-and-application-best-practices-training/">
past students&#x2019; feedback and find out more about the course</a> . And
again, do not forget to
<a href="http://www.w3techcourses.com/course/view.php?id=14">
register</a>before 9 January 2012 to benefit from the early bird
rate!</p><p>
<br />
<a href="http://feeds.wordpress.com/1.0/gocomments/mobiwebappw3c.wordpress.com/727/">

<img alt="" src="http://feeds.wordpress.com/1.0/comments/mobiwebappw3c.wordpress.com/727/" />
</a>
<a href="http://feeds.wordpress.com/1.0/godelicious/mobiwebappw3c.wordpress.com/727/">

<img alt="" src="http://feeds.wordpress.com/1.0/delicious/mobiwebappw3c.wordpress.com/727/" />
</a>
<a href="http://feeds.wordpress.com/1.0/gofacebook/mobiwebappw3c.wordpress.com/727/">

<img alt="" src="http://feeds.wordpress.com/1.0/facebook/mobiwebappw3c.wordpress.com/727/" />
</a>
<a href="http://feeds.wordpress.com/1.0/gotwitter/mobiwebappw3c.wordpress.com/727/">

<img alt="" src="http://feeds.wordpress.com/1.0/twitter/mobiwebappw3c.wordpress.com/727/" />
</a>
<a href="http://feeds.wordpress.com/1.0/gostumble/mobiwebappw3c.wordpress.com/727/">

<img alt="" src="http://feeds.wordpress.com/1.0/stumble/mobiwebappw3c.wordpress.com/727/" />
</a>
<a href="http://feeds.wordpress.com/1.0/godigg/mobiwebappw3c.wordpress.com/727/">

<img alt="" src="http://feeds.wordpress.com/1.0/digg/mobiwebappw3c.wordpress.com/727/" />
</a>
<a href="http://feeds.wordpress.com/1.0/goreddit/mobiwebappw3c.wordpress.com/727/">

<img alt="" src="http://feeds.wordpress.com/1.0/reddit/mobiwebappw3c.wordpress.com/727/" />
</a>
<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=mobiwebapp.eu&amp;blog=14776567&amp;post=727&amp;subd=mobiwebappw3c&amp;ref=&amp;feed=1" width="1" height="1" />
</p></div>
</div>
<div class="hentry closed expand_block">
<div class="headline">
<h3 class="tPadding0 bPadding0 entry-title">
<span class="expand_section">
<a class="uri url" href="http://mobiwebapp.eu/2011/12/13/registration-opens-for-3rd-edition-of-the-mobile-web-training-course/">
Registration opens for 3rd edition of the Mobile Web training
course</a>
</span>
</h3>
<p class="date">
<abbr class="published" title="2011-12-13">13
December 2011</abbr>
</p>
<p class="author vcard">from
<a class="fn org url" href="http://www.w3.org/Mobile/">Mobile Web @
W3C - W3C</a></p>
</div>
<div class="expand_description entry-content"><p>W3C is pleased to announce a third edition of its most
popular online training course, &#x201C;
<strong>Introduction to Mobile Web and Application Best
Practices</strong>&#x201C;:</p><ul class="show_items">
<li>
<strong>Start date</strong>: 30 January 2012</li>
<li>
<strong>Duration</strong>: 8 weeks</li>
<li>
<strong>Early bird price</strong>: 165&#x20AC; (until 9 Jan. 2012)</li>
<li>Full price: 225&#x20AC;</li>
<li>
<a href="http://www.w3devcampus.com/mobile-web-and-application-best-practices-training/">
Course description and other details</a>
</li>
<li>
<a href="http://www.w3techcourses.com/course/view.php?id=14">
Register</a>to this course</li>
</ul><p>During the course, participants will:</p><ul class="show_items">
<li>learn about and use the recommended versions of HTML and CSS to
use for mobile today;</li>
<li>understand the constraints of working on mobile and how to
overcome them to deliver the best possible experience to the widest
range of users;</li>
<li>practice client side and server side content adaptation
techniques;</li>
<li>learn about and use the exciting new APIs available on modern
mobile platforms.</li>
</ul><p>The course will be lead by trainers Frances de Waal and Phil
Archer. Read the
<a href="http://www.w3devcampus.com/mobile-web-and-application-best-practices-training/">
past students&#x2019; feedback and find out more about the course</a> . And
do not forget to
<a href="http://www.w3techcourses.com/course/view.php?id=14">
register</a>before 9 January 2012 to benefit from the early bird
rate!</p><p>
<br />
<a href="http://feeds.wordpress.com/1.0/gocomments/mobiwebappw3c.wordpress.com/712/">

<img alt="" src="http://feeds.wordpress.com/1.0/comments/mobiwebappw3c.wordpress.com/712/" />
</a>
<a href="http://feeds.wordpress.com/1.0/godelicious/mobiwebappw3c.wordpress.com/712/">

<img alt="" src="http://feeds.wordpress.com/1.0/delicious/mobiwebappw3c.wordpress.com/712/" />
</a>
<a href="http://feeds.wordpress.com/1.0/gofacebook/mobiwebappw3c.wordpress.com/712/">

<img alt="" src="http://feeds.wordpress.com/1.0/facebook/mobiwebappw3c.wordpress.com/712/" />
</a>
<a href="http://feeds.wordpress.com/1.0/gotwitter/mobiwebappw3c.wordpress.com/712/">

<img alt="" src="http://feeds.wordpress.com/1.0/twitter/mobiwebappw3c.wordpress.com/712/" />
</a>
<a href="http://feeds.wordpress.com/1.0/gostumble/mobiwebappw3c.wordpress.com/712/">

<img alt="" src="http://feeds.wordpress.com/1.0/stumble/mobiwebappw3c.wordpress.com/712/" />
</a>
<a href="http://feeds.wordpress.com/1.0/godigg/mobiwebappw3c.wordpress.com/712/">

<img alt="" src="http://feeds.wordpress.com/1.0/digg/mobiwebappw3c.wordpress.com/712/" />
</a>
<a href="http://feeds.wordpress.com/1.0/goreddit/mobiwebappw3c.wordpress.com/712/">

<img alt="" src="http://feeds.wordpress.com/1.0/reddit/mobiwebappw3c.wordpress.com/712/" />
</a>
<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=mobiwebapp.eu&amp;blog=14776567&amp;post=712&amp;subd=mobiwebappw3c&amp;ref=&amp;feed=1" width="1" height="1" />
</p></div>
</div>
<div class="hentry closed expand_block">
<div class="headline">
<h3 class="tPadding0 bPadding0 entry-title">
<span class="expand_section">
<a class="uri url" href="http://www.w3.org/blog/International/2011/12/09/w3c-workshop-call-for-participation-the-multilingual-web-%e2%80%93-the-way-ahead/">
W3C Workshop, Call for Participation: The Multilingual Web &#x2013; The
Way Ahead</a>
</span>
</h3>
<p class="date">
<abbr class="published" title="2011-12-09">09
December 2011</abbr>
</p>
<p class="author vcard">from
<a class="fn org url" href="http://www.w3.org/blog/International">
Internationalization Activity Blog &#xBB; w3cWebOfDevices</a></p>
</div>
<div class="expand_description entry-content"><div class="lMargin"><p>
<img src="http://www.w3.org/International/multilingualweb/images/mlw-logo.png" alt=" " />
</p></div><p>
<strong>15 &#x2013; 16 March 2012, Luxembourg</strong>. Co-located with
the European Commission&#x2019;s Language Technology Showcase Days, and
hosted by the Directorate-General for Translation (DGT) of the
European Commission.</p><p>The
<a href="http://www.multilingualweb.eu/">MultilingualWeb
project</a>is looking at best practices and standards related to
all aspects of creating, localizing and deploying the Web
multilingually. The project aims to raise the visibility of
existing best practices and standards and identify gaps. The core
vehicle for this is a series of four events which are planned over
two years.</p><p>After three highly successful workshops in Madrid, Pisa, and
Limerick, this final workshop in the series will continue to
investigate currently available best practices and standards aimed
at helping content creators, localizers, tools developers, and
others meet the challenges of the multilingual Web.</p><p>Participation is free. We welcome participation from both
speakers and non-speaking attendees. For more information, see the
<a href="http://www.multilingualweb.eu/register">Call for
Participation</a></p></div>
</div>
<div class="hentry closed expand_block">
<div class="headline">
<h3 class="tPadding0 bPadding0 entry-title">
<span class="expand_section">
<a class="uri url" href="http://mobiwebapp.eu/2011/12/06/november-update-to-standards-for-web-applications-on-mobile/">
November Update to Standards for Web Applications on Mobile</a>
</span>
</h3>
<p class="date">
<abbr class="published" title="2011-12-06">06
December 2011</abbr>
</p>
<p class="author vcard">from
<a class="fn org url" href="http://www.w3.org/Mobile/">Mobile Web @
W3C - W3C</a></p>
</div>
<div class="expand_description entry-content"><p>Back in February, I
<a href="http://mobiwebapp.eu/2011/02/24/towards-a-w3c-mobile-web-applications-standardization-roadmap/">
announced</a> the start of a series of updates for a
<a href="http://www.w3.org/2011/02/mobile-web-app-state.html">
standardization roadmap for Web applications on mobile devices</a> ,
a compilation of the most relevant current and upcoming
technologies to develop Web applications well-fitted to mobile
devices, which was again updated in
<a href="http://www.w3.org/2011/05/mobile-web-app-state.html">
May</a> and
<a href="http://www.w3.org/2011/08/mobile-web-app-state.html">
August 2011</a>.</p><p>I have just released
<strong>
<a href="http://www.w3.org/2011/11/mobile-web-app-state.html">a
fourth update to that document</a>
</strong>that takes into account the many changes that have
occurred in the past 3 months. Among the highlights:</p><ul class="show_items">
<li>the publication of the first draft of the
<a href="http://www.w3.org/TR/webrtc/">Web Real-Time
Communications</a>APIs, including work on the API to access the
camera and microphone;</li>
<li>progress on device APIs such as the
<a href="http://www.w3.org/TR/vibration/">Vibration API</a> (first
draft),
<a href="http://www.w3.org/TR/battery-status/">battery
status</a> (last call),
<a href="http://www.w3.org/TR/touch-events/">touch events</a> (last
call),
<a href="http://www.w3.org/TR/orientation-event/">
accelerometer/gyroscope support</a>(last call).</li>
</ul><p>The next smaller iteration of this document will be provided end
of February, in time for Mobile Word Congress 2012. Stay tuned!</p><p>
<br />
<a href="http://feeds.wordpress.com/1.0/gocomments/mobiwebappw3c.wordpress.com/692/">

<img alt="" src="http://feeds.wordpress.com/1.0/comments/mobiwebappw3c.wordpress.com/692/" />
</a>
<a href="http://feeds.wordpress.com/1.0/godelicious/mobiwebappw3c.wordpress.com/692/">

<img alt="" src="http://feeds.wordpress.com/1.0/delicious/mobiwebappw3c.wordpress.com/692/" />
</a>
<a href="http://feeds.wordpress.com/1.0/gofacebook/mobiwebappw3c.wordpress.com/692/">

<img alt="" src="http://feeds.wordpress.com/1.0/facebook/mobiwebappw3c.wordpress.com/692/" />
</a>
<a href="http://feeds.wordpress.com/1.0/gotwitter/mobiwebappw3c.wordpress.com/692/">

<img alt="" src="http://feeds.wordpress.com/1.0/twitter/mobiwebappw3c.wordpress.com/692/" />
</a>
<a href="http://feeds.wordpress.com/1.0/gostumble/mobiwebappw3c.wordpress.com/692/">

<img alt="" src="http://feeds.wordpress.com/1.0/stumble/mobiwebappw3c.wordpress.com/692/" />
</a>
<a href="http://feeds.wordpress.com/1.0/godigg/mobiwebappw3c.wordpress.com/692/">

<img alt="" src="http://feeds.wordpress.com/1.0/digg/mobiwebappw3c.wordpress.com/692/" />
</a>
<a href="http://feeds.wordpress.com/1.0/goreddit/mobiwebappw3c.wordpress.com/692/">

<img alt="" src="http://feeds.wordpress.com/1.0/reddit/mobiwebappw3c.wordpress.com/692/" />
</a>
<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=mobiwebapp.eu&amp;blog=14776567&amp;post=692&amp;subd=mobiwebappw3c&amp;ref=&amp;feed=1" width="1" height="1" />
</p></div>
</div>
<div class="hentry closed expand_block">
<div class="headline">
<h3 class="tPadding0 bPadding0 entry-title">
<span class="expand_section">
<a class="uri url" href="http://www.w3.org/QA/2011/11/from_hypertext_to_hyperdevices.html">
From hypertext to hyperdevices</a>
</span>
</h3>
<p class="date">
<abbr class="published" title="2011-11-22">22
November 2011</abbr>
</p>
<p class="author vcard">from
<a class="fn org url" href="http://www.w3.org/Mobile/">Mobile Web @
W3C - W3C</a></p>
</div>
<div class="expand_description entry-content"><p>When the Web started some 20 years ago, it brought a platform
for distributing and accessing text, with an added dimension
brought by links:
<strong>hypertext</strong>. Because it was free and could be
deployed everywhere easily, it was a revolution.</p><p>For the past few years, we've seen this additional dimension
brought to media content, building hypermedia: SVG and canvas make
it possible to build graphics that integrate or link to content
from various sources, the addition of the audio and video tags in
HTML5 are the starting points for making audio-video content as
integrated into the Web as images have been. The Popcorn.js project
illustrates for instance how video content can benefit from
hyperlinking (much in the same way
<a href="http://people.w3.org/~dom/archives/2009/02/the-beauty-of-htmlmediaelement/">
I had been exploring 2 years ago with my presentation viewer</a>).
Because these technologies are, can be deployed everywhere easily,
I expect this will increasingly revolutionize our consumption of
media.</p><p>I believe we're now starting to see a new trend of that sort,
with the emergence of what I would call
<em>hyperdevices</em>.</p><p>As more and more devices (
<a href="http://www.w3.org/Mobile/">mobile</a> obviously, but also
tablets,
<a href="http://www.w3.org/standards/webofdevices/tv">TV</a>, cars,
lightbulbs and many more) get connected, they more often that not
get shipped with Web capabilities.</p><p>As the Web gains more and more access to the specific
capabilities of these devices (
<a href="http://dvcs.w3.org/hg/webevents/raw-file/v1/touchevents.html">
touch interactions</a> ,
<a href="http://www.w3.org/QA/www.w3.org/TR/geolocation-API/">
geolocation</a> ,
<a href="http://www.w3.org/QA/dev.w3.org/geo/api/spec-source-orientation.html">
accelerometer</a> , and
<a href="http://www.w3.org/2011/08/mobile-web-app-state.html">many
more</a> ), not only does it become a platform of choice to develop
applications targeted at these devices (as we&#x2019;re exploring in the
<a href="http://mobiwebapp.eu/">MobiWebApp project</a>), but it
also creates new form of interactions across these devices that
were not possible previously.</p><p>To illustrate that point, I've built a couple of very simple
demos:</p><ul class="show_items">
<li>the
<a href="http://strong-frost-1713.heroku.com">remote
whiteboard</a> lets you use a touch-screen device to draw on another
device screen, via the browser; in other words, it gives
touch-capabilities to devices that don't have touch screens (e.g.
most desktops or TV sets) &#x2014; see the
<a href="http://www.w3.org/2011/11/remote-whiteboard-demo">video of
the demo in action</a></li>
<li>the
<a href="http://strong-summer-2638.herokuapp.com/">3D
explorer</a> lets you use a device with an accelerometer to rotate a
3D-graphic (in this case, the
<a href="http://www.w3.org/html/logo/">HTML5 logo</a> ) on a
separate screen (see
<a href="http://www.w3.org/2011/11/3d-demo.html">a video of the
demo in action</a>); it thus gives the equivalent of a 3D-mouse to
any Web-enabled devices; whilst there probably are some 3D mouses
out there, it's by far not as ubiquitous as mobile devices that
come with an accelerometer</li>
</ul><div class="lMargin"><p>No Video Support. Transcript of the video:</p><p>In this demonstration, I'm using the browser on my mobile phone
with accelerometer support to manipulate a 3D object viewed in the
browser on my desktop computer. As I turn the phone, the rendering
of the 3D object turns in synchronization.</p><p>This demo was built by Dominique Hazael-Massieux, only with W3C
Web technologies. Find out more at
<a href="http://github.com/dontcallmedom/node-3dexplorer/">
github.com/dontcallmedom</a>.</p><p>
<strong>Note:</strong>If your browser does not support HTML5, you
may still be able to view the video directly:
<a href="http://media.w3.org/2011/11/3D-demo-web.mp4">mp4
version</a> ,
<a href="http://media.w3.org/2011/11/3D-demo-web.webm">webm
version</a>.</p></div><p>We're still at the very early days on this wave, but there is a
growing interest around it. Device and service discovery (see
<a href="http://lists.w3.org/Archives/Public/public-webintents/">
recent discussions on Web Intents</a> ) will play a role there
without a doubt, and the work done as part of the
<a href="http://webinos.org">webinos project</a>(where I'm
involved) will hopefully also inform the technical challenges that
are still to be overcome. We will also need plenty of creativity to
invent user interactions that match these new capabilities.</p><p>But for sure, this is where we are going.</p><p>
<em>Follow me on Twitter:
<a href="http://twitter.com/dontcallmedom">
@dontcallemdom</a></em>.</p></div>
</div>
<div class="hentry closed expand_block">
<div class="headline">
<h3 class="tPadding0 bPadding0 entry-title">
<span class="expand_section">
<a class="uri url" href="http://mobiwebapp.eu/2011/11/21/beyond-the-device-frontier/">
Beyond the device frontier</a>
</span>
</h3>
<p class="date">
<abbr class="published" title="2011-11-21">21
November 2011</abbr>
</p>
<p class="author vcard">from
<a class="fn org url" href="http://www.w3.org/Mobile/">Mobile Web @
W3C - W3C</a></p>
</div>
<div class="expand_description entry-content"><p>I&#x2019;ve just published on the
<a href="http://www.w3.org/QA/2011/11/from_hypertext_to_hyperdevices.html">
W3C blog</a>an illustration on another aspect in which mobile Web
applications create new opportunities: given how ubiquitous the Web
is becoming, it is now offering ways for devices to complete one
another, making what I call &#x201C;hyperdevices&#x201D; (by analogy to
hypertext).</p><p>I&#x2019;ve built two demonstrations that illustrate this, and that you
can either run by yourself, or simply watch as a video:</p><ul class="show_items">
<li>the
<a href="http://strong-frost-1713.heroku.com/">remote
whiteboard</a> exploits touch-capabilities from a mobile device to
draw on a computer (
<a href="http://www.w3.org/2011/11/remote-whiteboard-demo">
video</a>);</li>
<li>the
<a href="http://strong-summer-2638.herokuapp.com/">3D
explorer</a> uses a mobile device with an accelerometer as a way to
manipulate a 3D object on another screen (
<a href="http://www.w3.org/2011/11/3d-demo.html">video</a>).</li>
</ul><p>The work happening in the
<a href="http://www.w3.org/2009/dap/">Device APIs Working
Group</a>&#x2014; in particular around device discovery &#x2014; will be a
critical component in making this type of interactions a natural
extension of what we think of using the Web.</p><p>
<br />
<a href="http://feeds.wordpress.com/1.0/gocomments/mobiwebappw3c.wordpress.com/664/">

<img alt="" src="http://feeds.wordpress.com/1.0/comments/mobiwebappw3c.wordpress.com/664/" />
</a>
<a href="http://feeds.wordpress.com/1.0/godelicious/mobiwebappw3c.wordpress.com/664/">

<img alt="" src="http://feeds.wordpress.com/1.0/delicious/mobiwebappw3c.wordpress.com/664/" />
</a>
<a href="http://feeds.wordpress.com/1.0/gofacebook/mobiwebappw3c.wordpress.com/664/">

<img alt="" src="http://feeds.wordpress.com/1.0/facebook/mobiwebappw3c.wordpress.com/664/" />
</a>
<a href="http://feeds.wordpress.com/1.0/gotwitter/mobiwebappw3c.wordpress.com/664/">

<img alt="" src="http://feeds.wordpress.com/1.0/twitter/mobiwebappw3c.wordpress.com/664/" />
</a>
<a href="http://feeds.wordpress.com/1.0/gostumble/mobiwebappw3c.wordpress.com/664/">

<img alt="" src="http://feeds.wordpress.com/1.0/stumble/mobiwebappw3c.wordpress.com/664/" />
</a>
<a href="http://feeds.wordpress.com/1.0/godigg/mobiwebappw3c.wordpress.com/664/">

<img alt="" src="http://feeds.wordpress.com/1.0/digg/mobiwebappw3c.wordpress.com/664/" />
</a>
<a href="http://feeds.wordpress.com/1.0/goreddit/mobiwebappw3c.wordpress.com/664/">

<img alt="" src="http://feeds.wordpress.com/1.0/reddit/mobiwebappw3c.wordpress.com/664/" />
</a>
<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=mobiwebapp.eu&amp;blog=14776567&amp;post=664&amp;subd=mobiwebappw3c&amp;ref=&amp;feed=1" width="1" height="1" />
</p></div>
</div>
<div class="hentry closed expand_block">
<div class="headline">
<h3 class="tPadding0 bPadding0 entry-title">
<span class="expand_section">
<a class="uri url" href="http://www.w3.org/QA/2011/11/web_walls_digital_signage_and.html">
Web walls, digital signage and personalized content</a>
</span>
</h3>
<p class="date">
<abbr class="published" title="2011-11-10">10
November 2011</abbr>
</p>
<p class="author vcard">from
<a class="fn org url" href="http://www.w3.org/Mobile/">Mobile Web @
W3C - W3C</a></p>
</div>
<div class="expand_description entry-content"><p>There is increasing interest in multiscreen applications, and
this is featured in the latest
<a href="http://webinos.org/">webinos</a> video on
<a href="http://www.youtube.com/watch?feature=player_embedded&amp;v=2w7H2ciPbLI">
multiplayer games</a> . In the office, we are used to having to plug
our personal computers into the room's projector, but perhaps these
days are numbered. It should be easy to have web applications that
run across multiple devices so that you can run your presentation
from your smart phone or tablet and view it on the wall screen,
with no need for video cables at all. One aspect of this is how
your mobile device discovers the wall screen. This is now in active
development in the W3C
<a href="http://www.w3.org/2009/dap/">Device APIs Working
Group</a>.</p><p>Large displays in public spaces are often used for
<a href="http://en.wikipedia.org/wiki/Digital_signage">Digital
Signage</a> , and this was the subject of a
<a href="http://www.w3.org/wiki/TPAC2011/Web-based_Digital_Signage">
break out session</a> in
<a href="http://www.w3.org/wiki/TPAC2011">TPAC2011</a> . One
challenge is how to provide personalized content for public
displays. This was brought into focus by the film
<a href="http://www.youtube.com/watch?v=oBaiKsYUdvg">Minority
Report</a> , and has made it into reality with
<a href="http://blog.moviefone.com/2007/01/31/minority-reports-intelligent-ads-are-now-science-fact/">
road side billboards that recognize car number plates</a> . The long
range infrared laser iris scanning technology in Minority Report is
a little scary, but another possibility is to use face recognition
together with
<a href="http://en.wikipedia.org/wiki/Picocell">pico cells</a>.
This identifies the set of people nearby based upon the mobile
phones they are carrying, and by limiting the number of people
increases the chances of successful face recognition. Bluetooth and
WiFi MAC addresses offer further alternatives. Social networks and
photo sharing sites already have our photos and profiles, so this
would be a direct extension to their advertising based business
model.</p><p>A final piece in the jigsaw is enabling the displays to target
multiple passersby with personalized content. The emergence of 3D
displays is pointing the way to a future where the content you see
is based upon your position relative to the display, and determined
by the face recognition software acting on the camera feeds for the
display. By this point, you are probably getting increasingly
concerned over privacy. Luckily, W3C is on the job with the
<a href="http://www.w3.org/2011/tracking-protection/">Tracking
Protection Working Group</a>allowing you to opt out of personalized
ads, whether on a conventional web page or a public display in the
airport.</p></div>
</div>
<div class="hentry closed expand_block">
<div class="headline">
<h3 class="tPadding0 bPadding0 entry-title">
<span class="expand_section">
<a class="uri url" href="http://mobiwebapp.eu/2011/10/28/workshop-papers-on-offline-web-applications/">
Workshop Papers on Offline Web Applications</a>
</span>
</h3>
<p class="date">
<abbr class="published" title="2011-10-28">28
October 2011</abbr>
</p>
<p class="author vcard">from
<a class="fn org url" href="http://www.w3.org/Mobile/">Mobile Web @
W3C - W3C</a></p>
</div>
<div class="expand_description entry-content"><p>As
<a href="http://mobiwebapp.eu/2011/09/12/workshop-on-future-of-offline-web-applications/">
announced a few weeks ago</a> , next week a
<a href="http://www.w3.org/2011/web-apps-ws/">W3C workshop
dedicated to offline Web applications</a>will take place in Santa
Clara, California.</p><p>I submitted two position papers based on the input and feedback
I&#x2019;ve gathered through the MobiWebApp project: one on
<a href="http://www.w3.org/2011/web-apps-ws/papers/Hazael-Massieux-2.html">
HTTP optimizations for HTML5&#x2019;s ApplicationCache</a> , and the other
on making
<a href="http://www.w3.org/2011/web-apps-ws/papers/Hazael-Massieux-1.html">
Web applications first class citizens</a>.</p><p>These are only two of the
<a href="http://www.w3.org/2011/web-apps-ws/Papers">28 papers that
were submitted to the workshop</a>, and which are bound to make a
basis for a great discussion next Saturday.</p><p>
<br />
<a href="http://feeds.wordpress.com/1.0/gocomments/mobiwebappw3c.wordpress.com/638/">

<img alt="" src="http://feeds.wordpress.com/1.0/comments/mobiwebappw3c.wordpress.com/638/" />
</a>
<a href="http://feeds.wordpress.com/1.0/godelicious/mobiwebappw3c.wordpress.com/638/">

<img alt="" src="http://feeds.wordpress.com/1.0/delicious/mobiwebappw3c.wordpress.com/638/" />
</a>
<a href="http://feeds.wordpress.com/1.0/gofacebook/mobiwebappw3c.wordpress.com/638/">

<img alt="" src="http://feeds.wordpress.com/1.0/facebook/mobiwebappw3c.wordpress.com/638/" />
</a>
<a href="http://feeds.wordpress.com/1.0/gotwitter/mobiwebappw3c.wordpress.com/638/">

<img alt="" src="http://feeds.wordpress.com/1.0/twitter/mobiwebappw3c.wordpress.com/638/" />
</a>
<a href="http://feeds.wordpress.com/1.0/gostumble/mobiwebappw3c.wordpress.com/638/">

<img alt="" src="http://feeds.wordpress.com/1.0/stumble/mobiwebappw3c.wordpress.com/638/" />
</a>
<a href="http://feeds.wordpress.com/1.0/godigg/mobiwebappw3c.wordpress.com/638/">

<img alt="" src="http://feeds.wordpress.com/1.0/digg/mobiwebappw3c.wordpress.com/638/" />
</a>
<a href="http://feeds.wordpress.com/1.0/goreddit/mobiwebappw3c.wordpress.com/638/">

<img alt="" src="http://feeds.wordpress.com/1.0/reddit/mobiwebappw3c.wordpress.com/638/" />
</a>
<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=mobiwebapp.eu&amp;blog=14776567&amp;post=638&amp;subd=mobiwebappw3c&amp;ref=&amp;feed=1" width="1" height="1" />
</p></div>
</div>
<div class="hentry closed expand_block">
<div class="headline">
<h3 class="tPadding0 bPadding0 entry-title">
<span class="expand_section">
<a class="uri url" href="http://mobiwebapp.eu/2011/10/18/mobile-web-applications-interoperability-event/">
Mobile Web Applications Interoperability Event</a>
</span>
</h3>
<p class="date">
<abbr class="published" title="2011-10-18">18
October 2011</abbr>
</p>
<p class="author vcard">from
<a class="fn org url" href="http://www.w3.org/Mobile/">Mobile Web @
W3C - W3C</a></p>
</div>
<div class="expand_description entry-content"><p>Are you concerned about mobile fragmentation? Do you need to
test a Web application on a mobile device? If so, we would like to
invite you to the
<a href="http://www.w3.org/2011/10/interop/">Mobile Web
Applications Interoperability event</a>on 6-7 December 2011, in
Sophia-Antipolis, France.</p><p>This event, co-organized by
<a href="http://www.w3.org/">W3C</a> through
<a href="http://mobiwebapp.eu/">MobiWebApp</a> and
<a href="http://www.mosquito-fp7.eu/consortium">MOSQUITO project
partners</a> , and hosted by
<a href="http://www.etsi.org/">ETSI</a>, will be the occasion:</p><ul class="show_items">
<li>to practice and
<strong>develop test cases</strong>for the
<a href="http://w3c-test.org/framework/">W3C testing framework</a>.
Web specifications under consideration are those directly relevant
for the development of mobile Web applications (candidates include
the audio/video elements in HTML5, HTML5 Application Cache, the
Contacts API, Device Orientation Event specification, Web Storage,
Web Workers).</li>
<li>to
<strong>test Web applications on a wide variety of
devices</strong>through various network configurations</li>
</ul><p>Participation is free and open to everyone. Please
<a href="http://webapp.etsi.org/plugtests/Register.asp?EventID=168">
register on ETSI&#x2019;s Web site</a>&#xA0;by mid-November.</p><p>Check the
<a href="http://www.w3.org/2011/10/interop/">Call for
Participation</a>for details.</p><p>
<br />
<a href="http://feeds.wordpress.com/1.0/gocomments/mobiwebappw3c.wordpress.com/632/">

<img alt="" src="http://feeds.wordpress.com/1.0/comments/mobiwebappw3c.wordpress.com/632/" />
</a>
<a href="http://feeds.wordpress.com/1.0/godelicious/mobiwebappw3c.wordpress.com/632/">

<img alt="" src="http://feeds.wordpress.com/1.0/delicious/mobiwebappw3c.wordpress.com/632/" />
</a>
<a href="http://feeds.wordpress.com/1.0/gofacebook/mobiwebappw3c.wordpress.com/632/">

<img alt="" src="http://feeds.wordpress.com/1.0/facebook/mobiwebappw3c.wordpress.com/632/" />
</a>
<a href="http://feeds.wordpress.com/1.0/gotwitter/mobiwebappw3c.wordpress.com/632/">

<img alt="" src="http://feeds.wordpress.com/1.0/twitter/mobiwebappw3c.wordpress.com/632/" />
</a>
<a href="http://feeds.wordpress.com/1.0/gostumble/mobiwebappw3c.wordpress.com/632/">

<img alt="" src="http://feeds.wordpress.com/1.0/stumble/mobiwebappw3c.wordpress.com/632/" />
</a>
<a href="http://feeds.wordpress.com/1.0/godigg/mobiwebappw3c.wordpress.com/632/">

<img alt="" src="http://feeds.wordpress.com/1.0/digg/mobiwebappw3c.wordpress.com/632/" />
</a>
<a href="http://feeds.wordpress.com/1.0/goreddit/mobiwebappw3c.wordpress.com/632/">

<img alt="" src="http://feeds.wordpress.com/1.0/reddit/mobiwebappw3c.wordpress.com/632/" />
</a>
<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=mobiwebapp.eu&amp;blog=14776567&amp;post=632&amp;subd=mobiwebappw3c&amp;ref=&amp;feed=1" width="1" height="1" />
</p></div>
</div>
<div class="hentry closed expand_block">
<div class="headline">
<h3 class="tPadding0 bPadding0 entry-title">
<span class="expand_section">
<a class="uri url" href="http://www.w3.org/blog/International/2011/09/30/slides-and-irc-logs-for-limerick-multilingualweb-workshop-now-available/">
Slides and IRC logs for Limerick MultilingualWeb workshop now
available</a>
</span>
</h3>
<p class="date">
<abbr class="published" title="2011-09-30">30
September 2011</abbr>
</p>
<p class="author vcard">from
<a class="fn org url" href="http://www.w3.org/blog/International">
Internationalization Activity Blog &#xBB; w3cWebOfDevices</a></p>
</div>
<div class="expand_description entry-content"><div class="lMargin"><p>
<img src="http://www.w3.org/International/multilingualweb/images/mlw-logo.png" alt=" " />
</p></div><p>The MultilingualWeb Workshop in
<a href="http://www.multilingualweb.eu/documents/limerick-workshop">
Limerick</a>was once more a success, thanks to the efforts of the
excellent speakers and the local organizers, but also thanks this
time to the participants themselves who enthusiastically took part
in the Open Space discussion organized by TAUS. This will hopefully
lead to some longer term initiatives, and most groups are already
planning to continue their discussions in Luxembourg, next Spring.
We had around 90 attendees.</p><p>The
<a href="http://www.multilingualweb.eu/documents/limerick-workshop/limerick-program">
program page</a>has now been updated to point to speakers&#x2019; slides
and to the relevant parts of the IRC logs. Links to video
recordings will follow shortly.</p><p>There will also be a page pointing to social media reports, such
as blog posts, tweets and photos, related to the workshop. If you
have any blog posts, photos, etc. online, please let Richard Ishida
know (ishida@w3.org) so that we can link to them from this
page.</p><p>A summary report of the workshop will follow a little later.</p></div>
</div>
</div>
</div>
<!-- End news -->
<div class="line">
<div class="w3c_events_talks">
<div class="line">
<div class="unit size1on2">
<div id="upcomingtalks" class="w3c_upcoming_talks"><h2 class="category"><a title="More Talks&#x2026;" href="/2007/11/Talks/Web_of_Devices.html">
	      Talks and Appearances
	      <img src="/2008/site/images/header-link" alt="Header link" width="13" height="13" class="header-link" /></a></h2><ul class="vevent_list"><li class="vevent"><p class="date single"><span class="dtstart"><span class="year">2012</span><span class="mm-dd">-03-13</span></span> <span class="paren">(</span><span class="dd-mmm">13 MAR</span><span class="paren">)</span></p><div class="info-wrap"><p class="summary">Options for Multimodal Applications -- platforms, standards, and tools</p><p class="source"> by Deborah Dahl</p><p class="eventtitle"><a href="http://mobilevoiceconference.com/" class="uri">Mobile Voice 2012</a></p><p class="location">San Francisco,
	  USA</p></div></li></ul><p>See also the <a href="/Talks/">full list of W3C Talks and Appearances</a>.</p></div>
</div>
<div class="unit size1on2 lastUnit">
<div id="upcomingevents" class="w3c_upcoming_events">
  <h2 class="category">
      <a title="More Events&#x2026;" href="/participate/eventscal.html">
      Events
      <img src="/2008/site/images/header-link" alt="Header link" width="13" height="13" class="header-link" />
    </a>
  </h2>
<ul class="vevent_list">
    <li class="vevent">
      <div class="date">
<span class="dtstart"><span class="year">2012</span><span class="mm-dd">-01-30</span></span>
<span class="paren">(</span><span class="dd-mmm">30 JAN</span><span class="paren">)</span>
<span class="date-separator"> &#x2013; </span>
<span class="dtend"><span class="year">2012</span><span class="mm-dd">-03-26</span></span>
<span class="paren">(</span><span class="dd-mmm">26 MAR</span><span class="paren">)</span>
</div>      <div class="info-wrap">
       <p class="summary">      <a href="http://www.w3devcampus.com/mobile-web-and-application-best-practices-training/" class="uri">W3C Introduction to Mobile Web and Application Best  Practices</a>
</p>
           <p class="location">Online</p>                   <div class="description">
     <p>The Introduction to W3C Mobile Web and Application Best Practices online course will help Web designers and content producers who are already familiar with the desktop world to become familiar with the Web as delivered on mobile devices. It is based entirely on W3C standards, particularly the Mobile Web Best Practices and Mobile Web Application Best Practices.</p>
  </div>
      </div>
    </li>
    <li class="vevent">
      <div class="date">
<span class="dtstart"><span class="year">2012</span><span class="mm-dd">-01-31</span></span>
<span class="paren">(</span><span class="dd-mmm">31 JAN</span><span class="paren">)</span>
<span class="date-separator"> &#x2013; </span>
<span class="dtend"><span class="year">2012</span><span class="mm-dd">-02-01</span></span>
<span class="paren">(</span><span class="dd-mmm"> 1 FEB</span><span class="paren">)</span>
</div>      <div class="info-wrap">
       <p class="summary">      <a href="http://www.w3.org/2011/04/webrtc/#meeting" class="uri">RTCWEB &amp; Web RTC Working Group meeting</a>
</p>
           <p class="location">San Jose, CA, USA</p>                       </div>
    </li>
    <li class="vevent">
      <div class="date">
<span class="dtstart"><span class="year">2012</span><span class="mm-dd">-02-27</span></span>
<span class="paren">(</span><span class="dd-mmm">27 FEB</span><span class="paren">)</span>
<span class="date-separator"> &#x2013; </span>
<span class="dtend"><span class="year">2012</span><span class="mm-dd">-03-01</span></span>
<span class="paren">(</span><span class="dd-mmm"> 1 MAR</span><span class="paren">)</span>
</div>      <div class="info-wrap">
       <p class="summary">      <a href="http://www.mobileworldcongress.com/" class="uri">Mobile World Congress 2012</a>
</p>
           <p class="location">Barcelona, Spain</p>                   <div class="description">
     <p>W3C will have a booth at Mobile World Congress: come and meet us in Hall 2, booth #2A31!</p>
  </div>
      </div>
    </li>
</ul>
 <p>See <a href="/participate/eventscal.html">full list of W3C Events</a>.</p>


</div>
</div>
</div>
</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/sup">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>
<!-- #footer address / page signature -->
<p class="copyright">Copyright &#xA9; 2012 W3C <sup>&#xAE;</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} --><div id="w3c_scripts"><script type="text/javascript" src="/2008/site/js/main" xml:space="preserve"><![CDATA[
//
<!-- -->
//
]]></script></div></body></html>