openweb-weekly-03.html 20.3 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, open web' />
    <meta name="description" content="This was a big week in terms of decisions. I recommend to read carefully the decision made by the HTML Working Group. They are always very detailed and give a very good overview about the issues. They also propose a way to reopen the issue with meaningful materials.  There have been many proposals and there are two workshops. W3C Workshops are opened to anyone." />
    <meta name="revision" content="$Id: openweb-weekly-03.html,v 1.21 2011/12/16 03:00:11 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-14 - 2011-03-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/03/openweb-weekly-02.html" title="Open Web Platform Weekly Summary - 2011-03-07 - 2011-03-13" />
   <link rel="next" href="http://www.w3.org/QA/2011/03/openweb-weekly-04.html" title="Open Web Platform Weekly Summary - 2011-03-21 - 2011-03-27" />

   <!--
<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/03/openweb-weekly-03.html"
    trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/380"
    dc:title="Open Web Platform Weekly Summary - 2011-03-14 - 2011-03-20"
    dc:identifier="http://www.w3.org/QA/2011/03/openweb-weekly-03.html"
    dc:subject="Open Web"
    dc:description="This was a big week in terms of decisions. I recommend to read carefully the decision made by the HTML Working Group. They are always very detailed and give a very good overview about the issues. They also propose a way to reopen the issue with meaningful materials.  There have been many proposals and there are two workshops. W3C Workshops are opened to anyone."
    dc:creator="Karl Dubost"
    dc:date="2011-03-20T21:52:40+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-02.html">&laquo; Open Web Platform Weekly Summary - 2011-03-07 - 2011-03-13</a> |
                        <a href="http://www.w3.org/QA/">Main</a>
                        | <a href="http://www.w3.org/QA/2011/03/openweb-weekly-04.html">Open Web Platform Weekly Summary - 2011-03-21 - 2011-03-27 &raquo;</a>
                     </p>

                        <h2 class="entry-header">Open Web Platform Weekly Summary - 2011-03-14 - 2011-03-20</h2>
                           <div class="entry-body">
                              <p>This is the third edition of our <a href="http://www.w3.org/QA/archive/open_web/">weekly</a> summary about the <a href="http://www.w3.org/wiki/Open_Web_Platform">Open Web Platform</a>. The intent is to give an overview of the discussions, proposals, decisions which have happened during the last week around <a href="http://w3.org/html5/">HTML5</a> and sometimes more broadly the Open Web Platform. This weekly summary covers events in multiple <a href="http://www.w3.org/">W3C</a> groups, and some outside events as well. Feel free to chime in the comments and add information or ask for more details. </p>

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

<p>This was a big week in terms of decisions. I recommend to read carefully the decision made by the HTML Working Group. They are always very detailed and give a very good overview about the issues. They also propose a way to reopen the issue with meaningful materials. </p>

<ul>
<li><a href="http://www.w3.org/2002/09/wbs/40318/issue-27-objection-poll/">poll</a> on rel ownership is open until March 24.</li>
<li><a href="http://www.w3.org/2002/09/wbs/40318/issue-122-objection-poll/">poll</a> on examples for alt attributes is open until March 24</li>
<li><a href="http://www.w3.org/2002/09/wbs/40318/issue-32-objection-poll/">poll</a> on summary attribute on table is open until March 28</li>
</ul>

<h4 id="figureelementsinaparagraphissue-128">figure elements in a paragraph ISSUE-128</h4>

<p>Should figure elements be allowed in a paragraph (<code>&lt;p&gt;</code> element)? It has impacts on the parsing algorithm.  The <a href="http://www.w3.org/html/wg/tracker/issues/128">issue 128</a> summarizes the discussion and the <a href="http://www.w3.org/html/wg/wiki/ChangeProposals/FigureInP">change proposals</a>. The <a href="http://www.w3.org/2002/09/wbs/40318/issue-128-objection-poll/results">straw poll</a> led to the <a href="http://www.w3.org/mid/4D7F8214.6050902@intertwingly.net">decision</a> to treat <code>&lt;figure&gt;</code> as being equivalent to <code>&lt;p&gt;</code> or <code>&lt;aside&gt;</code>. For reopening the issue, you might want to give concrete use cases that specifically require figures within a paragraph.  Ideally this would be accompanied by a list of actual sites that actually demonstrate this need.</p>

<h4 id="parsingquotesincontent-typeheaders-issue125">Parsing quotes in Content-Type headers - ISSUE 125</h4>

<p>When parsing quotes in Content-Type headers in &#8220;meta&#8221; elements, there is now a consensus from browser implementers. IE9 Release Candidate implementing the same behaviour than others. The <a href="http://lists.w3.org/Archives/Public/public-html/2011Jan/0337">change proposal</a> has been <a href="http://www.w3.org/mid/4D7F8212.2000709@intertwingly.net">adopted</a> for the <a href="http://www.w3.org/html/wg/tracker/issues/125">issue 125</a> after a <a href="http://www.w3.org/2002/09/wbs/40318/issue-125-objection-poll/results">straw poll</a></p>

