openweb-weekly-05.html 18.1 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='html5, http, open web, w3c' />
    <meta name="description" content="When we start writing and or read about the activities around the Open Web Platform, we realize that the Web has never been that active. Everyone is proposing, developping, testing. And even if this weekly news from HTML5 and broader topics seemed to be long, it doesn’t cover everything. It is also important to realize that if you are passionate about one of these topics, the full information is accessible and open. Quite exciting. Some of these topics could be the source of long technical blog posts. If you do, please leave a comment or let me know." />
    <meta name="revision" content="$Id: openweb-weekly-05.html,v 1.21 2011/12/16 03:00:14 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-03-28 - 2011-04-03 - W3C Blog</title>

   <link rel="start" href="http://www.w3.org/QA/" title="Home" />
   <link rel="prev" href="http://www.w3.org/QA/2011/03/openweb-weekly-04.html" title="Open Web Platform Weekly Summary - 2011-03-21 - 2011-03-27" />
   <link rel="next" href="http://www.w3.org/QA/2011/04/wiki-based_documentation_proje.html" title="Wiki-based documentation project" />

   <!--
<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/04/openweb-weekly-05.html"
    trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/383"
    dc:title="Open Web Platform Weekly Summary - 2011-03-28 - 2011-04-03"
    dc:identifier="http://www.w3.org/QA/2011/04/openweb-weekly-05.html"
    dc:subject="Open Web"
    dc:description="When we start writing and or read about the activities around the Open Web Platform, we realize that the Web has never been that active. Everyone is proposing, developping, testing. And even if this weekly news from HTML5 and broader topics seemed to be long, it doesn’t cover everything. It is also important to realize that if you are passionate about one of these topics, the full information is accessible and open. Quite exciting. Some of these topics could be the source of long technical blog posts. If you do, please leave a comment or let me know."
    dc:creator="Karl Dubost"
    dc:date="2011-04-03T20:43:56+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/03/openweb-weekly-04.html">&laquo; Open Web Platform Weekly Summary - 2011-03-21 - 2011-03-27</a> |
                        <a href="http://www.w3.org/QA/">Main</a>
                        | <a href="http://www.w3.org/QA/2011/04/wiki-based_documentation_proje.html">Wiki-based documentation project &raquo;</a>
                     </p>

                        <h2 class="entry-header">Open Web Platform Weekly Summary - 2011-03-28 - 2011-04-03</h2>
                           <div class="entry-body">
                              <p>When we start writing and or read about the activities around the <a href="http://www.w3.org/wiki/Open_Web_Platform">Open Web Platform</a>, we realize that the Web has  never been that active. Everyone is proposing, developping, testing. And even if this  <a href="http://www.w3.org/QA/archive/open_web/">weekly</a> news from <a href="http://w3.org/html5/">HTML5</a> and broader topics seemed to be long, it doesn&#8217;t cover everything. It is also important to realize that if you are passionate about one of these topics, the full information is accessible and open. Quite exciting. Some of these topics could be the source of long technical blog posts. If you do, please leave a comment or let me know.</p>

<h3 id="html_working_group_decisions">HTML Working Group Decisions</h3>

<p>Issues about <a href="http://www.w3.org/html/wg/tracker/issues/145">codecs vs octet</a> and <a href="http://www.w3.org/html/wg/tracker/issues/161">accessibility API mapping</a> have been closed by amicable resolutions. A couple of polls have been opened and some already closed</p>

