openweb-weekly-06.html 18.5 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='html, html5, open web, w3c, webapps' />
    <meta name="description" content="Shelley Powers, like me, published a late weekly. We are totally in synchronization in covering the Open Web Platform weekly news from HTML5 and broader topics. That said it was again quite active not only on the HTML WG mailing list but also on the Web apps WG mailing list. W3C is opening more ways to contribute and the CSS 2.1 is officially reaching Proposed Recommendation. Read and tell me if anything is missing." />
    <meta name="revision" content="$Id: openweb-weekly-06.html,v 1.20 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-04-04 - 2011-04-10 - W3C Blog</title>

   <link rel="start" href="http://www.w3.org/QA/" title="Home" />
   <link rel="prev" href="http://www.w3.org/QA/2011/04/government_data_done_well_and.html" title="Government Data Done Well and the Digital Agenda for Europe" />
   <link rel="next" href="http://www.w3.org/QA/2011/04/discovery_and_the_web_of_thing.html" title="Discovery and the Web of Things" />

   <!--
<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-06.html"
    trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/387"
    dc:title="Open Web Platform Weekly Summary - 2011-04-04 - 2011-04-10"
    dc:identifier="http://www.w3.org/QA/2011/04/openweb-weekly-06.html"
    dc:subject="Open Web"
    dc:description="Shelley Powers, like me, published a late weekly. We are totally in synchronization in covering the Open Web Platform weekly news from HTML5 and broader topics. That said it was again quite active not only on the HTML WG mailing list but also on the Web apps WG mailing list. W3C is opening more ways to contribute and the CSS 2.1 is officially reaching Proposed Recommendation. Read and tell me if anything is missing."
    dc:creator="Karl Dubost"
    dc:date="2011-04-10T20:49:49+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/04/government_data_done_well_and.html">&laquo; Government Data Done Well and the Digital Agenda for Europe</a> |
                        <a href="http://www.w3.org/QA/">Main</a>
                        | <a href="http://www.w3.org/QA/2011/04/discovery_and_the_web_of_thing.html">Discovery and the Web of Things &raquo;</a>
                     </p>

                        <h2 class="entry-header">Open Web Platform Weekly Summary - 2011-04-04 - 2011-04-10</h2>
                           <div class="entry-body">
                              <p><a href="http://burningbird.net/">Shelley Powers</a>, like me, published a late <a href="http://blog.whatwg.org/whatwg-weekly-2">weekly</a>. We are totally in synchronization in covering 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> news from <a href="http://w3.org/html5/">HTML5</a> and broader topics. I&#8217;m still a bit in the experiment mood and wondering if it is really useful to people who have no time to follow everything happening in the area.</p>

<p>As you may be aware, the HTML standard is co-developed by the WHATWG and the W3C. As part of this, the W3C is always looking for use cases that have not yet been properly addressed by the Web platform. Since Sam recently <a href="http://lists.w3.org/Archives/Public/public-html/2011Apr/0127">posted an e-mail</a> indicating that the W3C was interested in <a href="http://www.w3.org/html/wg/wiki/HTML.next">new features for HTML</a>, this may be a good time to remind everyone that you are also welcome to participate in the <a href="http://lists.w3.org/Archives/Public/">W3C mailing lists</a>, where we discuss adding new features to the <a href="http://www.w3.org/wiki/Open_Web_Platform">Open Web Platform</a>. For example, at the moment we are currently discussing HTML markup, diverse APIs for the Web, and how to standardize better privacy and <a href="http://www.w3.org/2011/identity-ws/">identity</a> mechanisms (amongst other things). </p>

<p>For more information, see also the blog post on <a href="http://www.w3.org/QA/2011/04/coming_soon_w3c_community_grou">W3C community engagement</a>, a new initiative. You may want to join the <a href="http://w3.org/html/wg">HTML WG</a>. There is no deadline for participating; the W3C has published the Web
standards continuously.</p>

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

<h4 id="rel_attribute_values_ownership_issue_27"><code>rel</code> attribute values ownership - ISSUE-27</h4>

