openweb-weekly-11.html 17.9 KB

Raw Blame History Permalink

<?xml version="1.0"?>
<!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">
  <head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <style type="text/css" media="all">
    @import "/QA/2006/01/blogstyle.css";
    </style>
    <meta name="keywords" content='api, DOM, html5, open web, openweb, w3c, webapps' />
    <meta name="description" content="Let's restart the Openweb platform weekly summary. It has been almost one month since the last time. HTML5 is in Last Call and there were a lot of discussions on many mailing lists. " />
    <meta name="revision" content="$Id: openweb-weekly-11.html,v 1.19 2011/12/16 03:00:17 gerald Exp $" />
   <link rel="alternate" type="application/atom+xml" title="Atom" href="http://www.w3.org/QA/atom.xml" />
   <link rel="alternate" type="application/rss+xml" title="RSS 1.0" href="http://www.w3.org/QA/news.rss" />
   <title>Open Web Platform Weekly Summary - 2011-05-17 - 2011-06-20 - W3C Blog</title>

   <link rel="start" href="http://www.w3.org/QA/" title="Home" />
   <link rel="prev" href="http://www.w3.org/QA/2011/06/post.html" title="CSS wiki-based documentation" />
   <link rel="next" href="http://www.w3.org/QA/2011/06/tracking_protection_and_do_not.html" title="Tracking Protection and Do Not Track at W3C" />

   <!--
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
         xmlns:dc="http://purl.org/dc/elements/1.1/">
<rdf:Description
    rdf:about="http://www.w3.org/QA/2011/06/openweb-weekly-11.html"
    trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/405"
    dc:title="Open Web Platform Weekly Summary - 2011-05-17 - 2011-06-20"
    dc:identifier="http://www.w3.org/QA/2011/06/openweb-weekly-11.html"
    dc:subject="Open Web"
    dc:description="Let&apos;s restart the Openweb platform weekly summary. It has been almost one month since the last time. HTML5 is in Last Call and there were a lot of discussions on many mailing lists. "
    dc:creator="Karl Dubost"
    dc:date="2011-06-21T20:08:05+00:00" />
</rdf:RDF>
-->

    <!-- <script type="text/javascript" src="http://www.w3.org/QA/mt.js"></script>-->

</head>
<body class="layout-one-column">
      <div id="banner">
      <h1 id="title">
	<a href="http://www.w3.org/"><img height="48" alt="W3C" id="logo" src="http://www.w3.org/Icons/WWW/w3c_home_nb" /></a>
W3C Blog
</h1>
    </div>

    <ul class="navbar" id="menu">
        <li><strong><a href="/QA/" title="W3C Blog Home">[ W3C Blog ]</a></strong></li>
        <li><a href="/QA/Library/" title="Documents and Publications on Web and Quality">Documents</a></li>
        <li><a href="/QA/Tools/" accesskey="3" title="Validators and other Tools">Tools</a></li>
        <li><a href="/2007/12/qa-blog-help/index#feedback">Feedback</a></li>
    </ul>
<div id="searchbox">
<form method="get" action="http://www.google.com/custom" enctype="application/x-www-form-urlencoded">
<p id="formbox"><input type="text" size="15" class="textfield" name="q" accesskey="E" maxlength="255" /> <input type="submit" class="submitfield" value="Search" id="goButton" name="sa" accesskey="G" /> <input type="hidden" name="cof" value="T:black;LW:72;ALC:#ff3300;L:http://www.w3.org/Icons/w3c_home;LC:#000099;LH:48;BGC:white;AH:left;VLC:#660066;GL:0;AWFID:0b9847e42caf283e;" /><input type="hidden" id="searchW3C" name="sitesearch" checked="checked" value="www.w3.org/QA" /><input type="hidden" name="domains" value="www.w3.org/QA" /></p>
</form>
</div>


    <div id="main"><!-- This DIV encapsulates everything in this page - necessary for the positioning -->

                     <p class="content-nav">
                        <a href="http://www.w3.org/QA/2011/06/post.html">&laquo; CSS wiki-based documentation</a> |
                        <a href="http://www.w3.org/QA/">Main</a>
                        | <a href="http://www.w3.org/QA/2011/06/tracking_protection_and_do_not.html">Tracking Protection and Do Not Track at W3C &raquo;</a>
                     </p>

                        <h2 class="entry-header">Open Web Platform Weekly Summary - 2011-05-17 - 2011-06-20</h2>
                           <div class="entry-body">
                              <p>I dropped the ball since the last <a href="http://www.w3.org/QA/archive/open_web/">weekly</a> summary of the <a href="http://www.w3.org/wiki/Open_Web_Platform">Open Web Platform</a>. A lot of trips, jetlag, preparing talks didn&#8217;t help. <a href="http://annevankesteren.nl/">Anne Van Kesteren</a> is back from his long trip in South America and has <a href="http://blog.whatwg.org/weekly-back">taken over</a> the wonderful job that <a href="http://burningbird.net/">Shelley Powers</a> did for the last few weeks.</p>

