You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
961 lines
51 KiB
961 lines
51 KiB
<!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 Design and Applications - 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 class="current">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 href="/standards/webofdevices/">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> <span class="cr">»</span> </li>
|
|
<li><a href="/standards/">Standards</a> <span class="cr">»</span> </li>
|
|
<li class="current">Web Design and Applications</li>
|
|
</ul>
|
|
</div>
|
|
</div>
|
|
<h1 class="title">
|
|
<img src="/2008/site/images/theme-web-design" alt="" />Web Design and Applications</h1>
|
|
<ul class="w3c_toc"><li class="toc_prefix">On this page → </li><li>
|
|
<a href="#w3c_overview">technology topics</a>
|
|
<span class="bullet">•</span>
|
|
</li><li>
|
|
<a href="#recent">news</a>
|
|
<span class="bullet">•</span>
|
|
</li><li>
|
|
<a href="#upcomingevents">upcoming events and talks</a>
|
|
</li></ul>
|
|
<div id="w3c_content_body">
|
|
<div class="line">
|
|
<div class="intro">
|
|
<p>Web Design and Applications involve the standards for building and Rendering Web pages, including HTML, CSS, SVG, Ajax, and other technologies for Web Applications (“WebApps”). This section also includes information on how to make pages accessible to people with disabilities (WCAG), to internationalize them, and make them work on mobile devices.</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/htmlcss">HTML & CSS <img src="/2008/site/images/header-link" alt="Header link" width="13" height="13" class="header-link" />
|
|
</a>
|
|
</h2>
|
|
<p class="tPadding0">
|
|
HTML and CSS are the fundamental technologies for building
|
|
Web pages: HTML (html and xhtml) for structure, CSS for
|
|
style and layout, including WebFonts. Find resources for good Web page design
|
|
as well as helpful tools.
|
|
</p>
|
|
</div>
|
|
<div class="unit size1on3">
|
|
<h2 class="w3c_topic">
|
|
<a href="/standards/webdesign/script">Scripting and Ajax <img src="/2008/site/images/header-link" alt="Header link" width="13" height="13" class="header-link" />
|
|
</a>
|
|
</h2>
|
|
<p class="tPadding0">
|
|
Standard APIs for client-side Web Application
|
|
development include those for Geolocation, XMLHttpRequest (Ajax), and
|
|
mobile widgets. W3C standards for document models (the
|
|
“DOM”) and technologies such as XBL
|
|
allow content providers to create interactive
|
|
documents through scripting.
|
|
</p>
|
|
</div>
|
|
<div class="unit size1on3 lastUnit">
|
|
<h2 class="w3c_topic">
|
|
<a href="/standards/webdesign/graphics">Graphics <img src="/2008/site/images/header-link" alt="Header link" width="13" height="13" class="header-link" />
|
|
</a>
|
|
</h2>
|
|
<p class="tPadding0">
|
|
W3C is the home of the widely deployed PNG raster format,
|
|
SVG vector format, and the Canvas API. WebCGM is a more specialized
|
|
format used, for example, in the fields of automotive engineering,
|
|
aeronautics.
|
|
</p>
|
|
</div>
|
|
</div>
|
|
<div class="line">
|
|
<div class="unit size1on3">
|
|
<h2 class="w3c_topic">
|
|
<a href="/standards/webdesign/audiovideo">Audio and Video <img src="/2008/site/images/header-link" alt="Header link" width="13" height="13" class="header-link" />
|
|
</a>
|
|
</h2>
|
|
<p class="tPadding0">
|
|
Some of the W3C formats that enable authoring audio and video
|
|
presentations include HTML, SVG, and SMIL (for synchronization).
|
|
W3C is also working on a timed text format for captioning and
|
|
other applications.
|
|
</p>
|
|
</div>
|
|
<div class="unit size1on3">
|
|
<h2 class="w3c_topic">
|
|
<a href="/standards/webdesign/accessibility">Accessibility <img src="/2008/site/images/header-link" alt="Header link" width="13" height="13" class="header-link" />
|
|
</a>
|
|
</h2>
|
|
<p class="tPadding0">
|
|
W3C’s Web Accessibility Initiative (WAI) has published
|
|
Web Content Accessibility Guidelines (WCAG) to
|
|
help authors create content that is
|
|
accessible to people with disabilities. WAI-ARIA gives authors
|
|
more tools to create accessible Web Applications by providing
|
|
additional semantics about widgets and behaviors.
|
|
</p>
|
|
</div>
|
|
<div class="unit size1on3 lastUnit">
|
|
<h2 class="w3c_topic">
|
|
<a href="/standards/webdesign/i18n">Internationalization <img src="/2008/site/images/header-link" alt="Header link" width="13" height="13" class="header-link" />
|
|
</a>
|
|
</h2>
|
|
<p class="tPadding0">
|
|
W3C has a mission to design technology that works across
|
|
cultures and languages. W3C standards such as HTML
|
|
and XML are built on Unicode, for instance. In addition,
|
|
W3C has published guidance for authors related to language tags
|
|
bi-directional (bidi) text, and more.
|
|
</p>
|
|
</div>
|
|
</div>
|
|
<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 “One Web” that is available on any device.
|
|
W3C’s Mobile Web Best Practices help authors understand
|
|
how to create content that provides a reasonable
|
|
experience on a wide variety of devices, contexts, and
|
|
locations.
|
|
</p>
|
|
</div>
|
|
<div class="unit size1on3">
|
|
<h2 class="w3c_topic">
|
|
<a href="/standards/webdesign/privacy">Privacy <img src="/2008/site/images/header-link" alt="Header link" width="13" height="13" class="header-link" />
|
|
</a>
|
|
</h2>
|
|
<p class="tPadding0">
|
|
The Web is a powerful tool for communications and transactions
|
|
of all sorts. It is important to consider privacy and
|
|
security implications of the Web as part of technology design. Learn more about tracking and Web App security.
|
|
</p>
|
|
</div>
|
|
<div class="unit size1on3 lastUnit">
|
|
<h2 class="w3c_topic">
|
|
<a href="/standards/webdesign/math">Math on the Web <img src="/2008/site/images/header-link" alt="Header link" width="13" height="13" class="header-link" />
|
|
</a>
|
|
</h2>
|
|
<p class="tPadding0">
|
|
Mathematics and formula are used on the Web for business
|
|
reports, education materials and scientific research. W3C’s MathML
|
|
enables mathematics to be served, received, and processed on the World Wide Web, just as HTML has enabled this functionality for other types of
|
|
content.
|
|
</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/webdesign/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
|
|
“Mobile Web and Application Best Practices” (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  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’ 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&blog=14776567&post=727&subd=mobiwebappw3c&ref=&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/12/w3c_tag_publishes_finding_on_i.html">
|
|
W3C TAG Publishes Finding on Identifying Application State</a>
|
|
</span>
|
|
</h3>
|
|
<p class="date">
|
|
<abbr class="published" title="2011-12-24">24
|
|
December 2011</abbr>
|
|
</p>
|
|
<p class="author vcard">from
|
|
<a class="fn org url" href="http://www.w3.org/html/">W3C HTML
|
|
Working Group</a></p>
|
|
</div>
|
|
<div class="expand_description entry-content"><p>The W3C TAG is pleased to announce the publication of a new TAG
|
|
Finding "
|
|
<a href="http://www.w3.org/2001/tag/doc/IdentifyingApplicationState">
|
|
Identifying Application State</a>."</p><p>URIs were originally used primarily to identify documents on the
|
|
Web, or with the use of fragment identifiers, portions of those
|
|
documents. As Web content has evolved to include Javascript and
|
|
similar applications that have extensive client-side logic, a need
|
|
has arisen to use URIs to identify states of such applications, to
|
|
provide for bookmarking and linking those states, etc. This finding
|
|
sets out some of the challenges of using URIs to identify
|
|
application states, and recommends some best practices. A more
|
|
formal introduction to the Finding and its scope can be found in
|
|
its
|
|
<a href="http://www.w3.org/2001/tag/doc/IdentifyingApplicationState#abstract">
|
|
abstract</a>.</p><p>The W3C TAG would like to thank Ashok Malhotra, who did much of
|
|
the analysis and editing for this work, and also former TAG member
|
|
T.V. Raman, who first brought this issue to the TAG's attention,
|
|
and who wrote earlier drafts on which this finding is based.</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, “
|
|
<strong>Introduction to Mobile Web and Application Best
|
|
Practices</strong>“:</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€ (until 9 Jan. 2012)</li>
|
|
<li>Full price: 225€</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’ 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&blog=14776567&post=712&subd=mobiwebappw3c&ref=&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/13/new-translations-into-russian-and-ukrainian-2/">
|
|
New translations into Russian and Ukrainian</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/blog/International">
|
|
Internationalization Activity Blog » w3cWebDesign</a></p>
|
|
</div>
|
|
<div class="expand_description entry-content"><p>Ukrainian:
|
|
<br />
|
|
<a href="http://www.w3.org/International/tutorials/svg-tiny-bidi/Overview.uk.php">
|
|
Створення Невеличких SVG Сторінок в Арабській мові, Івриті та інших
|
|
скриптах, які вирівнюються справа наліво</a>(Creating SVG Tiny
|
|
Pages in Arabic, Hebrew and other Right-to-Left Scripts)</p><p>Russian:
|
|
<br />
|
|
<a href="http://www.w3.org/International/tutorials/svg-tiny-bidi/Overview.ru.php">
|
|
Создание небольших SVG Страниц на Арабском языке, Иврите и других
|
|
скриптах, которые выравниваются справа налево</a>(Creating SVG Tiny
|
|
Pages in Arabic, Hebrew and other Right-to-Left Scripts)</p><p>These articles were translated thanks to Alexandr Shlapak.</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/12/open_web_platform_weekly_summa.html">
|
|
Open Web Platform Weekly Summary - 2011-12-05 - 2011-12-11</a>
|
|
</span>
|
|
</h3>
|
|
<p class="date">
|
|
<abbr class="published" title="2011-12-12">12
|
|
December 2011</abbr>
|
|
</p>
|
|
<p class="author vcard">from
|
|
<a class="fn org url" href="http://www.w3.org/html/">W3C HTML
|
|
Working Group</a></p>
|
|
</div>
|
|
<div class="expand_description entry-content"><p>The
|
|
<a href="http://www.w3.org/wiki/Open_Web_Platform">Open Web
|
|
Platform</a>
|
|
<a href="http://www.w3.org/QA/archive/open_web/">weekly</a> summary
|
|
is about love for the open Web, about the work we do
|
|
<strong>together</strong>, about the hours we spent every day to
|
|
create a better Web. I can work in this domain, because others gave
|
|
an open environment for working. Let’s keep it open.</p><h3>HTML5</h3><p>The specification has been
|
|
<a href="http://html5.org/r/6845">modified</a> to allow two syntaxes
|
|
for the
|
|
<code>time</code>element. You may write time with a T or a
|
|
<a href="http://wiki.whatwg.org/wiki/Time_element#permit_space_instead_of_T_in_datetimes">
|
|
single space separator</a>between the date and the time.</p><pre>
|
|
<code><time>2011-12-24T23:59</time>
|
|
<time>2011-12-24 23:59</time>
|
|
</code>
|
|
</pre><p>XML documents have a
|
|
<code>UTF-8</code>default encoding. Kornel Lesiński
|
|
<a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15076">
|
|
asked</a>if it would be possible to do that for documents with an
|
|
HTML5 doctype. Henri Sivonen (Mozilla), who is also developing the
|
|
HTML5 parser for Firefox, rejected the suggestion. It would
|
|
introduce more incompatibilities and more specific behaviors than
|
|
the already existing explicit mechanisms.</p><h3>HTML Rich Content</h3><p>Sometimes Web developers need to extend their content with a
|
|
richer semantics by adding simple data structure to their markup. A
|
|
|
|
<a href="http://www.w3.org/TR/rdfa-lite/">first Working Draft for
|
|
RDFa Lite 1.1</a>has been published. For example to specify that
|
|
this column is written by a human and not a cow.</p><pre>
|
|
<code><p vocab="http://schema.org/"
|
|
resource="#karl"
|
|
typeof="Person">
|
|
This blog post is written by
|
|
<span property="name">Karl Dubost</span>.</p>
|
|
</code>
|
|
</pre><p>The purpose of this group is to develop a common specification
|
|
in OWL for structured and unstructured annotations on Web
|
|
documents, based on prior work developed by the Annotation Ontology
|
|
(http://code.google.com/p/annotation-ontology/) and Open Annotation
|
|
Collaboration (http://www.openannotation.org/) efforts.</p><p>You are invited to support the creation of this group:
|
|
http://www.w3.org/community/groups/proposed#annotation</p><h3>Video Tracks</h3><p>The WebVTT format (Web Video Text Tracks) is a format intended
|
|
for marking up external text track resources.
|
|
<a href="http://dev.w3.org/html5/webvtt/">WebVTT</a> has escaped
|
|
HTML5 to be developed by the
|
|
<a href="http://www.w3.org/community/texttracks/">Web Media Text
|
|
Tracks Community Group</a> . They also have a
|
|
<a href="http://twitter.com/webvtt">twitter account</a> . Anne van
|
|
Kesteren has created a
|
|
<a href="http://quuz.org/webvtt/">WebVTT Validator</a> and published
|
|
the
|
|
<a href="https://bitbucket.org/annevk/webvtt">source code</a>on
|
|
bitbucket. The syntax is a very simple text file.</p><pre>
|
|
<code>WEBVTT
|
|
|
|
00:11.000 --> 00:13.000
|
|
<v Roger Bingham>We are in New York City
|
|
|
|
00:13.000 --> 00:16.000
|
|
<v Roger Bingham>We're actually at the Lucern Hotel, just
|
|
down the street
|
|
</code>
|
|
</pre><h3>Web Apps</h3><p>If humanity had an
|
|
<a href="http://rniwa.com/editing/undomanager.html">
|
|
<code>UndoManager</code>API</a> we might have been able to fix a lot
|
|
of mistakes. Ryosuke Niwa (webkit) is working on such an API for
|
|
the Web and he is asking feedback. A
|
|
<a href="http://wiki.whatwg.org/wiki/UndoManager_Problem_Descriptions">
|
|
long list of use cases</a>has been outlined to better understand
|
|
what do we need to solve.</p><p>Dominique Hazaël-Massieux (W3C) has been giving a summary of the
|
|
|
|
<a href="http://www.w3.org/2011/11/mobile-web-app-state.html">
|
|
Standards for Web Applications on Mobile</a>. He has published an
|
|
update for November 2011.</p><h3>DOM</h3><p>The new methods for
|
|
<code>append</code>,
|
|
<code>prepend</code>, … that we mentioned a few weeks ago have been
|
|
addred to the DOM 4 specification in the
|
|
<a href="http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#mutation-methods">
|
|
mutation methods section</a> . This triggered a new
|
|
<a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=14188">
|
|
syntax requirement for WebIDL</a> , which has not yet been
|
|
completely defined. Anne van Kesteren (Opera) has also started to
|
|
define
|
|
<a href="http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#mutation-observers">
|
|
Mutation observers</a>.</p><h3>CSS</h3><p>An update has been published for
|
|
<a href="http://www.w3.org/TR/2011/WD-css3-images-20111206/">CSS
|
|
Image Values and Replaced Content</a> and a new
|
|
<strong>editor</strong>draft for
|
|
<a href="http://dev.w3.org/csswg/css3-grid-align/">CSS3 Grid
|
|
Layout</a> . As a kind reminder, these are drafts and then
|
|
<strong>not stable</strong>. If the implementations change them or
|
|
drop these features, you will have to eat your own hat :)</p><h3>Web Architecture</h3><p>A tendency in Web development has emerged a little while ago.
|
|
Web developers started to push hash sign in their URIs not to
|
|
define an anchor in the document but the state of an application.
|
|
The W3C Technical Architecture Group has summarized
|
|
<a href="http://www.w3.org/2001/tag/doc/IdentifyingApplicationState-20111130">
|
|
best practices for handling hash signs URIs</a>.</p><p>The W3C TAG is
|
|
<a href="http://www.w3.org/2001/tag/products/">working on a few
|
|
topics</a> in parallel. You could participate constructively to the
|
|
discussions by subscribing to the
|
|
<a href="http://lists.w3.org/Archives/Public/www-tag/">www-tag
|
|
mailing list</a>.</p><h3>HTTP</h3><p>You can now buffer this number, RFC 6455, in your memory lane.
|
|
The
|
|
<a href="http://tools.ietf.org/html/rfc6455">WebSocket
|
|
Protocol</a> is
|
|
<a href="http://www.ietf.org/mail-archive/web/ietf-announce/current/msg09663.html">
|
|
accepted</a>. Though be careful, because there might still be a bit
|
|
of breakage depending if your browser has released a version of the
|
|
implementation but disabled by default. Check your preferences.</p><p>In the discussion about extending HTTP status code, Roy Fielding
|
|
(Adobe) gave an interesting
|
|
<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/2011OctDec/0364">
|
|
rule for knowing how/when to extend the list of codes</a>.</p><blockquote>
|
|
<p>When extending HTTP status codes, the question that needs to be
|
|
asked is “how will a client process this response differently than
|
|
any of the existing status codes?”</p>
|
|
</blockquote><h3>Elsewhere</h3><ul class="show_items">
|
|
<li>
|
|
<a href="http://movethewebforward.org/">Move The Web Forward</a>is
|
|
the new kid in town. It gives a long list of resources to help Web
|
|
developers stay informed about what’s going on the Open Web
|
|
platform.</li>
|
|
<li>
|
|
<a href="http://redbot.org/">Redbot</a> , the HTTP validation tool
|
|
developed by Mark Nottingham, now supports
|
|
<a href="http://blog.redbot.org/https-in-redbot">HTTP over SSL and
|
|
TLS</a></li>
|
|
</ul><p>This column is written by
|
|
<a href="http://www.la-grange.net/karl/">Karl Dubost</a> ,
|
|
<a href="http://my.opera.com/karlcow/blog/">working</a> in the
|
|
<a href="http://dev.opera.com/">Developer Relations team</a> at
|
|
<a href="http://www.opera.com/">Opera Software</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://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 – 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 » w3cWebDesign</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 – 16 March 2012, Luxembourg</strong>. Co-located with
|
|
the European Commission’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&blog=14776567&post=692&subd=mobiwebappw3c&ref=&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/Style/CSS/Overview.en.html">Updated draft
|
|
of CSS Image Values and Replaced Content Modul#x2026;</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/Style/CSS/Overview.en.html">Cascading Style
|
|
Sheets</a></p>
|
|
</div>
|
|
<div class="expand_description entry-content"><p>Updated draft of CSS
|
|
Image Values and Replaced Content Module Level 3</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/12/openweb-weekly-22.html">Open Web
|
|
Platform Weekly Summary - 2011-11-29 - 2011-12-04</a>
|
|
</span>
|
|
</h3>
|
|
<p class="date">
|
|
<abbr class="published" title="2011-12-05">05
|
|
December 2011</abbr>
|
|
</p>
|
|
<p class="author vcard">from
|
|
<a class="fn org url" href="http://www.w3.org/html/">W3C HTML
|
|
Working Group</a></p>
|
|
</div>
|
|
<div class="expand_description entry-content"><p>The
|
|
<a href="http://www.w3.org/wiki/Open_Web_Platform">Open Web
|
|
Platform</a>
|
|
<a href="http://www.w3.org/QA/archive/open_web/">weekly</a>summary
|
|
is about HTML5 oldies, shadows and intents, and protocols.</p><h3>HTML5</h3><p>Yehuda Katz and a few others have started a discussion on
|
|
<a href="http://lists.w3.org/Archives/Public/public-html/2011Nov/thread.html#msg234">
|
|
Restoring PUT and DELETE</a> in HTML5 forms (
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=1067">Issue
|
|
1067</a> ). The Ruby on Rails Web framework is currently using a
|
|
<a href="http://guides.rubyonrails.org/form_helpers.html#how-do-forms-with-put-or-delete-methods-work">
|
|
hack for simulating PUT and DELETE</a>.</p><p>The Web is an amazing big pile of history.
|
|
<code>border</code>attribute on
|
|
<code>table</code>elements didn’t have any units. Though people had
|
|
a tendency to put units such as the wrong
|
|
<code><table border="5px"></code>. So browsers repaired
|
|
automagically to take into account only the beginning of the string
|
|
and ignore any trailing characters. Sylvain Galineau (Microsoft)
|
|
raised an
|
|
<a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15047">
|
|
issue</a> because he thought it would create issues for microdata
|
|
values. Ian Hickson mentioned that the incorrect values were not
|
|
<strong>valid</strong>but fixed by the browser if wrong.</p><p>
|
|
<code>INS</code>and
|
|
<code>DEL</code>elements which are used to track insertion and
|
|
deletion of contents in HTML have a very simple model. So simple
|
|
that according to Daniel Glazman (Disruptive Innovations), it is
|
|
<a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=13057">not
|
|
easily implementable</a>in any useful way for authoring tools.</p><p>A Community Group has been proposed to
|
|
<a href="http://www.w3.org/community/groups/proposed#html5spec">
|
|
discuss ideas around the future of HTML and associated
|
|
features</a>.</p><h3>Web Apps</h3><p>Webkit has a
|
|
<a href="https://bugs.webkit.org/show_bug.cgi?id=73528">proposed
|
|
patch</a> for the
|
|
<a href="http://www.w3.org/TR/netinfo-api/">Network Information
|
|
API</a> . This is an interesting API because it allows to create
|
|
apps which behave differently depending if the network is 3g, wifi,
|
|
etc. For example, imagine a
|
|
<strong>responsive Web design</strong>where images of adequate
|
|
sizes are sent depending on the type of network which gives a good
|
|
idea of what could be the bandwidth.</p><p>Rich Tibbet (Opera) has proposed a
|
|
<a href="http://richtr.tumblr.com/post/12929135260/a-better-model-for-web-intents">
|
|
model for the Web intents</a>work.</p><p>Simon Pieters (Opera) wanted an
|
|
<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=15007">API
|
|
to queue a task</a>. After discussing about the opportunity of such
|
|
a need, Glenn Maynard proposed a piece of code that finally Simon
|
|
extended.</p><pre>
|
|
<code>var queueTask = function(task) {
|
|
var mc = new MessageChannel();
|
|
var args = [].slice.call(arguments, 1);
|
|
mc.port1.onmessage = function(){
|
|
this.onmessage = null; task.apply(task, args);
|
|
};
|
|
mc.port2.postMessage(null);
|
|
};
|
|
queueTask(function(arg) { console.log(arg, this) }, "test");
|
|
</code>
|
|
</pre><p>Dimitri Glazkov (Chromium team) has proposed a high level
|
|
<a href="http://dvcs.w3.org/hg/webcomponents/raw-file/tip/explainer/index.html">
|
|
overview of Web Components for Web Developers</a>.</p><h3>DOM</h3><p>The
|
|
<code>setAttributeNS()</code>is
|
|
<a href="http://www.w3.org/mid/op.v5pue1ha64w2qv@annevk-macbookpro.local">
|
|
implemented differently</a> in IE, Firefox, Webkit and Opera. The
|
|
discussion, which started on the mutability of attributes, led to
|
|
discuss about simplifying the platform for HTML documents by
|
|
removing the namespacing of attributes. According to Jonas Sicking
|
|
(Mozilla), that would also improve browser performances. There
|
|
would still be needed for
|
|
<code>XMLDocument</code>interface.</p><h3>HTTP</h3><p>When exchanging data in between client and server, there are a
|
|
few techniques. One of them is XMLHttpRequest which helps inject a
|
|
data flow into the page without reloading the full context. People
|
|
often uses it to transfer JSON packaged data. Anne van Kestern
|
|
(Opera) has added
|
|
<code>json</code>response type to
|
|
<a href="http://dvcs.w3.org/hg/xhr/raw-file/tip/Overview.html#the-responsetype-attribute">
|
|
XMLHttpRequest</a>.</p><p>When a client and server interact on the Web, the server answer
|
|
to client requests with 3 number codes. These have very specific
|
|
meanings. For example,
|
|
<code>200</code>means that the server has successfully answered the
|
|
client request. It is happening quite often that Web developers
|
|
(specifically those developing Web APIs) lack some
|
|
<a href="http://en.wikipedia.org/wiki/List_of_HTTP_status_codes">
|
|
HTTP status code</a> to have a richer interactions between the
|
|
client and the server. Mark Nottingham has been working for a while
|
|
on
|
|
<a href="http://tools.ietf.org/html/nottingham-http-new-status">new
|
|
HTTP status code</a>.</p><p>HTTP/1.1 allows many types of characters. This has a tendency to
|
|
create security issues when, for example in
|
|
<a href="http://tools.ietf.org/html/rfc3875">CGI/1.1</a> ,
|
|
translating these characters into UNIX environment variables. Some
|
|
of them are not valid and/or parseable characters. Yutaka Oiwa
|
|
<a href="http://www.w3.org/mid/4EDC3AC0.70803@aist.go.jp">
|
|
brought</a>the subject on HTTPbis mailing list.</p><h3>Elsewhere</h3><ul class="show_items">
|
|
<li>
|
|
<a href="http://codemirror.net/">CodeMirror</a>is a JavaScript
|
|
library that can be used to create a relatively pleasant editor
|
|
interface for code-like content ― computer programs, HTML markup,
|
|
and similar.</li>
|
|
<li>
|
|
<a href="http://24ways.org/2011/unicode-range">Creating Custom Font
|
|
Stacks with Unicode-Range</a>
|
|
</li>
|
|
<li>
|
|
<a href="http://blogs.msdn.com/b/ie/archive/2011/11/29/html5-for-applications-the-fourth-ie10-platform-preview.aspx">
|
|
IE10 Preview 4th</a>has support for CORS.</li>
|
|
<li>Firefox seems likely after Chrome to support
|
|
<a href="https://wiki.mozilla.org/Platform/Features/SPDY">
|
|
SPDY</a></li>
|
|
</ul><p>This week, the theme of
|
|
<a href="http://annevankesteren.nl/">Anne Van Kesteren</a> ’s
|
|
<a href="http://blog.whatwg.org/weekly-encoding-woes">
|
|
report</a>about Encoding woes and WebVTT.</p><p>This column is written by
|
|
<a href="http://www.la-grange.net/karl/">Karl Dubost</a> ,
|
|
<a href="http://my.opera.com/karlcow/blog/">working</a> in the
|
|
<a href="http://dev.opera.com/">Developer Relations team</a> at
|
|
<a href="http://www.opera.com/">Opera Software</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://www.w3.org/blog/International/2011/12/01/new-working-draft-of-requirements-for-japanese-text-layout/">
|
|
New Working Draft of Requirements for Japanese Text Layout</a>
|
|
</span>
|
|
</h3>
|
|
<p class="date">
|
|
<abbr class="published" title="2011-12-01">01
|
|
December 2011</abbr>
|
|
</p>
|
|
<p class="author vcard">from
|
|
<a class="fn org url" href="http://www.w3.org/blog/International">
|
|
Internationalization Activity Blog » w3cWebDesign</a></p>
|
|
</div>
|
|
<div class="expand_description entry-content"><p>A
|
|
<a href="http://www.w3.org/TR/2011/WD-jlreq-20111129/">new version
|
|
of Requirements for Japanese Text Layout</a>has just been published
|
|
as a Working Draft.</p><p>The plan is to replace the
|
|
<a href="http://www.w3.org/TR/2009/NOTE-jlreq-20090604/">current
|
|
W3C Working Group Note</a>with the content of this new Working
|
|
Draft after a period of review.</p><p>This document describes requirements for general Japanese layout
|
|
realized with technologies such as CSS, SVG and XSL-FO. It is also
|
|
being used by developers of other technologies, such as ebooks. The
|
|
document builds on and further develops the Japanese standard for
|
|
text layout, JIS X 4051.</p><p>This second version of the document contains a significant
|
|
amount of additional information related to hanmen design, such as
|
|
handling headings, placement of illustrations and tables, handling
|
|
of notes and reference marks, etc.</p><p>Please take a look at the new version, which is available in
|
|
English and Japanese, and send any comments to
|
|
<a href="mailto:public-i18n-cjk@w3.org?subject=[JLReq]">
|
|
public-i18n-cjk@w3.org</a> (
|
|
<a href="http://lists.w3.org/Archives/Public/public-i18n-cjk/">
|
|
subscribe at the archive main page</a>). Use “[JLReq]” in the
|
|
subject line of your email, followed by a brief subject.</p><p>Send any comments before the end of December. We hope to publish
|
|
the final version of the updated Working Group Note early in the
|
|
New Year.</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…" href="/2007/11/Talks/Web_Design_and_Applications.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><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><li class="vevent"><p class="date single"><span class="dtstart"><span class="year">2012</span><span class="mm-dd">-03-15</span></span> <span class="paren">(</span><span class="dd-mmm">15 MAR</span><span class="paren">)</span></p><div class="info-wrap"><p class="summary"><a href="http://www.w3.org/2012/Talks/0315-Luxembourg-IH/#talk">What is Happening in the W3C Semantic Web Activity?</a></p><p class="source"> keynote by Ivan Herman</p><p class="eventtitle"><a href="http://www.multilingualweb.eu/en/documents/luxembourg-workshop" class="uri">The Multilingual Web - the Way Ahead</a></p><p class="location">Luxembourg,
|
|
Luxembourg</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…" 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"> – </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"> – </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 & 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"> – </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/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>
|
|
<!-- #footer address / page signature -->
|
|
<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} --><div id="w3c_scripts"><script type="text/javascript" src="/2008/site/js/main" xml:space="preserve"><![CDATA[
|
|
//
|
|
<!-- -->
|
|
//
|
|
]]></script></div></body></html>
|