<p>The <code>rel</code> attribute values give additional information on the purpose of a piece of text or a link, such as defining if the stylesheet is for a screen or print, or if a link represents a link to a license. Historically some of them were declared into HTML4.01 specification. These values are likely to appear and disappear quicker than the evolution of the language. It has been decided to put them in a separate registry. The <a href="http://www.w3.org/html/wg/tracker/issues/27">question</a> was then who should own the registry for these values. The HTML Working Group <a href="http://www.w3.org/mid/4D9F17A6.5070100@intertwingly.net">decided</a> to defer to the Microformats community for <a href="http://www.w3.org/html/wg/wiki/User%3AEoconnor/ISSUE-27">cataloging HTML rel values</a>. Read the decision carefully, it is long and detailed.</p>

<h4 id="playback_rate_and_video_element_issue_147">playback rate and video element - ISSUE-147</h4>

<p>When playing a video, what is happening when a unsupported playback rate is requested. Should there be a way for scripts to detect this? Or it might not be possible or matters. What are the best way of exposing this information through an API? The HTML Working Group <a href="http://www.w3.org/mid/4D9F50B6.2000807@intertwingly.net">decided</a> to adopt the <a href="http://lists.w3.org/Archives/Public/public-html/2011Mar/0682">change proposal</a> stating that it is a hardware limitation and then should not be exposed via a dedicated API.</p>

<h4 id="conforming_u_element_issue_144">conforming <code>u</code> element - ISSUE-144</h4>

<p>The <code>u</code> element is a controversial element for a long time on the Web. It has always existed since the first versions of HTML. It creates a line under a string of characters. Usabilitiy experts have long debated that it was likely to be mistaken with links. It is one of these very <a href="http://www.w3.org/html/wg/tracker/issues/144">long standing issues</a>. Should the <code>u</code> element be conforming or not? Conformance here means when writing or validating markup. The parsing support is another matter. It is a distinction that people often forget. The Working Group has finally <a href="http://www.w3.org/mid/4D9F5041.1060807@intertwingly.net">decided</a> the <a href="http://www.w3.org/html/wg/wiki/ChangeProposals/UShouldBeConforming"><code>u</code> element to be conforming</a>.</p>

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

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

<ul>
<li>Andreas Petersson (Opera) sent his first draft for standardizing <a href="http://www.w3.org/mid/20110407113217.5662559a@hetzer">Forwarded-For HTTP header</a>. X-Forwarded-For is used by proxies to inform a server that the originated IP is different. It is important for personnalization of services based on IP geolocation for example.</li>
<li>Steve Faulkner <a href="http://www.w3.org/mid/BANLkTi=P_o43S7EaLtuR-oDC3FBTWa6YPw@mail.gmail.com">proposed</a> the <code>subheading</code> value for the <code>role</code> attribute to replace the need of the <code>hgroup</code> element which led to a <a href="http://lists.w3.org/Archives/Public/public-html/2011Apr/thread.html#msg147">lively discussion</a>.</li>
</ul>

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

<ul>
<li>W3C Proposal for <a href="http://www.w3.org/QA/2011/04/coming_soon_w3c_community_grou">community engagement</a></li>
<li><a href="http://www.w3.org/2011/04/07-html-wg-minutes">April 7 HTML WG minutes</a></li>
<li>is <a href="http://www.w3.org/mid/4D9AFC88.2060200@nokia.com">Websockets API</a> ready for Last Call?</li>
<li><a href="http://www.w3.org/mid/4D99F307.3040109@nokia.com">Call for publishing</a> Working Drafts of <a href="http://dev.w3.org/2009/dap/file-system/file-writer.html">File API: Writer</a> and <a href="http://dev.w3.org/2009/dap/file-system/file-dir-sys.html">File API: Directories and System</a></li>
<li>CSS 2.1 is officially a Proposed Recommendation.</li>
</ul>

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