<ul>
<li><a href="http://www.w3.org/html/wg/tracker/issues/155">Table borders</a> <a href="http://www.w3.org/2002/09/wbs/40318/issue-155-objection-poll/">opened</a> until April 4, 2011</li>
<li><a href="http://www.w3.org/html/wg/tracker/issues/144">u element</a> <a href="http://www.w3.org/2002/09/wbs/40318/issue-144-objection-poll/">opened</a> until April 4, 2011</li>
<li><a href="http://www.w3.org/html/wg/tracker/issues/147">playbackrate undefined</a> <a href="http://www.w3.org/2002/09/wbs/40318/issue-147-objection-poll/">opened</a> until April 5, 2011</li>
<li>&#8220;What verbiage should HTML5 use for the first two paragraphs of the img element definition?&#8221; <a href="http://www.w3.org/2002/09/wbs/40318/issue-31-80-verbiage-objection-poll/">opened</a> until April 5, 2011</li>
<li>“Where/who will define the requirements on the possible values of text alternative examples?”  <a href="http://www.w3.org/2002/09/wbs/40318/issue-31-80-requirements-objection-poll/">opened</a> until April 5, 2011</li>
<li>“What to do about validation when the image element is missing the alt attribute?&#8221; <a href="http://www.w3.org/2002/09/wbs/40318/issue-31-80-validation-objection-poll/">opened</a> until April 5, 2011</li>
</ul>

<h4 id="rdfa_prefixes_in_html5_issue_120">RDFa prefixes in HTML5 - ISSUE-120</h4>

<p>RDFa is a language to add additional structure to markup already existing. It is a way to extend the hosting language. It <a href="http://www.w3.org/html/wg/tracker/issues/120">uses optional prefixes</a>. Adoption has not been an issue with 501% growth. It has been then <a href="http://www.w3.org/mid/4D91F3C7.4010109@intertwingly.net">decided</a> to clarify the way RDFa prefixes are used in the HTML5 specification. A <a href="http://www.w3.org/mid/AANLkTin=9OdJfH1Seq63KTtmTeg0AKQs+CE8iSoyQ2_C@mail.gmail.com">formal objection</a> by Tab Atkins has <a href="http://dev.w3.org/html5/status/formal-objection-status.html#ISSUE-120">been recorded</a>. </p>

<h4 id="summary_attribute_on_table_element_issue_32"><code>summary</code> attribute on <code>table</code> element - ISSUE-32</h4>

<p>The <a href="http://www.w3.org/html/wg/tracker/issues/32"><code>summary</code> attribute</a> on <code>table</code> element was a way to give information about the content of the table. It is usually called hidden metadata, because the information is not directly accessible to sighted users such as <code>alt</code> attribute for example. The name &#8220;discoverable metadata&#8221; is proposed for labelling such attributes. The change proposal  which invited to drop the <code>summary</code> attribute has been chosen. This <a href="http://www.w3.org/mid/4D9B24E2.5020006@intertwingly.net">decision</a> has been carefully written. Read it carefully. There are suggestions as usual to reopen the issues with meaningul data and input.</p>

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

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

<ul>
<li><a href="http://www.w3.org/mid/D0BC8E77E79D9846B61A2432D1BA4EAE027CB995@TK5EX14MBXC116.redmond.corp.microsoft.com">Improving sandbox for popups</a> by Jacob Rossi (Microsoft)</li>
<li><a href="http://www.w3.org/mid/D0BC8E77E79D9846B61A2432D1BA4EAE027BB67A@TK5EX14MBXC110.redmond.corp.microsoft.com">text/html-sandboxed should just be a sandboxed MIME type attribute</a> by Jacob Rossi (Microsoft)</li>
</ul>

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

<ul>
<li>New draft for <a href="http://greenbytes.de/tech/webdav/draft-ietf-httpbis-content-disp-latest-from-ietf-lc.diff.html">Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)</a>. HTTPWG bis is working actively on tidying HTTP specification.</li>
<li>Task Force on <a href="http://www.w3.org/2011/webtv/wiki/Main_Page">Home Networking Content and Services Discovery and Control</a>. This is part of the activities around Web and TV.</li>
<li>new Working Draft for <a href="http://dev.w3.org/2006/webapi/clipops/clipops.html">Clipboard API and Events</a> by Hallvord R. M. Steen (Opera).</li>
<li><a href="http://www.ietf.org/internet-drafts/draft-snell-http-prefer-03.txt">Prefer Header for HTTP</a> by
James Snell</li>
<li>Last Call for <a href="http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-06">Web Sockets protocol</a>. All comments should be submitted to hybi@ietf.org by April 15 at the latest.</li>
<li>Draft <a href="http://www.ietf.org/proceedings/80/minutes/httpbis.txt">minutes of HTTP WG in Prague</a></li>
</ul>

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

