openweb-weekly-21.html 18.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='css, dom, openweb, web architecture, webapps' />
    <meta name="description" content="This week, one of the main discussions has been around developing (or not) a support for XPath in find and findAll methods. The Open Web Platform weekly summary is also mentioning Web architecture, Web Apps WG hosting new work." />
    <meta name="revision" content="$Id: openweb-weekly-21.html,v 1.11 2011/12/16 03:00:32 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-11-21 - 2011-11-28 - W3C Blog</title>

   <link rel="start" href="http://www.w3.org/QA/" title="Home" />
   <link rel="prev" href="http://www.w3.org/QA/2011/11/rdfa_11_meets_json-ld_in_the_d.html" title="RDFa 1.1 meets JSON-LD in the Distiller…" />
   <link rel="next" href="http://www.w3.org/QA/2011/11/interview_roger_cutler_on_w3c.html" title="Interview: Roger Cutler on W3C and Chevron use of Semantic Web Technology" />

   <!--
<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/11/openweb-weekly-21.html"
    trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/449"
    dc:title="Open Web Platform Weekly Summary - 2011-11-21 - 2011-11-28"
    dc:identifier="http://www.w3.org/QA/2011/11/openweb-weekly-21.html"
    dc:subject="Open Web"
    dc:description="This week, one of the main discussions has been around developing (or not) a support for XPath in find and findAll methods. The Open Web Platform weekly summary is also mentioning Web architecture, Web Apps WG hosting new work."
    dc:creator="Karl Dubost"
    dc:date="2011-11-28T03:18:00+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/11/rdfa_11_meets_json-ld_in_the_d.html">&laquo; RDFa 1.1 meets JSON-LD in the Distiller…</a> |
                        <a href="http://www.w3.org/QA/">Main</a>
                        | <a href="http://www.w3.org/QA/2011/11/interview_roger_cutler_on_w3c.html">Interview: Roger Cutler on W3C and Chevron use of Semantic Web Technology &raquo;</a>
                     </p>

                        <h2 class="entry-header">Open Web Platform Weekly Summary - 2011-11-21 - 2011-11-28</h2>
                           <div class="entry-body">
                              <p>This week, one of the main discussions has been around developing (or not) a support for XPath in <code>find</code> and <code>findAll</code> methods. 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> summary is also mentioning Web architecture, Web Apps WG hosting new work.</p>

<h3>HTML5</h3>

<p>The old <a href="http://www.w3.org/TR/html4/struct/tables.html#adef-abbr">HTML4 <code>abbr</code> attribute</a> has been deprecated in the HTML5 specification. The role of the attribute was to give a short form of table cells content. It was meant to help users getting the content of these cells quickly. A <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=704754">Firefox patch</a> has just been proposed to implement it.</p>

<p>Frank Olivier (Microsoft) <a href="http://lists.w3.org/Archives/Public/public-html/2011Nov/0210">said</a>:</p>

<blockquote><p>Text editing is certainly a fool&rsquo;s errand in canvas.</p></blockquote>

<p>and indeed there was previous attempt to recreate text-editor all in Canvas. Some of these projects have been abandoned since. That said the group is struggling to find solutions for raising accessibility in canvas to an acceptable level. One solution which is being explored is to add primitives for Path.</p>

<h3>Web Apps</h3>

<p>There are proposals for</p>

<ul>
<li>a <a href="http://www.w3.org/community/networkfriendly/">community group working on best practices and developer guidelines for building apps and webapps</a> that use Web technologies in a &ldquo;network-friendly&rdquo; way</li>
<li>one on the concept of <a href="http://www.w3.org/community/native-web-apps/">Native Web Apps</a>. New work on W3C widgets will take place there as <a href="http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/1020">announced</a> by Marcos Caceres.</li>
</ul>


<p>The work on <a href="http://dglazkov.github.com/component-model/">Component Models</a> that I mentioned a few times about under the label shadow DOM is <a href="http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/1144">moving to the Web Apps WG</a> led by Dimitry Glazkov (Chromium team).</p>

<p>Darin Fischer (Google) proposes to add the <a href="http://dvcs.w3.org/hg/webevents/raw-file/default/mouse-lock.html">Pointer Lock</a> (formerly known as Mouse Lock) spec and the <a href="http://dvcs.w3.org/hg/webevents/raw-file/tip/gamepad.html">Gamepad</a> spec be added to the Web Applications WG&rsquo;s charter.</p>

<h3>ECMAScript</h3>

<p>Some fundamental features are missing in JavaScript. I know for example missing things like <code>startsWith</code> and <code>endsWidth</code> on strings annoy me a lot. There is a <a href="http://blogs.msdn.com/b/ie/archive/2011/11/22/evolving-ecmascript.aspx">proposal for evolving ECMAScript</a> on IE blog.</p>

<h3>DOM</h3>

<p>There has been <a href="http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/thread.html#msg1047">a gigantic thread</a> (with a lot of misunderstandings and rebuttals) about allowing XPath in the <code>find</code>/<code>findAll</code> APIs we were talking about last week. The discussion goes along the common <a href="http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/thread.html#msg1236">permathread</a> about CSS selectors and XPath has a way to select a path in a DOM. With similar goals, they often addressed different problem spaces and they do not have the exact same set of features. Some people argue it is not worth the cost adding XPath for selecting nodes. Eventually, people will reach an agreement. We are not there yet.</p>