<ul>
<li>The HTML WG <a href="http://www.w3.org/mid/4D91F3C7.4010109@intertwingly.net">decision</a> about RDFa prefixes is highly debated on www-archive mailing-list. There is disagreement on the decision. James Graham (Opera) <a href="http://www.w3.org/mid/4D9D9AD9.3060905@opera.com">strongly disagrees</a> with the decision. He is giving more information about the issue. Kurt Cagle (Avalon Consulting, Library of Congress) <a href="http://www.w3.org/mid/BANLkTikB9kHQAVQ-HhSoz8W5D7kz7n9v+g@mail.gmail.com">followed up</a> on the thread by <a href="http://www.w3.org/mid/BANLkTino1-76PKcPv=qSid2zL8s30zTmGQ@mail.gmail.com">trying</a> to find a middle ground, James Graham seems to be happy about it. David Carlisle (Numerical Algorithms Group Ltd) <a href="http://www.w3.org/mid/4D9F3B20.1060005@nag.co.uk">continued</a> the discussion. Danny Ayers <a href="http://www.w3.org/mid/BANLkTim5UQsRdnOR+SoZzkjGzpQvpjw7Xg@mail.gmail.com">gave</a> a <a href="http://rdfa.info/wiki/Consume">list of libraries</a> implementing RDFa. In the meantime, Sam Ruby (IBM, HTML WG chair) is <a href="http://www.w3.org/mid/4DA310BF.4030801@intertwingly.net">struggling</a> to keep the original discussion on topic. </li>
<li>The discussion about <a href="http://lists.w3.org/Archives/Public/public-html/2011Apr/thread.html#msg28">PUT and DELETE HTTP methods in 200 code</a> is still very active. This discussions overlaps at least two specifications HTML5 and HTTP in the process of being fixed. </li>
<li>As predicted the <a href="http://lists.w3.org/Archives/Public/public-html/2011Apr/thread.html#msg21">discussion on Specification licenses</a> is going on. Gervase Markham (Mozilla) <a href="http://lists.w3.org/Archives/Public/public-html/2011Apr/thread.html#msg263">proposed</a> to adopt the CreativeCommons CC0 license.</li>
<li>Another lively discussion of the week is about <a href="http://lists.w3.org/Archives/Public/public-html/2011Apr/thread.html#msg118">Systematic access to media/plugin metadata</a> started by Danny Ayers.</li>
<li>Glenn Maynard is asking about <a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-April/thread.html#31192">Canvas.getContext error handling</a></li>
<li>Mark Notthingham started a discussion about <a href="http://www.w3.org/mid/90400372-C89F-4E9C-92F6-D8F1A6AAD631@mnot.net">SHOULD-level requirements in p6-caching</a> HTTP working draft</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 10, 2011  8:49 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-06.html">Permalink</a>
                                 | <a href="http://www.w3.org/QA/2011/04/openweb-weekly-06.html#comments">Comments (2)</a>
                                 | <a href="http://www.w3.org/QA/2011/04/openweb-weekly-06.html#trackback">TrackBacks (0)</a>
</p>


<h3 class="comments-header" id="comments">Comments</h3>
<div class="comment" id="comment-223218">
<p class="comment-meta" id="c223218">
<span class="comment-meta-author"><strong>Olivier </strong></span>
<span class="comment-meta-date"><a href="#c223218">#</a> 2011-04-14</span>
</p>
<div class="comment-bulk">
<p>Count me in the (mostly silent) number of those who appreciate your summary, Karl.</p>

</div>
</div>


<div class="comment" id="comment-223358">
<p class="comment-meta" id="c223358">
<span class="comment-meta-author"><strong>Ian Jacobs <a class="commenter-profile" href="http://www.w3.org/People/Jacobs/"><img alt="Author Profile Page" src="http://www.w3.org/QA/sununga/mt-static/images/comment/mt_logo.png" width="16" height="16" /></a></strong></span>
<span class="comment-meta-date"><a href="#c223358">#</a> 2011-04-18</span>
</p>
<div class="comment-bulk">
<p>Let's not be silent! Karl++ :)</p>

<p>Ian</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="9065" />
<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>