<p><a href="http://w3.org/html5/">HTML5</a> is in Last Call. The <a href="http://w3.org/html/wg/">HTML WG</a> may expect a lot of comments.</p>

<h3 id="conversations">Conversations</h3>

<h4 id="proposals">Proposals</h4>

<ul>
<li>Mark Nottingham <a href="http://www.w3.org/mid/04FFD657-4CF3-44EE-A7DA-3BC533ACA001@mnot.net">created</a> a RFC draft for <a href="http://tools.ietf.org/html/draft-nottingham-linked-cache-inv-00.html">Linked Cache Invalidation</a>. It defines Web link types that invalidate HTTP caches, along with an HTTP cache-control extension that allows caches that understand those link types to use responses containing them. Yngve N. Pettersen has a similar document called <a href="http://datatracker.ietf.org/doc/draft-pettersen-cache-context/">Cache Context</a> and Mark pointed to a paper by Bala and Craig Wills on <a href="http://www2.research.att.com/~bala/papers/">Piggyback Cache Invalidation</a> as well sharing working and deployed code for <a href="https://github.com/mnot/squid-lci">Squid</a></li>
<li>There is a <a href="http://lists.w3.org/Archives/Public/ietf-http-wg/2011AprJun/thread.html#msg207">new proposal</a> for HTTP authentication scheme using a MAC algorithm to authenticate requests (via a pre-arranged MAC key): <a href="http://tools.ietf.org/html/draft-hammer-oauth-v2-mac-token">HTTP MAC Authentication Scheme</a></li>
<li>Marcos Caceres <a href="http://www.w3.org/mid/4DDA3B21.4090104@gmail.com">has</a> updated the <a href="http://dev.w3.org/2006/waf/widgets-digsig/test-suite/">test suite</a> for Widgets Digital Signature.</li>
<li>There has been a <a href="http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/thread.html#msg795">proposal</a> for a <a href="https://wiki.mozilla.org/Privacy/Features/DOMCryptAPISpec/Latest">DOMCrypt API</a>. The crypto API in browsers would allow the creation of secure communications. There are cases where it should not be required to rely only on the good will of the servers. </li>
<li>Adam Barth has been working on a <a href="https://docs.google.com/document/edit?id=1r_VTFKApVOaNIkocrg0z-t7lZgzisTuGTXkdzAk4gLU&amp;hl=en&amp;pli=1">URL Interface</a>. There was a strong <a href="http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/thread.html#msg778">interest</a> from the community. </li>
<li><a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-May/thread.html#31768">Proposal for separating script downloads and execution</a></li>
<li>Guha proposed a <a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-May/thread.html#31822">simplification to Microdata</a></li>
</ul>

<h4 id="announcements">Announcements</h4>