<h4 id="normativereferenceforus-ascii-issue101">Normative reference for US-ASCII - ISSUE 101</h4>

<p>There was not satisfying free document for referencing precisely what is US-ASCII. It has been <a href="http://www.w3.org/mid/4D7F820E.5020706@intertwingly.net">decided</a> to retain references to free of charge documents for the <a href="http://www.w3.org/html/wg/tracker/issues/101">issue 101</a> following the comments on the <a href="http://www.w3.org/2002/09/wbs/40318/issue-101-objection-poll/results">poll</a>. To reopen the issue, we should be able to provide a stable, maintained, official reference that is made available royalty free that defines ASCII in terms of UNICODE code points. It sounds like there is a need for a W3C note such as the one which was made for date and time.</p>

<h4 id="progresselementinhtml5-issue96">Progress element in HTML5 - ISSUE 96</h4>

<p>You should read carefully the  <a href="http://www.w3.org/mid/4D84BA4F.5050605@intertwingly.net">decision</a> on <a href="http://www.w3.org/html/wg/tracker/issues/96">issue 96</a> which has been documented at length. Following the <a href="http://www.w3.org/2002/09/wbs/40318/issue-96-objection-poll/results">poll</a>, it has been decided to keep the <code>progress</code> element into HTML5. There is already support from authoring communities and implementers.</p>

<h4 id="nofollowandnoreferrervaluesonlink-issue124"><code>nofollow</code> and <code>noreferrer</code> values on link - ISSUE 124</h4>

<p>A few years ago, a group of companies introduced <code>nofollow</code> and <code>noreferrer</code>  for the <code>rel</code> attribute values for fighting against spam. It has been <a href="http://www.w3.org/html/wg/tracker/issues/124">questionned</a> if these values should be allowed on link elements. After the <a href="http://www.w3.org/2002/09/wbs/40318/issue-124-objection-poll/results">straw poll</a>, it has been <a href="http://www.w3.org/mid/4D84BAED.8080504@intertwingly.net">decided</a> that these values should not be allowed on the link element.</p>

<h4 id="attributevaluessemanticdiversityonaandlinkelements-issue127">attribute values semantic diversity on <code>a</code> and <code>link</code> elements - ISSUE 127</h4>

<p>The <a href="http://www.w3.org/html/wg/tracker/issues/127">issue 127</a> summarizes if the <code>a</code> and <code>link</code> elements may have similar attributes with different semantics.  It has been <a href="http://www.w3.org/mid/4D84BB77.8070306@intertwingly.net">decided</a> after the <a href="http://www.w3.org/2002/09/wbs/40318/issue-127-objection-poll/results">straw poll</a> that the specification need to be clarified for legibility. The issue relates also to <a href="http://www.w3.org/html/wg/tracker/issues/27">issue 27</a> about the convergence of Atom, HTTP, and HTML5 for these values.</p>

<h4 id="multiplelanguageforhtmlcontent-issue88">Multiple language for HTML content - ISSUE 88</h4>

<p>Is it possible to have multiple language in the <code>content</code> attribute of the <code>meta</code> element. Should the <code>Content-Language</code> pragma be treated as conforming. It has been <a href="http://www.w3.org/mid/4D84B9B4.3040809@intertwingly.net">decided</a> on <a href="http://www.w3.org/html/wg/tracker/issues/88">issue 88</a> following the <a href="http://www.w3.org/2002/09/wbs/40318/issue-88-objection-poll/results">straw poll</a> that <code>Content-Language</code> would be non-conforming.</p>

<h4 id="iriandhtml5-issue56">IRI and HTML5 - ISSUE 56</h4>

<p>A RFC defines IRI, international URIs. The initial wording of the specification showed discrepancies in between the two. It has been <a href="http://www.w3.org/mid/4D84CDA4.8010908@intertwingly.net">decided</a> on <a href="http://www.w3.org/html/wg/tracker/issues/56">issue 56</a> following the <a href="http://www.w3.org/2002/09/wbs/40318/issue-56-objection-poll/results">straw poll</a> to restore a text explaining how to translate input strings contained in text/html documents into URIs.</p>

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

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