<p><code>matchesSelector</code> is verbose and people start to look at ways to <a href="http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/thread.html#msg1032">make it shorter for Web developers</a>. Two proposals have been by Tab Atkins (Google) with <code>.matches()</code> and <code>.is()</code>. Though Dimitri Glazkov said that he wishes to use <code>.is()</code> for components. It would be used like</p>

<pre><code>elt.matches("div span")
</code></pre>

<h3>CSS</h3>

<p>Jake Archibald (Lanyrd) is not satisfied with the <a href="http://jaffathecake.posterous.com/scoped-styles-the-shadow-dom">Shadow DOM and scope stylesheets</a> we mentioned a few times in that column.</p>

<p>Experimenting with new styles for CSS Specifications. <a href="http://dvcs.w3.org/hg/FXTF/raw-file/tip/custom/index.html">CSS shaders</a> is currently having the proposal.</p>

<h3>Web Architecture</h3>

<p>URIs are one of the corner stones of the Web architecture. There is a specification clearly defining the <a href="http://tools.ietf.org/html/rfc3986">URI syntax and meaning</a>. But as usual with the human Web, things get deployed with errors in a distributed way. What is happening when you get something which looks like an URI but is not really a URI. User agents have for long implemented techniques to cope with the common URI mispellings found on the Web. Mike Smith will <a href="http://lists.w3.org/Archives/Public/public-html/2011Nov/0194">start working</a> on a document on how browsers process URIs, following a proposal made at HTML WG F2F during the TPAC 2011. It has been suggested that this should be part of the <a href="http://dvcs.w3.org/hg/url/raw-file/tip/Overview.html">URL API</a> document.</p>

<h3>HTTP</h3>

<p>The <code>Referer</code> HTTP header has been a concern for a long time in terms of security and privacy. Adam Barth is proposing to <a href="http://www.schemehostport.com/2011/11/referer-sic.html">add a <code>referrer</code> attribute in HTML</a> (<code>meta</code> element) for suppressing its value from each HTTP requests.</p>

<p>This week, the theme of <a href="http://annevankesteren.nl/">Anne Van Kesteren</a>'s <a href="http://blog.whatwg.org/weekly-xmlhttprequest-merger">report</a> is about XMLHttpRequest.</p>

<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 team</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 November 28, 2011  3:18 AM 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/11/openweb-weekly-21.html">Permalink</a>
                                 | <a href="http://www.w3.org/QA/2011/11/openweb-weekly-21.html#comments">Comments (4)</a>
                                 | <a href="http://www.w3.org/QA/2011/11/openweb-weekly-21.html#trackback">TrackBacks (0)</a>
</p>


<h3 class="comments-header" id="comments">Comments</h3>
<div class="comment" id="comment-882563">
<p class="comment-meta" id="c882563">
<span class="comment-meta-author"><strong>steve faulkner </strong></span>
<span class="comment-meta-date"><a href="#c882563">#</a> 2011-12-01</span>
</p>
<div class="comment-bulk">
<p>Hi Karl,</p>

<p>In regards to firefox implementation of the abbr attribute its more than 'proposed', its <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=704754#c11" rel="nofollow">inbound</a> "Verified fixed in Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0a1) Gecko/20111127 Firefox/11.0a1".</p>

<p>I would suggest the continued highlighting of the 'text editor' bogeyman, does not serve to find solutions for the real world canvas accessibility issues yet to be resolved, but it interesting to note the work on <a href="http://dvcs.w3.org/hg/ime-api/raw-file/tip/Overview.html" rel="nofollow">JavaScript based IMEs</a>. Also Charles Pritchard has provided a summary of discussions on canvas accessibility, which is worth a read <a href="http://lists.w3.org/Archives/Public/public-canvas-api/2011OctDec/0061.html" rel="nofollow">[public-canvas-api] Summary of accessibility threads between 2009 - 2011</a>.</p>

</div>
</div>


<div class="comment" id="comment-883608">
<p class="comment-meta" id="c883608">
<span class="comment-meta-author"><strong>Karl Dubost <a class="commenter-profile" href="http://my.opera.com/karlcow/blog/"><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="#c883608">#</a> 2011-12-01</span>
</p>
<div class="comment-bulk">
<p>Ah indeed. Thanks for the clarification Steve. That is very useful.</p>

</div>
</div>


<div class="comment" id="comment-951252">
<p class="comment-meta" id="c951252">
<span class="comment-meta-author"><strong>Stéphane Deschamps </strong></span>
<span class="comment-meta-date"><a href="#c951252">#</a> 2011-12-13</span>
</p>
<div class="comment-bulk">
<p>I'm sorry to be not too close to the HTML5 discussions, but what on earth is the rationale behind dropping the abbr attribute?</p>

<p>It <em>is</em> useful and we've used it a lot in my company for a long time.</p>

<p>Where is the cowpath and why are we putting stones on it so that cows must walk elsewhere?</p>

<p>This plus longdesc, which is a long-standing discussion point (and I still haven't seen a proper, solid replacement for it), makes me think my own implementation of HTML5 will not be standard. But at least it will work for blind people.</p>

</div>
</div>


<div class="comment" id="comment-951960">
<p class="comment-meta" id="c951960">
<span class="comment-meta-author"><strong>Karl Dubost <a class="commenter-profile" href="http://my.opera.com/karlcow/blog/"><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="#c951960">#</a> 2011-12-13</span>
</p>
<div class="comment-bulk">
<p>Stéphane, not sure you have seen Steve's comment here. Firefox has implemented it recently, and if others are following, I guess it is likely to be reopened. I'm pretty sure if there are implementations experience of abbr in other products that would be valuable input for people.</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="9276" />
<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:32 $</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>