<ul>
<li>A new version of the <a href="http://dev.w3.org/html5/decision-policy/decision-policy-v2.htm">Decision policy</a> for the HTML WG is being drafted. This document explains how decisions are made, what are the mechanisms to push further an issue, etc.</li>
<li><a href="http://www.w3.org/mid/E3EACD022300B94D88613639CF4E25F81AB65D2F@TK5EX14MBXC138.redmond.corp.microsoft.com">There</a> is also a <a href="http://www.w3.org/TR/2011/WD-DOM-Level-3-Events-20110531/">Last Call for DOM 3 Events</a>. Implementers have until June 28 for commenting on the implementability of the specification.</li>
<li>There is a <a href="http://www.w3.org/mid/92138C83-7747-47FE-B2D8-ED52189D8066@apple.com">request to give help</a> to Ian Hickson for dealing with the issues brought to the HTML WG. It is the time you could get involved in HTML5 Specification.</li>
<li>A new version of <a href="https://datatracker.ietf.org/doc/draft-vandesompel-memento/">Memento-ID</a> has been published which proposes a mechanism for keeping dated archives of content.</li>
<li><a href="http://www.w3.org/TR/2011/WD-widgets-20110607/">Widget Packaging &amp; XML Configuration</a>, <a href="http://www.w3.org/TR/2011/WD-widgets-apis-20110607/">Widget Interface</a> and <a href="http://www.w3.org/TR/2011/WD-widgets-digsig-20110607/">Widget Digital Signature</a> have been published as Last Call Working Drafts.</li>
<li>A Last Call Working Draft has been published for the <a href="http://www.w3.org/TR/2011/WD-contacts-api-20110616/">Contact API</a>. The comment deadline is July 14. The goal is to have a way to make the addressbook portable between Web applications.</li>
<li><a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/thread.html#31881">Enhancement request: change EventSource to allow cross-domain access</a></li>
</ul>

<h4 id="hottopics">Hot Topics</h4>

