openweb-weekly-13.html 16.2 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, html, html5, http, openweb, w3c, webapps' />
    <meta name="description" content="The weekly summary of the Open Web Platform is out. There was a few giant threads, be prepared to mutate any opinions about these events. Read also Anne van Kesteren's report. HTML5 is still in Last Call. Conversations Proposals Maciej..." />
    <meta name="revision" content="$Id: openweb-weekly-13.html,v 1.24 2011/12/16 03:00:20 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-06-29 - 2011-07-05 - W3C Blog</title>

   <link rel="start" href="http://www.w3.org/QA/" title="Home" />
   <link rel="prev" href="http://www.w3.org/QA/2011/07/interview_adobe_on_html5_and_a.html" title="Interview: Adobe on HTML5 and Authoring with the Open Web Platform" />
   <link rel="next" href="http://www.w3.org/QA/2011/07/openweb-weekly-14.html" title="Open Web Platform Weekly Summary - 2011-07-06 - 2011-07-12" />

   <!--
<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/07/openweb-weekly-13.html"
    trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/412"
    dc:title="Open Web Platform Weekly Summary - 2011-06-29 - 2011-07-05"
    dc:identifier="http://www.w3.org/QA/2011/07/openweb-weekly-13.html"
    dc:subject="Open Web"
    dc:description="The weekly summary of the Open Web Platform is out. There was a few giant threads, be prepared to mutate any opinions about these events. Read also Anne van Kesteren&apos;s report. HTML5 is still in Last Call. Conversations Proposals Maciej..."
    dc:creator="Karl Dubost"
    dc:date="2011-07-06T20:16:42+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/07/interview_adobe_on_html5_and_a.html">&laquo; Interview: Adobe on HTML5 and Authoring with the Open Web Platform</a> |
                        <a href="http://www.w3.org/QA/">Main</a>
                        | <a href="http://www.w3.org/QA/2011/07/openweb-weekly-14.html">Open Web Platform Weekly Summary - 2011-07-06 - 2011-07-12 &raquo;</a>
                     </p>

                        <h2 class="entry-header">Open Web Platform Weekly Summary - 2011-06-29 - 2011-07-05</h2>
                           <div class="entry-body">
                              <p>The <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> is out. There was a few giant threads, be prepared to mutate any opinions about these events. Read also <a href="http://annevankesteren.nl/">Anne van Kesteren</a>'s <a href="http://blog.whatwg.org/weekly-component-mutation">report</a>.</p>

<p><a href="http://w3.org/html5/">HTML5</a> is still in Last Call. </p>

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

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

<ul>
<li><p>Maciej Stachowiak (Apple) <a href="http://www.w3.org/mid/5BBC3EAB-DA46-4011-8B20-15369C7AF7E2@apple.com">unsatisfied</a> with the discussion on <a href="http://glazkov.com/2011/01/14/what-the-heck-is-shadow-dom/">Shadow DOM</a> API has started a new thread about <a href="http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/thread.html#msg1364">Component Models and Encapsulation</a></p></li>
<li><p>Anne van Kesteren (Opera) proposed to publish <a href="http://dvcs.w3.org/hg/from-origin/raw-file/tip/Overview.html">From-Origin</a> as a first public WD but there were a few comments from <a href="http://www.w3.org/mid/213E0EC97FE58F469BB618245B3118BB550C1B28A9@DEN-MEXMS-001.corp.ebay.com">Brad Hill</a> (eBay) about security, and from <a href="http://www.w3.org/mid/l937175f1u869oq3mbhi8m4ev5kii0tjks@hive.bjoern.hoehrmann.de">Björn Höhrmann</a></p></li>
<li><p>Aaron Colwell (Google) is proposing to <a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/thread.html#32277">extend HTML5 video for adaptive streaming</a>.</p></li>
<li><p>Anne van Kesteren (Opera) has proposed to <a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/032255.html">reconcile document.URL and document.documentURI</a></p></li>
</ul>

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

<ul>
<li><p><a href="http://www.w3.org/mid/4E0C53FF.7010305@nokia.com">Call</a> to publish <a href="http://dev.w3.org/2006/webapi/WebIDL/">WebIDL</a> as a Last Call Working Draft.</p></li>
<li><p><a href="http://www.w3.org/mid/4E0CA5B5.604@nokia.com">Call</a> to publish <a href="http://dev.w3.org/2006/waf/widgets/">Widget Packaging and XML Configuration</a> as a Proposed Recommendation. You can read the <a href="http://dev.w3.org/2006/waf/widgets/imp-report/">implementation report</a> for 4 products.</p></li>
</ul>

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