<ul>
<li>Steve Faulkner <a href="http://www.w3.org/mid/AANLkTi=N=k0E3Fs4P0xj_JgpGWkqs8iE-adKo+ifzehM@mail.gmail.com">proposed</a> text <a href="http://www.html5accessibility.com/tests/img-longdesc.html">examples</a> for longdesc attributes. </li>
<li>Markus Ernst <a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-March/030821.html">proposed</a> to set a  restricted palette for input type=color</li>
<li>Jeb Boniakowski would like to be able to paste images: <a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-March/030879.html">Rich Paste &amp; DataTransfer / DataTransferItems API</a></li>
<li><a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-March/030929.html">PeerConnection: encryption feedback</a> by Glenn Maynard</li>
<li><a href="http://aryeh.name/gitweb.cgi?p=editcommands;a=blob_plain;f=editcommands.html;hb=HEAD">HTML Editing Commands</a> <a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-March/030714.html">proposed</a> by Aryeh Gregor.</li>
<li><a href="http://www.w3.org/mid/AANLkTikRgr7RO73Er10ec5wDkzeAWOMgqGKsq7d_ovTB@mail.gmail.com">proposal</a> by Tony Gentilcore for a <a href="http://dev.chromium.org/searchbox">searchbox API</a></li>
<li>Tab Atkins <a href="http://www.w3.org/mid/AANLkTik2J_yq3WgTwJLJaKZzZdSYQQLT=748VJ1NCxP0@mail.gmail.com">proposed</a> a CSS Mixins. A mixin is a block of rules that can be &#8220;mixed into&#8221; other declaration
blocks.</li>
</ul>

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

<ul>
<li>March 17 <a href="http://www.w3.org/2011/03/17-html-wg-minutes">HTML WG minutes</a> </li>
<li><a href="http://www.w3.org/2011/identity-ws/">W3C Workshop on Identity in the Browser</a> - 24/25th May 2011, Mountain View (USA)</li>
<li><a href="http://www.w3.org/2011/track-privacy/">W3C Workshop on Web Tracking and User Privacy, 28/29 April 2011, Princeton, NJ, USA</a></li>
<li><a href="http://www.w3.org/TR/2011/WD-webmessaging-20110317/">HTML5 Web Messaging</a> Last Call</li>
<li><a href="http://www.w3.org/TR/2011/WD-media-frags-20110317/">Media Fragments URIs</a> Last Call</li>
*
</ul>

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

<ul>
<li><a href="http://www.w3.org/mid/AANLkTik1USpaF7KuSfW2DACmmrRcf2JCr9_hrQnnNqzn@mail.gmail.com">Component Model is not an Isolation Model</a></li>
<li><a href="http://www.w3.org/mid/4CD526D7-17BB-4069-B800-9A121D6E6990@apple.com">Using ArrayBuffer as payload for binary data to/from Web Workers</a></li>
<li>The <a href="http://html5.org/tools/web-apps-tracker?from=5944&amp;to=5945">device element</a> was dropped from the specification. Ian Hickson <a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-March/030941.html">explained why</a> and proposed a detail Javascript API</li>
<li>Ian Hickson <a href="http://www.w3.org/mid/Pine.LNX.4.64.1103211005470.25791@ps20323.dreamhostps.com">sent</a> a change proposal for Audio and Video Track Selection and Synchronisation  for Media Elements (issue 152)</li>
<li>Jonas Sicking is concerned about <a href="http://www.w3.org/mid/AANLkTimBVm9Bp_eo4FkWV+-cFfQg71TJ9S_=AukCuC9_@mail.gmail.com">using ARIA to override semantics</a></li>
<li><a href="http://www.w3.org/html/wg/tracker/issues/147">issue 147</a> about playback rate is highly debated, and Silvia Pfeiffer has sent a   <a href="http://www.w3.org/mid/AANLkTini9nAAdF4XD6kouzb3CBTG=VKCse2LfTCDiEo=@mail.gmail.com">change proposal</a></li>
<li>Daniel Glazman expressed a <a href="http://www.w3.org/mid/4D837E7D.2090102@disruptive-innovations.com">disagreement</a> on the non validity of the <code>name</code> attribute in HTML5.</li>
<li>Proposal about <a href="http://www.w3.org/html/wg/wiki/ChangeProposals/InstateLongdesc#.3Ccanvas_src.3E">canvas src</a> is still heavily debated on the HTML WG mailing list.</li>
<li>Geoff Freed sent a <a href="http://www.w3.org/mid/C99FCA53.168C5%25geoff_freed@wgbh.org">long comment</a> about <code>longdesc</code> attribute on the <a href="http://www.w3.org/html/wg/tracker/issues/30">issue 30</a>. You should read also Laura Carlson&#8217;s <a href="http://www.w3.org/mid/AANLkTi=1AtrmuN07NfLx-rX3LzubgkO=hvTd-TT+JTJ8@mail.gmail.com">email</a>.</li>
<li>The license debate for HTML5 specification is still going on and not solved.</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 March 20, 2011  9:52 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/03/openweb-weekly-03.html">Permalink</a>
                                 | <a href="http://www.w3.org/QA/2011/03/openweb-weekly-03.html#comments">Comments (0)</a>
                                 | <a href="http://www.w3.org/QA/2011/03/openweb-weekly-03.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="9043" />
<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:11 $</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>