<ul>
<li><a href="http://lists.w3.org/Archives/Public/public-html/2011May/thread.html#msg386">Adapative images</a> are an issue for content negotiation based on the device capabilities. Right now there is no easy way to send a different image depending on the screen size. It becomes important in terms of usability and performances.</li>
<li>Getting the right feedback on a specification can be challenging. The tools might create an additional burden for the commenters. <a href="http://www.twitter.com/stevefaulkner">Steve Faulkner</a> is <a href="http://lists.w3.org/Archives/Public/public-html/2011May/thread.html#msg268">proposing</a> to improve Bugzilla which has been used for the HTML WG. Mike Smith is <a href="http://www.w3.org/html/wg/tracker/actions/203">working on a solution</a>.</li>
<li>There is a <a href="http://lists.w3.org/Archives/Public/public-html/2011Jun/thread.html#msg28">long dicussion</a> about where should lie the HTML5 normative requirements for <strong>Web Authors</strong>. Right now the HTML5 Specification contains the requirements for the different class of products (parser, authors, etc.). A view has been created for authors but which is for now informative only. The question is then &#8220;Should there be an easily readable normative specification for Web authors only?&#8221; </li>
<li>Is the <a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-14#section-8.2.4">HTTP code <code>203 Non-Authoritative</code></a> used and <a href="http://lists.w3.org/Archives/Public/ietf-http-wg/2011AprJun/thread.html#msg271">should it be deprecated</a>?</li>
<li>Vincent Scheib (Google) has <a href="http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/thread.html#msg1095">worked</a> on an implementation of mouse lock in Chrome</li>
<li>Israel Hilerio (Microsoft) proposed for IndexedDB: <a href="http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/thread.html#msg898">Using WebIDL Dictionary in IDBObjectStore.createIndex  for optionalParameters</a>, <a href="http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/thread.html#msg1062">Should deleteDatabase return IDBVersionChangeRequest?</a>, <a href="http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/thread.html#msg916">IDBDatabase.setVersion non-nullable parameter has a  default for null</a></li>
<li><q>Gecko, Presto, and Webkit all support on* event attributes on all DOM elements, not just HTMLElement. IE9 seems to only support them on HTMLElement.</q> Boris Zbarsky (Mozilla) <a href="http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/thread.html#msg717">proposed</a> to be supported on all DOM elements but element-specific (e.g. &#8220;click&#8221;).</li>
<li>Some changes are <a href="http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/thread.html#msg805">proposed</a> for the <a href="http://dev.w3.org/html5/postmsg/">Web Messaging specification</a></li>
<li>Aryeh Gregor has <a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-May/thread.html#31765">asked for feedback</a> on  <a href="http://aryeh.name/gitweb.cgi?p=editcommands;a=blob_plain;f=editcommands.html;hb=4a898d7#the-formatblock-command">supported elements for formatBlock</a></li>
<li><a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-May/thread.html#31866">Generalized execCommand() alternatives, or standardized selection and range handling</a></li>
<li><a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/thread.html#31928">WebVTT feedback</a> and <a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/thread.html#31898">Video feedback</a></li>
<li><a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/thread.html#32056">Selectors within <code>&lt;style scoped&gt;</code></a></li>
<li><a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/thread.html#32109">Hashing Passwords Client-side</a></li>
<li><a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/thread.html#32078">getSelection().modify() in vertical writing modes</a></li>
</li><a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/thread.html#32187">Handling of collapsed whitespace in contenteditable</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 &amp; Tools</a> at <a href="http://www.opera.com/">Opera Software</a>.</p>
                           </div>
                           <div id="more" class="entry-more">

                           </div>
                       <p class="postinfo">Filed by <a href="http://my.opera.com/karlcow/blog/">Karl Dubost</a> on June 21, 2011  8:08 PM in <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/open_web/">Open Web</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/w3c_life/">W3C Life</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2011/06/openweb-weekly-11.html">Permalink</a>
                                 | <a href="http://www.w3.org/QA/2011/06/openweb-weekly-11.html#comments">Comments (0)</a>
                                 | <a href="http://www.w3.org/QA/2011/06/openweb-weekly-11.html#trackback">TrackBacks (0)</a>
</p>


  <div class="comments-open" id="comments-open">
<h3 class="comments-open-header">Leave a comment</h3>

<div class="comments-open-moderated">
   <p>
   Note: this blog is intended to foster <strong>polite
   on-topic discussions</strong>. Comments failing these
   requirements and spam will not get published. Please,
   enter your real name and email address. Every
   individual comment is reviewed by the W3C staff.
   This may take some time, thank you for your patience.
   </p>
   <p>
   You can use the following HTML markup (a href, b, i,
   br/, p, strong, em, ul, ol, li, blockquote, pre)
   and/or <a href="http://daringfireball.net/projects/markdown/syntax">Markdown syntax</a>.</p>
</div>

<div id="comments-open-data">
<form method="post" action="http://www.w3.org/QA/sununga/beach.pl" id="comments-form">
<h4>Your comment</h4>
<div id="comments-open-text">
  <textarea id="comment-text" name="text" rows="20" cols="100"></textarea><br />
<label for="comment-text">Write your comment text here. Remember, keep the discussion on topic and courteous.</label>
</div>

<h4>About you</h4>
<div id="comment-form-name">
  <input type="hidden" name="static" value="1" />
<input type="hidden" name="entry_id" value="9130" />
<input type="hidden" name="__lang" value="en" />
<label for="comment-author">Your Name</label>
<input id="comment-author" name="author" size="30" value="" />
</div>
<div id="comment-form-email">
<label for="comment-email">Your Email Address</label>
<input id="comment-email" name="email" size="30" value="" />
</div>

<div id="comments-open-footer">
<input type="submit" accesskey="s" name="post" id="comment-submit" value="Submit" />

</div>
</form>
</div>
</div>


<p id="gentime">This page was last generated on $Date: 2011/12/16 03:00:17 $</p>

      </div><!-- End of "main" DIV. -->

<address>

This blog is written by W3C staff and working group participants,<br />
&nbsp;and maintained by <a href="/People/CMercier/">Coralie Mercier</a>.<br />
Authorized parties may <a href="/QA/new">log in</a> to create a new entry.<br/>
<span id="poweredby">Powered by Movable Type, magpierss and a lot of Web Technology</span>
    </address>


    <p class="copyright">
      <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 1994-2011
      <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a>&reg;
      (<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>),
      All Rights Reserved.
      W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
      <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>,
      <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a>
      and <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/copyright-software">software licensing</a>
      rules apply. Your interactions with this site are in accordance
      with our <a href="http://www.w3.org/Consortium/Legal/privacy-statement#Public">public</a> and
      <a href="http://www.w3.org/Consortium/Legal/privacy-statement#Members">Member</a> privacy
      statements.
    </p>

  </body>
</html>