<ul>
<li>One of the most active topic is <a href="http://www.w3.org/mid/4D961316.6090804@webr3.org">the PUT/DELETE with HTML form</a>. Mike Amundsen has created a <a href="http://amundsen.com/examples/put-delete-forms/">document to explain how it would work with html</a>. The discussion is also <a href="http://www.w3.org/mid/AANLkTi=A7=Y7DW7n5C1wNfn_UvyaC4MG9MDRXVU_oT1Q@mail.gmail.com">happening on HTMLWG</a>. There were similar discussions around <a href="http://bitworking.org/projects/atom/rfc5023.html#edit-via-PUT">Atom and PUT</a> in the past.</li>
<li><a href="http://www.w3.org/mid/AANLkTinpXqAEhVWqRK800Vz-VfYTZEwh9mwWoZcOmMS4@mail.gmail.com">Any future plans, or has IndexedDB replaced WebSQL?</a></li>
<li><a href="http://www.ietf.org/mail-archive/web/ietf/current/msg65974.html">Web applications and architecture</a></li>
<li><a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-March/031000.html">selection.modify behavior across platforms</a></li>
<li>When writing tests in preparation for Opera&#8217;s implementation
of <code>&lt;details&gt;</code> and <code>&lt;summary&gt;</code>, Wilhelm Joys Andersen <a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-March/031067.html">had a few questions</a>.</li>
<li><a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-March/031057.html">Peer-to-peer communication, video conferencing, and related topics (3)</a> by Ian Hickson (Google)</li>
<li><a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-March/031047.html">Implementation difficulties for MediaController</a></li>
<li><a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-March/031053.html">DOM Range: redefining behavior under DOM mutation</a></li>
<li><a href="http://www.w3.org/mid/OF6A58DDBD.13A92692-ON86257861.007D6358-86257862.00641349@us.ibm.com">Canvas change for improved hit testing that also  facilitates accessibility</a> by Rich Schwerdtfeger (IBM)</li>
<li><a href="http://www.w3.org/mid/104E6B5B6535E849970CDFBB1C5216EB3D263C8A@TK5EX14MBXC138.redmond.corp.microsoft.com">Result of calling MultipleReads on FileReader</a> related to <a href="http://dev.w3.org/2006/webapi/FileAPI/#MultipleReads">File API multiread</a></li>
<li>Explanation of the <a href="http://www.w3.org/mid/4D946DDF.3010808@nokia.com">Web Apps WG Testing process</a></li>
<li><a href="http://www.w3.org/mid/4D963AD3.101@lachy.id.au">Selectors API IDL Issues</a> by Lachlan Hunt (Opera)</li>
<li><a href="http://blog.whatwg.org/whatwg-weekly-the-rubber-hits-the-road">WHATWG Weekly: the rubber hits the road</a> by Shelley Powers</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 April  3, 2011  8:43 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/04/openweb-weekly-05.html">Permalink</a>
                                 | <a href="http://www.w3.org/QA/2011/04/openweb-weekly-05.html#comments">Comments (1)</a>
                                 | <a href="http://www.w3.org/QA/2011/04/openweb-weekly-05.html#trackback">TrackBacks (0)</a>
</p>


<h3 class="comments-header" id="comments">Comments</h3>
<div class="comment" id="comment-223450">
<p class="comment-meta" id="c223450">
<span class="comment-meta-author"><strong>Robert Morris </strong></span>
<span class="comment-meta-date"><a href="#c223450">#</a> 2011-04-22</span>
</p>
<div class="comment-bulk">
<p>There is just too much to remember and it was better in the good old days when each new product was accompanied by a limited amount of literature.</p>

</div>
</div>


  <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="9054" />
<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:14 $</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>