<ul>
<li><p>The <a href="http://lists.w3.org/Archives/Public/public-html/2011Jul/thread.html#msg3">discussion</a> on immediate (Canvas) and retained (SVG) mode graphics is still going on. Kimberly Blessing (Comcast) <a href="http://www.w3.org/mid/D3216380E43BA14AA8322B3B9966CF11059EB8CA@PACDCEXMB01.cable.comcast.com">reminds</a> us that there is a big interest for Canvas from set-top boxes implementers. Some interesting questions about accessibility led Doug Schepers to write <a href="http://schepers.cc/retain-a11y-immediately">Retain Accessibility Immediately</a>. A more focused discussion on solving concrete cases would help. Right now, it is often a meta discussion about accessibility and graphics mode. This ties to discussions such as the <a href="http://blog.mozilla.com/cjones/2011/06/15/overview-of-pdf-js-guts/">Javascript PDF viewer</a> currently in development at Mozilla. Matt May (Adobe) gave a <a href="http://www.w3.org/mid/96000FCB2ADA2F4F84F49CC99202F19925EE26F9B6@NAMBX01.corp.adobe.com">list of Javascript projects using canvas</a> creating accessibility issues. </p></li>
<li><p><a href="http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/thread.html#msg0">Mutation events replacement</a> is the other big discussion of the week. First of all, lets&#8217;s go back to the <a href="http://www.w3.org/TR/DOM-Level-2-Events/events.html">DOM Level 2 Event Model</a> specification published in 2000. The specification <a href="http://www.w3.org/TR/DOM-Level-2-Events/events.html#Events-eventgroupings-mutationevents">says</a>: <q cite="http://www.w3.org/TR/DOM-Level-2-Events/events.html#Events-eventgroupings-mutationevents">Mutation Events The mutation event module is designed to allow notification of any changes to the structure of a document, including attr and text modifications.</q> Olli Pettay (Mozilla) <a href="http://www.w3.org/mid/4E09BB41.2040308@helsinki.fi">mentioned</a> that there was a <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=641821">patch for Gecko</a> implementing a variant of a <a href="http://lists.w3.org/Archives/Public/public-webapps/2009AprJun/0745">proposal by Jonas Sicking in 2009</a>. Sergey Ilinsky (Ample SDK implementer) in June 2009 <a href="http://lists.w3.org/Archives/Public/public-webapps/2009AprJun/0747">asked</a> for <a href="http://lists.w3.org/Archives/Public/public-webapps/2009AprJun/thread.html#msg747">Mutation events use cases</a>. There is <a href="http://lists.w3.org/Archives/Public/www-dom/2009AprJun/thread.html#msg95">another giant thread</a> about Mutation Events on the DOM mailing list that took place in June 2009 and we can find <a href="http://www.w3.org/2008/webapps/track/actions/320">traces</a> in March 2009.</p></li>
<li><p>Some servers are unable to deal with empty filename parameter in XHR, Anne Van Kesteren (Opera) added a <a href="http://dev.w3.org/2006/webapi/XMLHttpRequest-2/#dom-formdata-append">blob for File objects</a> in this case.</p></li>
<li><p>James Kozianski (Google) <a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-April/031309.html">proposed</a> in the past to add to the <cite><a href="http://www.whatwg.org/specs/web-apps/current-work/#custom-handlers">registerProtocolHandler specification</a></cite> the two functions: <code>isRegistered()</code> and <code>unregisterProtocolHandler()</code>. Ojab Vafai (Google) is <a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-July/thread.html#32290">wondering</a> if the proposal makes sense. Timeless <a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-July/032299.html">disagrees</a> with the benefit of this feature for users. Some people proposed to use the <a href="http://dev.w3.org/2009/dap/perms/FeaturePermissions.html">notifications model</a> but there is a balance to maintain in terms of features when it comes to <a href="http://weblogs.mozillazine.org/roc/archives/2011/06/permissions_for.html">user agreement interacting with Web applications</a>.</p></li>
<li><p><a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/thread.html#31883">Discussion on AppCache</a>. The discussion seems to mix understanding about what is HTTP and AppCache with a bit of user interactions. </p></li>
<li><p>Should we have a specific HTTP Status code for <a href="http://lists.w3.org/Archives/Public/ietf-http-wg/2011AprJun/thread.html#msg531">HTTP headers which are too big</a>? It raised the question of what is happening in the wild? What the <a href="http://lists.w3.org/Archives/Public/ietf-http-wg/2011AprJun/0531.html">servers</a> and clients do with <a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/299">big HTTP headers</a>?</p></li>
<li><p>Mark Nottingham <a href="http://lists.w3.org/Archives/Public/ietf-http-wg/2011JulSep/thread.html#msg37">proposed</a> to clarify the 1xx response semantics in HTTP.</p></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 July  6, 2011  8:16 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/07/openweb-weekly-13.html">Permalink</a>
                                 | <a href="http://www.w3.org/QA/2011/07/openweb-weekly-13.html#comments">Comments (0)</a>
                                 | <a href="http://www.w3.org/QA/2011/07/openweb-weekly-13.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="9142" />
<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:20 $</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>