<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>W3C HTML Working Group</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/html/" />
    <link rel="self" type="application/atom+xml" href="http://www.w3.org/QA/atom.xml" />
   <id>tag:www.w3.org,2012:/QA//1</id>
    <updated>2012-01-16T04:03:53Z</updated>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.34-en</generator>
 

<entry>
    <title>W3C TAG Publishes Finding on Identifying Application State</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/12/w3c_tag_publishes_finding_on_i.html" />
    <id>tag:www.w3.org,2011:/QA//1.9306</id>
    
    <published>2011-12-24T16:53:15Z</published>
    <updated>2011-12-24T18:49:00Z</updated>
    
    <summary type="html">The W3C TAG has published a finding on Identifying Application State.  See http://www.w3.org/2001/tag/doc/IdentifyingApplicationState</summary>
    <author>
        <name>Ashok Malhotra</name>
        
    </author>
    
        <category term="HTML" />
    
        <category term="Web Architecture" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[<p>The W3C TAG is pleased to announce the publication of a new TAG Finding "<a href="http://www.w3.org/2001/tag/doc/IdentifyingApplicationState">Identifying Application State</a>."</p>
<p>
URIs were originally used primarily to identify documents on the Web, or with the use of fragment identifiers, portions of those documents. As Web content has evolved to include Javascript and similar applications that have extensive client-side logic, a need has arisen to use URIs to identify states of such applications, to provide for bookmarking and linking those states, etc. This finding sets out some of the challenges of using URIs to identify application states, and recommends some best practices. A more formal introduction to the Finding and its scope can be found in its <a href="http://www.w3.org/2001/tag/doc/IdentifyingApplicationState#abstract">abstract</a>.</p>
<p>The W3C TAG would like to thank Ashok Malhotra, who did much of the analysis and editing for this work, and also former TAG member T.V. Raman, who first brought this issue to the TAG's attention, and who wrote earlier drafts on which this finding is based.</p> 

]]>
        
    </content>
</entry>

<entry>
    <title>Open Web Platform Weekly Summary - 2011-12-05 - 2011-12-11</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/12/open_web_platform_weekly_summa.html" />
    <id>tag:www.w3.org,2011:/QA//1.9291</id>
    
    <published>2011-12-12T23:32:24Z</published>
    <updated>2011-12-12T23:35:40Z</updated>
    
    <summary type="html">The Open Web Platform weekly summary is about love for the open Web, about the work we do together, about the hours we spent every day to create a better Web. I can work in this domain, because others gave an open environment for working. Let’s keep it open.</summary>
    <author>
        <name>Karl Dubost</name>
        <uri>http://my.opera.com/karlcow/blog/</uri>
    </author>
    
        <category term="HTML" />
    
        <category term="HTTP" />
    
        <category term="Open Web" />
    
        <category term="W3C Life" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[<p>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 about love for the open Web, about the work we do <strong>together</strong>, about the hours we spent every day to create a better Web. I can work in this domain, because others gave an open environment for working. Let&rsquo;s keep it open.</p>

<h3>HTML5</h3>

<p>The specification has been <a href="http://html5.org/r/6845">modified</a> to allow two syntaxes for the <code>time</code> element. You may write time with a T or a <a href="http://wiki.whatwg.org/wiki/Time_element#permit_space_instead_of_T_in_datetimes">single space separator</a> between the date and the time.</p>

<pre><code>&lt;time&gt;2011-12-24T23:59&lt;/time&gt;
&lt;time&gt;2011-12-24 23:59&lt;/time&gt;
</code></pre>

<p>XML documents have a <code>UTF-8</code> default encoding. Kornel Lesiński <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15076">asked</a> if it would be possible to do that for documents with an HTML5 doctype. Henri Sivonen (Mozilla), who is also developing the HTML5 parser for Firefox, rejected the suggestion. It would introduce more incompatibilities and more specific behaviors than the already existing explicit mechanisms.</p>

<h3>HTML Rich Content</h3>

<p>Sometimes Web developers need to extend their content with a richer semantics by adding simple data structure to their markup. A <a href="http://www.w3.org/TR/rdfa-lite/">first Working Draft for RDFa Lite 1.1 </a> has been published. For example to specify that this column is written by a human and not a cow.</p>

<pre><code>&lt;p vocab="http://schema.org/" 
   resource="#karl" 
   typeof="Person"&gt;
   This blog post is written by 
   &lt;span property="name"&gt;Karl Dubost&lt;/span&gt;.&lt;/p&gt;
</code></pre>

<p>The purpose of this group is to develop a common specification in OWL
for structured and unstructured annotations on Web documents, based on
prior work developed by the Annotation Ontology
(http://code.google.com/p/annotation-ontology/) and Open Annotation
Collaboration (http://www.openannotation.org/) efforts.</p>

<p>You are invited to support the creation of this group:
 http://www.w3.org/community/groups/proposed#annotation</p>

<h3>Video Tracks</h3>

<p>The WebVTT format (Web Video Text Tracks) is a format intended for marking up external text track resources. <a href="http://dev.w3.org/html5/webvtt/">WebVTT</a> has escaped HTML5 to be developed by the <a href="http://www.w3.org/community/texttracks/">Web Media Text Tracks Community Group</a>. They also have a <a href="http://twitter.com/webvtt">twitter account</a>. Anne van Kesteren has created a <a href="http://quuz.org/webvtt/">WebVTT Validator</a> and published the <a href="https://bitbucket.org/annevk/webvtt">source code</a> on bitbucket. The syntax is a very simple text file.</p>

<pre><code>WEBVTT

00:11.000 --&gt; 00:13.000
&lt;v Roger Bingham&gt;We are in New York City

00:13.000 --&gt; 00:16.000
&lt;v Roger Bingham&gt;We're actually at the Lucern Hotel, just down the street
</code></pre>

<h3>Web Apps</h3>

<p>If humanity had an <a href="http://rniwa.com/editing/undomanager.html"><code>UndoManager</code> API</a> we might have been able to fix a lot of mistakes. Ryosuke Niwa (webkit) is working on such an API for the Web and he is asking feedback. A <a href="http://wiki.whatwg.org/wiki/UndoManager_Problem_Descriptions">long list of use cases</a> has been outlined to better understand what do we need to solve.</p>

<p>Dominique Hazaël-Massieux (W3C) has been giving a summary of the <a href="http://www.w3.org/2011/11/mobile-web-app-state.html">Standards for Web Applications on Mobile</a>. He has published an update for November 2011.</p>

<h3>DOM</h3>

<p>The new methods for <code>append</code>, <code>prepend</code>, … that we mentioned a few weeks ago have been addred to the DOM 4 specification in the <a href="http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#mutation-methods">mutation methods section</a>. This triggered a new <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=14188">syntax requirement for WebIDL</a>, which has not yet been completely defined. Anne van Kesteren (Opera) has also started to define <a href="http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#mutation-observers">Mutation observers</a>.</p>

<h3>CSS</h3>

<p>An update has been published for <a href="http://www.w3.org/TR/2011/WD-css3-images-20111206/">CSS Image Values and Replaced Content</a> and a new <strong>editor</strong> draft for <a href="http://dev.w3.org/csswg/css3-grid-align/">CSS3 Grid Layout</a>. As a kind reminder, these are drafts and then <strong>not stable</strong>. If the implementations change them or drop these features, you will have to eat your own hat :)</p>

<h3>Web Architecture</h3>

<p>A tendency in Web development has emerged a little while ago. Web developers started to push hash sign in their URIs not to define an anchor in the document but the state of an application. The W3C Technical Architecture Group has summarized <a href="http://www.w3.org/2001/tag/doc/IdentifyingApplicationState-20111130">best practices for handling hash signs URIs</a>.</p>

<p>The W3C TAG is <a href="http://www.w3.org/2001/tag/products/">working on a few topics</a> in parallel. You could participate constructively to the discussions by subscribing to the <a href="http://lists.w3.org/Archives/Public/www-tag/">www-tag mailing list</a>.</p>

<h3>HTTP</h3>

<p>You can now buffer this number, RFC 6455, in your memory lane. The <a href="http://tools.ietf.org/html/rfc6455">WebSocket Protocol</a> is <a href="http://www.ietf.org/mail-archive/web/ietf-announce/current/msg09663.html">accepted</a>. Though be careful, because there might still be a bit of breakage depending if your browser has released a version of the implementation but disabled by default. Check your preferences.</p>

<p>In the discussion about extending HTTP status code, Roy Fielding (Adobe) gave an interesting <a href="http://lists.w3.org/Archives/Public/ietf-http-wg/2011OctDec/0364">rule for knowing how/when to extend the list of codes</a>.</p>

<blockquote><p>When extending HTTP status codes, the question that needs to be asked
is &ldquo;how will a client process this response differently than any of
the existing status codes?&rdquo;</p></blockquote>

<h3>Elsewhere</h3>

<ul>
<li><a href="http://movethewebforward.org/">Move The Web Forward</a> is the new kid in town. It gives a long list of resources  to help Web developers stay informed about what&rsquo;s going on the Open Web platform.</li>
<li><a href="http://redbot.org/">Redbot</a>, the HTTP validation tool developed by Mark Nottingham, now supports <a href="http://blog.redbot.org/https-in-redbot">HTTP over SSL and TLS</a></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 team</a> at <a href="http://www.opera.com/">Opera Software</a>.</p>
]]>
        
    </content>
</entry>

<entry>
    <title>Open Web Platform Weekly Summary - 2011-11-29 - 2011-12-04</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/12/openweb-weekly-22.html" />
    <id>tag:www.w3.org,2011:/QA//1.9281</id>
    
    <published>2011-12-05T19:42:53Z</published>
    <updated>2011-12-05T19:59:28Z</updated>
    
    <summary type="html">The Open Web Platform weekly summary is about HTML5 oldies, shadows and intents, and protocols.</summary>
    <author>
        <name>Karl Dubost</name>
        <uri>http://my.opera.com/karlcow/blog/</uri>
    </author>
    
        <category term="HTML" />
    
        <category term="HTTP" />
    
        <category term="Open Web" />
    
        <category term="W3C Life" />
    
        <category term="Web Applications" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[<p>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 about HTML5 oldies, shadows and intents, and protocols.</p>

<h3>HTML5</h3>

<p>Yehuda Katz and a few others have started a discussion on  <a href="http://lists.w3.org/Archives/Public/public-html/2011Nov/thread.html#msg234">Restoring PUT and DELETE</a> in HTML5 forms (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=1067">Issue 1067</a>). The Ruby on Rails Web framework is currently using a <a href="http://guides.rubyonrails.org/form_helpers.html#how-do-forms-with-put-or-delete-methods-work">hack for simulating PUT and DELETE</a>.</p>

<p>The Web is an amazing big pile of history. <code>border</code> attribute on <code>table</code> elements didn&rsquo;t have any units. Though people had a tendency to put units such as the wrong <code>&lt;table border="5px"&gt;</code>. So browsers repaired automagically to take into account only the beginning of the string and ignore any trailing characters. Sylvain Galineau (Microsoft) raised an <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=15047">issue</a> because he thought it would create issues for microdata values. Ian Hickson mentioned that the incorrect values were not <strong>valid</strong> but fixed by the browser if wrong.</p>

<p><code>INS</code> and <code>DEL</code> elements which are used to track insertion and deletion of contents in HTML have a very simple model. So simple that according to Daniel Glazman (Disruptive Innovations), it is <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id=13057">not easily implementable</a> in any useful way for authoring tools.</p>

<p>A Community Group has been proposed to <a href="http://www.w3.org/community/groups/proposed#html5spec">discuss ideas around the future of HTML and associated features</a>.</p>

<h3>Web Apps</h3>

<p>Webkit has a <a href="https://bugs.webkit.org/show_bug.cgi?id=73528">proposed patch</a> for the <a href="http://www.w3.org/TR/netinfo-api/">Network Information API</a>. This is an interesting API because it allows to create apps which behave differently depending if the network is 3g, wifi, etc. For example, imagine a <strong>responsive Web design</strong> where images of adequate sizes are sent depending on the type of network which gives a good idea of what could be the bandwidth.</p>

<p>Rich Tibbet (Opera) has proposed a <a href="http://richtr.tumblr.com/post/12929135260/a-better-model-for-web-intents">model for the Web intents</a> work.</p>

<p>Simon Pieters (Opera) wanted an <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=15007">API to queue a task</a>. After discussing about the opportunity of such a need, Glenn Maynard proposed a piece of code that finally Simon extended.</p>

<pre><code>var queueTask = function(task) {
    var mc = new MessageChannel();
    var args = [].slice.call(arguments, 1);
    mc.port1.onmessage = function(){ 
        this.onmessage = null; task.apply(task, args); 
        };
    mc.port2.postMessage(null);
    };
queueTask(function(arg) { console.log(arg, this) }, "test"); 
</code></pre>

<p>Dimitri Glazkov (Chromium team) has proposed a high level <a href="http://dvcs.w3.org/hg/webcomponents/raw-file/tip/explainer/index.html">overview of Web Components for Web Developers</a>.</p>

<h3>DOM</h3>

<p>The <code>setAttributeNS()</code> is <a href="http://www.w3.org/mid/op.v5pue1ha64w2qv@annevk-macbookpro.local">implemented differently</a> in IE, Firefox, Webkit and Opera. The discussion, which started on the mutability of attributes, led to discuss about simplifying the platform for HTML documents by removing the namespacing of attributes. According to Jonas Sicking (Mozilla), that would also improve browser performances. There would still be needed for <code>XMLDocument</code> interface.</p>

<h3>HTTP</h3>

<p>When exchanging data in between client and server, there are a few techniques. One of them is XMLHttpRequest which helps inject a data flow into the page without reloading the full context. People often uses it to transfer JSON packaged data. Anne van Kestern (Opera) has added <code>json</code> response type to <a href="http://dvcs.w3.org/hg/xhr/raw-file/tip/Overview.html#the-responsetype-attribute">XMLHttpRequest</a>.</p>

<p>When a client and server interact on the Web, the server answer to client requests with 3 number codes. These have very specific meanings. For example, <code>200</code> means that the server has successfully answered the client request.  It is happening quite often that Web developers (specifically those developing Web APIs) lack some <a href="http://en.wikipedia.org/wiki/List_of_HTTP_status_codes">HTTP status code</a> to have a richer interactions between the client and the server. Mark Nottingham has been working for a while on <a href="http://tools.ietf.org/html/nottingham-http-new-status">new HTTP status code</a>.</p>

<p>HTTP/1.1 allows many types of characters. This has a tendency to create security issues when, for example in <a href="http://tools.ietf.org/html/rfc3875">CGI/1.1</a>, translating these characters into UNIX environment variables.  Some of them are not valid and/or parseable characters. Yutaka Oiwa <a href="http://www.w3.org/mid/4EDC3AC0.70803@aist.go.jp">brought</a> the subject on HTTPbis mailing list.</p>

<h3>Elsewhere</h3>

<ul>
<li><a href="http://codemirror.net/">CodeMirror</a> is a JavaScript library that can be used to create a relatively pleasant editor interface for code-like content ― computer programs, HTML markup, and similar.</li>
<li><a href="http://24ways.org/2011/unicode-range">Creating Custom Font Stacks with Unicode-Range</a></li>
<li><a href="http://blogs.msdn.com/b/ie/archive/2011/11/29/html5-for-applications-the-fourth-ie10-platform-preview.aspx">IE10 Preview 4th</a> has support for CORS.</li>
<li>Firefox seems likely after Chrome to support <a href="https://wiki.mozilla.org/Platform/Features/SPDY">SPDY</a></li>
</ul>


<p>This week, the theme of <a href="http://annevankesteren.nl/">Anne Van Kesteren</a>&rsquo;s <a href="http://blog.whatwg.org/weekly-encoding-woes">report</a> about Encoding woes and WebVTT.</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>
]]>
        
    </content>
</entry>

<entry>
    <title>Open Web Platform Weekly Summary - 2011-11-21 - 2011-11-28</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/11/openweb-weekly-21.html" />
    <id>tag:www.w3.org,2011:/QA//1.9276</id>
    
    <published>2011-11-28T03:18:00Z</published>
    <updated>2011-12-01T03:24:10Z</updated>
    
    <summary type="html">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.</summary>
    <author>
        <name>Karl Dubost</name>
        <uri>http://my.opera.com/karlcow/blog/</uri>
    </author>
    
        <category term="HTML" />
    
        <category term="Open Web" />
    
        <category term="W3C Life" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[<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>
]]>
        
    </content>
</entry>

<entry>
    <title>RDFa 1.1 meets JSON-LD in the Distiller…</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/11/rdfa_11_meets_json-ld_in_the_d.html" />
    <id>tag:www.w3.org,2011:/QA//1.9268</id>
    
    <published>2011-11-24T16:12:20Z</published>
    <updated>2011-11-25T13:11:13Z</updated>
    
    <summary type="html">I have blogged recently on the update of the RDFa 1.1 Distiller. I have just added a cool new feature. Up to today, the possible serializations were RDF/XML, Turtle, and N Triples. Although not yet final, I decided to add...</summary>
    <author>
        <name>Ivan Herman</name>
        <uri>http://www.w3.org/People/Ivan</uri>
    </author>
    
        <category term="HTML" />
    
        <category term="Semantic Web" />
    
        <category term="Technology" />
    
        <category term="Tools" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[<p>I have<a href="http://www.w3.org/QA/2011/11/new_release_of_the_rdfa_11_dis.html"> blogged recently</a> on the update of the RDFa 1.1 Distiller. I have just added a cool new feature. Up to today, the possible serializations were <a href="http://www.w3.org/TR/rdf-syntax-grammar/">RDF/XML</a>, <a href="http://www.w3.org/TR/turtle/">Turtle</a>, and <a href="http://www.w3.org/TR/rdf-testcases/#ntriples">N Triples</a>. Although not yet final, I decided to add a <a href="http://json-ld.org/spec/latest/json-ld-syntax/">JSON-LD</a> serialization, too, in spite of the fact that JSON-LD is not yet final either (it is under development by a <a href="http://www.w3.org/community/json-ld/">W3C Community Group</a>). However,  adding this to the system it shows the potentials of this combination…</p>
<p>An example may be the schema.org example I used in <a href="http://www.w3.org/QA/2011/11/schemaorg_and_rdfa_11_lite_how.html">another blog</a> lately:</p>
<pre>&lt;div vocab="http://schema.org/" typeof="Product"&gt;
  &lt;img property="image" src="dell-30in-lcd.jpg" /&gt;
  &lt;span property="name"&gt;Dell UltraSharp 30" LCD Monitor&lt;/span&gt;

  &lt;div property="aggregateRating" typeof="AggregateRating"&gt;
    &lt;span property="ratingValue"&gt;87&lt;/span&gt;
    out of &lt;span property="bestRating"&gt;100&lt;/span&gt;
    based on &lt;span property="ratingCount"&gt;24&lt;/span&gt; user ratings
  &lt;/div&gt;

  &lt;div property="offers" typeof="AggregateOffer"&gt;
	&lt;span property="lowPrice"&gt;$1250&lt;/span&gt;
	to &lt;span property="highPrice"&gt;$1495&lt;/span&gt;
	from &lt;span property="offerCount"&gt;8&lt;/span&gt; sellers
  &lt;/div&gt;

  Sellers:
  &lt;div property="offers" typeof="Offer" &gt;
    &lt;a property="url" href="save-a-lot-monitors.com/dell-30.html"&gt;
     Save A Lot Monitors - $1250&lt;/a&gt;
  &lt;/div&gt;
  
  &lt;div property="offers" typeof="Offer"&gt;
    &lt;a property="url" href="jondoe-gadgets.com/dell-30.html"&gt;
    Jon Doe's Gadgets - $1350&lt;/a&gt;
  &lt;/div&gt;
  ...
&lt;/div&gt;     </pre>
<p>Running this through the distiller, one gets the following JSON output:</p>
<pre>{
    "@context": {
        "@vocab": "http://schema.org/",
        "@coerce": {
            "@iri": [
                "http://schema.org/image",
                "http://schema.org/offers",
                "http://schema.org/url",
                "http://schema.org/aggregateRating"
            ]
        }
    },
    "@type": "Product",
    "aggregateRating": {
        "@type": "AggregateRating",
        "ratingCount": "24",
        "ratingValue": "87",
        "bestRating": "100"
    },
    "offers": [
        {
            "@type": "Offer",
            "url": "http://www.example.org/save-a-lot-monitors.com/dell-30.html"
        },
        {
            "@type": "AggregateOffer",
            "lowPrice": "$1250",
            "highPrice": "$1495",
            "offerCount": "8"
        }
    ],
    "name": "Dell UltraSharp 30\" LCD Monitor",
    "image": "http://www.example.org/dell-30in-lcd.jpg"
}</pre>
<p>Of course, the generated JSON may be a bit more complex, e.g., if the original page contains other RDFa attributes generating other triples. But it still looks pretty readable to me…</p>
]]>
        
    </content>
</entry>

<entry>
    <title>Open Web Platform Weekly Summary - 2011-11-14 - 2011-11-20</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/11/openweb-weekly-20.html" />
    <id>tag:www.w3.org,2011:/QA//1.9266</id>
    
    <published>2011-11-22T20:05:39Z</published>
    <updated>2011-11-24T20:37:33Z</updated>
    
    <summary type="html">This week, the Open Web Platform weekly summary is about HTML5 Tidy (yes it is back!), A few things about web apps such as storage mechanisms, and a few discussions about DOM properties. CSS has been discussing a few things including the issue of vendor extensions. And more bite sized information. Enjoy!</summary>
    <author>
        <name>Karl Dubost</name>
        <uri>http://my.opera.com/karlcow/blog/</uri>
    </author>
    
        <category term="HTML" />
    
        <category term="Open Web" />
    
        <category term="W3C Life" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[<p>This week, 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 about HTML5 Tidy (yes it is back!), A few things about web apps such as storage mechanisms, and a few discussions about DOM properties. CSS has been discussing a few things including the issue of vendor extensions. And more bite sized information. Enjoy!</p>

<h3>HTML5</h3>

<p><a href="http://tidy.sourceforge.net/">Tidy</a>, the useful piece of code that was helping you to fix your broken XHTML and HTML had not evolved. Björn Hörhmann <a href="http://lists.w3.org/Archives/Public/www-archive/2011Nov/0007.html">published a patch</a> to fix it. Dominique Hazaël-Massieux (W3C) decided to create a <a href="https://github.com/w3c/tidy-html5">HTML5 tidy github project</a></p>

<h3>Web Apps</h3>

<p>There are many ways of storing information on the Web on the client side. The cookies was one of the first one, but since AppCache and Web Storage have been developed. There is a <a href="http://www.w3.org/2008/webapps/wiki/Database">wiki page on client side database</a> solutions documenting what are the relations between the different technologies.</p>

<p>There is a lot of work going on for enabling a <a href="http://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html">FullScreen API</a>.</p>

<p>I mentioned Web Intents last week. An <a href="http://lists.w3.org/Archives/Public/public-web-intents/2011Nov/0000">introduction about Web Intents</a> has been  written by the priceless timeless.</p>

<h3>DOM</h3>

<p>There is a proposal for a new <code>findAll</code> property. Jonas Sicking (Mozilla) is asking <a href="http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/thread.html#msg808">what <code>type</code> <code>findAll</code> should return</a>.</p>

<p>Anne van Kesteren (Opera) had <a href="https://bugs.webkit.org/show_bug.cgi?id=72591">opened a bug on Webkit bug reporting system</a> about the deprecated <code>document.width</code> and  <code>document.height</code> properties. It is fixed! The two properties have been removed from the Webkit source code. He also started a new round of <a href="http://lists.w3.org/Archives/Public/www-dom/2011OctDec/0183">discussions on how to improve the DOM</a></p>

<p>Rafael Weinstein (Chromium Team) is <a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-November/thread.html#33868">proposing to have a fragment of DOM being inactive</a> but inside the page for future use. Dynamic web pages could use them during the user interaction later on. The proposal is a declarative Inert DOM (a <code>&lt;template&gt;</code> element)</p>

<h3>CSS</h3>

<p>Fantasai (Mozilla) is explaining how the <a href="http://fantasai.inkedblade.net/weblog/2011/inside-csswg/">CSS Working Group is working</a>.</p>

<p><code>scoped</code> stylesheets have been introduced to define a mechanism where the stylesheet would apply only in a precise context.  <a href="http://lists.w3.org/Archives/Public/www-style/2011Nov/thread.html#msg422"><code>scoped</code> is more complicated to implement</a> than initially thought.</p>

<h3>Semantic Web</h3>

<p>RDFa is the swiss army knife for injecting rich data into your Web pages. Initially designed for XHTML, the group is in the process of evolving it for HTML. There is a lot of discussion around it on how to make it easy for developers and compatible with the current Web. Sebastian Heath proposed to change a bit the <a href="http://lists.w3.org/Archives/Public/public-rdfa-wg/2011Nov/0141">consumption of RDFa to take into account <code>id</code></a>. Now a Web author needs to declare an <code>about</code> attribute:</p>

<pre><code>&lt;p id="item1" typeof="ex:item" about="#item1"&gt;
   &lt;span property="item_name"&gt;An interesting item (1)&lt;/span&gt;
 &lt;/p&gt;
</code></pre>

<p>His proposal is to reduce it to:</p>

<pre><code>&lt;p id="item1" typeof="ex:item"&gt;
   &lt;span property="rdfs:label"&gt;An interesting item (1)&lt;/span&gt;
 &lt;/p&gt;
</code></pre>

<p>which would produced the triples of information.</p>

<pre><code> &lt;http://example.org/document1#item1&gt; rdf:type &lt;http://example.org/ns/item&gt; .
 &lt;http://example.org/document1#item1&gt; rdfs:label "An interesting item (1)" .
</code></pre>

<h3>Web Architecture</h3>

<h4>Vendor extensions</h4>

<p>There are at a regular pace discussions about vendor extensions in CSS. In my daily job, I have to contact Web sites which have improper use of CSS and makes it hard to have a good Web experience for any users. So I have written a mail to explain why I disliked them: <a href="http://lists.w3.org/Archives/Public/www-archive/2011Nov/0009">CSS vendor extension issues</a>. Henri Sivonen (Mozilla) extended the discussion in a more general discussions on how <a href="http://hsivonen.iki.fi/vendor-prefixes/">Vendor Prefixes Are Hurting the Web</a>. Daniel Glazman (CSS WG co-chair) doesn&rsquo;t completely agree, or maybe he does, for certain parts and decided to write an <a href="http://www.glazman.org/weblog/dotclear/index.php?post/2011/11/16/CSS-vendor-prefixes-an-answer-to-Henri-Sivonen">answer to Henri Sivonen</a>, which triggered another supportive post by Alex Russel (Google) on why <a href="http://infrequently.org/2011/11/vendor-prefixes-are-a-rousing-success/">Vendor Prefixes Are A Rousing Success</a>.</p>

<p>Conclusion? The <strong>discussion is going on</strong>.</p>

<h3>SVG</h3>

<p>I had missed that last July, but it seems that there is a &ldquo;new&rdquo; <a href="http://svgmagazine.com/">quaterly publication about SVG</a>. The <a href="http://www.svgmagazine.com/jul2011/">first issue</a> has 3 articles covering DOM Helper, D3.js and sensorial expressions and emotion.</p>

<h3>HTTP</h3>

<p>Henri Sivonen (Mozilla) <a href="http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/0954">landed</a> support for HTML parsing in <code>XMLHttpRequest</code> in Firefox engine (Gecko). He is giving details on how he has implemented it. His implementations create a direct feedback for changing <a href="http://dev.w3.org/2006/webapi/XMLHttpRequest-2/">XMLHttpRequest specification</a>. The same way Julian Reschke has <a href="http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/0955">implemented and tested</a> a part of the specification about <code>content-type</code> rewriting. These are two of the many ways you can help specifications development.</p>

<h3>URIs</h3>

<h3>Tools and Tutorials</h3>

<ul>
<li><a href="http://html5doctor.com/history-api/">Pushing and Popping with the History API</a></li>
<li><a href="http://robert.ocallahan.org/2011/11/latency-of-html5-sounds.html">Latency Of HTML5 <code>&lt;audio&gt;</code> Sounds</a></li>
<li><a href="http://www.iandevlin.com/blog/2011/11/html5/in-defence-of-pubdate">In defence of the <code>pubdate</code> attribute</a>.</li>
</ul>


<p>This week, the theme of <a href="http://annevankesteren.nl/">Anne van Kesteren</a>&rsquo;s <a href="http://blog.whatwg.org/weekly-time-police">report</a> is about <code>&lt;time&gt;</code> and <code>findAll</code>. I feel there is <a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-November/033913.html"><del>fatigue</del> <ins>desire to know if it's useful</ins></a> in Anne&rsquo;s report. He is asking for feedback.</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>]]>
        
    </content>
</entry>

<entry>
    <title>Open Web Platform Weekly Summary - 2011-11-07 - 2011-11-13</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/11/openweb-weekly-19.html" />
    <id>tag:www.w3.org,2011:/QA//1.9259</id>
    
    <published>2011-11-15T14:15:38Z</published>
    <updated>2011-11-15T15:58:45Z</updated>
    
    <summary type="html">This week, the Open Web Platform weekly summary is about hgroup and time elements, lang attribute. There are discussions on starting work on Web Intents and how to create a simpler DOM for documents fragments. Plenty of other things. Enjoy.</summary>
    <author>
        <name>Karl Dubost</name>
        <uri>http://my.opera.com/karlcow/blog/</uri>
    </author>
    
        <category term="HTML" />
    
        <category term="Open Web" />
    
        <category term="W3C Life" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[<p>This week, 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 about <code>hgroup</code> and <code>time</code> elements, <code>lang</code> attribute. There are discussions on starting work on Web Intents and how to create a simpler DOM for documents fragments. Plenty of other things. Enjoy.</p>

<h3>HTML5</h3>

<p>The <code>hgroup</code> element, which was proposed for defining sub headlines, is still being actively discussed. It is not yet clear if it should be replaced by a different element with a simpler content model, by an attribute, just dropped or maintained.</p>

<p>The <code>lang</code> attribute helps authors to specify the language of the content in an HTML page. Some people consider that the <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=14709"><code>lang</code> attribute validation constraints</a> are not sufficient.</p>

<p>Tantek Çelik (Mozilla) is proposing <a href="http://lists.w3.org/Archives/Public/public-html/2011Nov/0117">refinements for the <code>time</code> element</a>, which has just been added again to <a href="http://dev.w3.org/html5/spec/text-level-semantics.html#the-time-element">W3C HTML5 Editor draft</a>.</p>

<h3>Web Apps</h3>

<p>Bryan Sullivan (AT&amp;T) is writing a &ldquo;<a href="http://bkaj.net/w3c/eventsource-push.html">Push API</a>&rdquo; that would use the <a href="http://www.w3.org/TR/eventsource/">Server-Sent Events</a> specification. That becomes handy in situation of low consumption on mobile handsets by offloading management of EventSource connections. The event delivery can be handled by other types of push servers.</p>

<h4>Web Intents</h4>

<p>The WebApps and Device APIs WGs are <a href="http://lists.w3.org/Archives/Public/public-device-apis/2011Nov/0054">joining</a> forces around <strong><a href="http://webintents.org/">Web Intents</a></strong> <a href="http://w3c-test.org/dap/proposals/intents-tf.txt">proposal</a>, the new cool kid in town. The aim is to reinvent a kind of Web RPC. Basically Web applications should be able to register themselves so you can hook them to specific services. For example if you want to trigger a specific Web applications for managing <code>mailto:</code> links.</p>

<ul>
<li>Minutes of Web Apps WG on <a href="http://www.w3.org/2011/10/31-webapps-minutes.html">October 31</a> and <a href="http://www.w3.org/2011/11/01-webapps-minutes.html">November 1</a></li>
<li><a href="http://www.w3.org/TR/2011/WD-webstorage-20111025/">Last Call Working Draft of Web Storage</a> has been published. It is an API for persistent data storage of key-value pair data in Web clients.</li>
</ul>


<h4>AppCache</h4>

<p>AppCache is a technology which was created for enabling the possibility for an application to run offline. After having been deployed for a while, Web developers have noticed a lot of issues in the way it was initially built. A community group has been created for <a href="http://www.w3.org/community/fixing-appcache/">Fixing Application Cache</a>. Join!</p>

<h3>DOM</h3>

<p>Yehuda Katz would like to be able to <a href="http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/0663">take a string of HTML and parse it into a document fragment</a> without knowing the context in advance.</p>

<pre><code>var frag = document.createDocumentFragment();
frag.innerHTML = "&lt;tr&gt;&lt;td&gt;hello&lt;/td&gt;&lt;/tr&gt;"
someTable.appendChild(frag)
</code></pre>

<p>João Eiras (Opera) agrees but proposes <a href="http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/0678">a different code</a>.</p>

<p>Ojan Vafai (Chromium Team) proposed to <a href="http://lists.w3.org/Archives/Public/www-dom/2011OctDec/0011">create new methods for the DOM</a> instead of hacking around the old ones.</p>

<blockquote><p>lets add the following methods to Node:</p>

<p>prepend(nodeish) &ndash; Adds to the start of the node.
append(nodeish) &ndash; Adds to the end of the node.
before(nodeish) &ndash; Adds before the node.
after(nodeish) &ndash; Adds after the node.
replace(nodeish) &ndash; Replaces the node.
remove() &ndash; Removes the node.</p></blockquote>

<p>Anne van Kesteren (Opera) described <a href="http://lists.w3.org/Archives/Public/www-dom/2011OctDec/0140">the new DOM methods and their model</a>. It&rsquo;s not yet stabilized. Read the full thread.</p>

<p>If you remember I talked already a few times about mutation events. The work is still in progress. So much that the initial musings on them has been scraped. The specification contains currently a placeholder on how <a href="http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#mutations">Mutation Events</a> are implemented in Chrome and being implemented in Mozilla but <strong>this is likely to change again</strong>.</p>

<h3>Web Architecture</h3>

<p>The W3C Technical Architecture Group has started a discussion <a href="http://www.w3.org/2001/tag/2011/11/04-minutes">about the experimental Google Protocol SPDY</a> and its interactions with Web Architecture. The latency in HTTP communications is an issue that Web developers and browser implementers are trying to tackle. In an era of applications being on the Web, the hunt to anything slowing down the responsiveness is important. Google worked on a proposal for modifying the way the client and the server communicates. This has strong consequences for the Web architecture, among others caching.</p>

<h3>SVG</h3>

<p>You love moving blocks around? Yes but which syntax in which language? An effort, currently <strong>only an editor draft</strong>, is going on to merge SVG/CSS/2D/3D transforms specifications as a <a href="http://dev.w3.org/csswg/css3-transforms/">unique transform specification</a>.</p>

<h3>HTTP</h3>

<ul>
<li><p><code>X-Forwarded-For:</code> is currently the way that some proxies indicates that the HTTP request they are handling is coming from another IP. A. Petersson, M. Nilsson are writing an <a href="http://tools.ietf.org/html/draft-petersson-forwarded-for">IETF RFC draft for defining <code>Forwarded-For</code> HTTP header</a>. For example,  clients with an ip1 (such as Opera Mini or Amazon Silk) are using a proxy client (with an ip2) for creating the HTTP requests. The proxy will send to the requested server, the following information.</p>

<p>  X-Forwarded-For: ip1</p></li>
</ul>


<h3>URIs</h3>

<p>You know it already: <a href="http://www.w3.org/Provider/Style/URI">Cool URIs do not change</a>. It means that you should be able to maintain your URIs space for a very long time so people can rely on them when interacting on the Web. You could even create a <a href="http://www.w3.org/Consortium/Persistence">URI persistence policy</a> for your company or organization. The W3C and the Digital Curation Centre are organizing a workshop on <a href="http://www.w3.org/2001/tag/doc/idcc_workshop.html">Domain names and persistence</a> on December 8, 2011, in Bristol (UK).</p>

<h2>Tools and Tutorials</h2>

<ul>
<li>Caveman is an <a href="http://nedbatchelder.com/code/caveman/">Appcache manifest validation tool</a> in python (<a href="https://bitbucket.org/ned/caveman">bitbucket</a>)</li>
<li>The <a href="http://www.w3.org/community/webed/">W3C Web Education community group</a> has released its <a href="http://lists.w3.org/Archives/Public/public-webed/2011Nov/0005">plans for the next few weeks</a>.</li>
<li><a href="http://www.w3.org/community/scriptlib/">Script Library Community Group</a> is a forum for improved communication between script library authors and users, and W3C working groups working on relevant specifications.</li>
<li>You do not remember the unicode character code but you know what it looks like? Then there is a tool to <a href="http://www.shapecatcher.com/">convert drawing into character codepoint</a>.</li>
</ul>


<p>This week, the theme of <a href="http://annevankesteren.nl/">Anne Van Kesteren</a>&rsquo;s <a href="http://blog.whatwg.org/weekly-tpac-2011">report</a> is mainly about TPAC 2011.</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>]]>
        
    </content>
</entry>

<entry>
    <title>New release of the RDFa 1.1 Distiller and Validator </title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/11/new_release_of_the_rdfa_11_dis.html" />
    <id>tag:www.w3.org,2011:/QA//1.9258</id>
    
    <published>2011-11-15T12:30:03Z</published>
    <updated>2011-11-15T13:54:11Z</updated>
    
    <summary type="html">Back in May I have already blogged on the release of a new, RDFa 1.1 version of the distiller code. Many things have happened since May, however, with changes in RDFa, introduction of RDFa 1.1 Lite, etc. I have also...</summary>
    <author>
        <name>Ivan Herman</name>
        <uri>http://www.w3.org/People/Ivan</uri>
    </author>
    
        <category term="HTML" />
    
        <category term="Semantic Web" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[<p>Back in May I have already <a href="http://www.w3.org/QA/2011/05/rdfa_11_distiller_and_validato.html">blogged</a> on the release of a new, <a href="http://www.w3.org/2007/08/pyRdfa/Shadow.html">RDFa 1.1 version of the distiller code</a>. Many things have happened since May, however, with changes in RDFa, introduction of <a href="http://www.w3.org/2010/02/rdfa/sources/rdfa-lite/Overview-src.html">RDFa 1.1 Lite</a>, etc. I have also <a href="http://www.w3.org/QA/2011/11/schemaorg_and_rdfa_11_lite_how.html">blogged about those changes</a>, and what they mean for <a href="http://schema.org/">Schema.org</a>, for example, a few days ago. I have followed the changes on the specs with my code for the distiller; I have now updated the <a href="http://www.w3.org/2007/08/pyRdfa/Shadow.html">service</a>. It implements the latest <a href="http://www.w3.org/2010/02/rdfa/sources/rdfa-core/Overview-src.html">editors’ draft of RDFa 1.1 Core</a>. </p><p>As also announced in my blog in May, I have also made an accompanying service called the <a href="http://www.w3.org/2007/08/pyRdfa/Validator">(RDFa) validator</a>. It relies on the same code as the distiller, except that it catches the possible error and warning triples and makes a human-readable version of those. Note that the validator can also be instructed to check <a href="http://www.w3.org/2010/02/rdfa/sources/rdfa-lite/Overview-src.html">RDFa 1.1 Lite</a>, ie, it issues warning if the RDFa content uses RDFa attributes that are not part of RDFa 1.1 Lite.</p><p>The usual caveat applies, of course: this is still a service under development; it may change as the specification of RDFa evolves and, obviously, if contains bugs that I do not know about…</p>]]>
        
    </content>
</entry>

<entry>
    <title>Schema.org and RDFa 1.1 Lite: how does it look now?</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/11/schemaorg_and_rdfa_11_lite_how.html" />
    <id>tag:www.w3.org,2011:/QA//1.9256</id>
    
    <published>2011-11-12T09:12:30Z</published>
    <updated>2011-11-12T09:28:49Z</updated>
    
    <summary type="html"> In his latest blog entry on the Schema.org, Dan Brickley announced that Schema.org would also process RDFa 1.1 Lite as an alternative syntax to encode Schema.org terms. As he emphasized: This work opens up new possibilities also for developers...</summary>
    <author>
        <name>Ivan Herman</name>
        <uri>http://www.w3.org/People/Ivan</uri>
    </author>
    
        <category term="HTML" />
    
        <category term="Semantic Web" />
    
        <category term="Technology" />
    
        <category term="Web Applications" />
    
        <category term="Web Design" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[    <p>In his latest <a href="http://blog.schema.org/2011/11/using-rdfa-11-lite-with-schemaorg.html">blog entry on the Schema.org</a>, Dan Brickley announced that
      Schema.org would also process RDFa 1.1 Lite as an alternative
      syntax to encode Schema.org terms. As he emphasized:</p>
    <blockquote>This work opens up new possibilities also for developers
      who intend to work with schema.org data using RDF-based tools and
      <a href="http://en.wikipedia.org/wiki/Linked_Data">Linked Data</a>,
      and defines a simplified publisher-friendly 'Lite' view of RDFa.</blockquote>
    <p> However, one has to be careful about a detail: the RDFa 1.1
      version that will be processed is <span style="font-style: italic;">not</span>
      the latest <a href="http://www.w3.org/TR/2011/WD-rdfa-core-20110331/">“official” W3C draft</a>; indeed, as a result of feedback’s and technical
      discussion, the next release of RDFa 1.1 will include some
      significant changes. As Dan emphasized in his blog, there are
      still some technical details to finalize before the Working Group
      would publish that new draft, but the changed version is already
      available as an <a href="http://www.w3.org/2010/02/rdfa/sources/rdfa-core/Overview-src.html">editors’ draft</a>. The most important new feature, as far as the
      Schema.org examples also go, is the changed behavior of the <code>@property</code>
      attribute: in the overwhelming percentage of RDFa usage, it
      becomes synonymous to <code>@rel</code>. (What essentially
      happens is that, in the presence of, say, an <code>@href</code>
      attribute, the value of that attribute is bound to <code>@property</code>
      instead of a possible literal.)</p>
    <p>The <a href="http://schema.org/docs/datamodel.html">Schema.org
        datamodel</a> page has an early example showing some canonical
      Schema.org use cases in terms of RDFa 1.1. It encodes an earlier
      version of the example given on the <a href="http://schema.org/Product">Schema.org Product</a>. Here is how the same example looks like in the
      new setting, i.e., RDFa 1.1. This example is also in <a href="http://www.w3.org/2010/02/rdfa/sources/rdfa-lite/Overview-src.html">RDFa 1.1 Lite</a>, i.e., the simpler albeit strict subset of RDFa 1.1: </p>
    <pre>&lt;div vocab="http://schema.org/" typeof="Product"&gt;
  &lt;img property="image" src="dell-30in-lcd.jpg" /&gt;
  &lt;span property="name"&gt;Dell UltraSharp 30" LCD Monitor&lt;/span&gt;

  &lt;div property="aggregateRating" typeof="AggregateRating"&gt;
    &lt;span property="ratingValue"&gt;87&lt;/span&gt;
    out of &lt;span property="bestRating"&gt;100&lt;/span&gt;
    based on &lt;span property="ratingCount"&gt;24&lt;/span&gt; user ratings
  &lt;/div&gt;

  &lt;div property="offers" typeof="AggregateOffer"&gt;
	&lt;span property="lowPrice"&gt;$1250&lt;/span&gt;
	to &lt;span property="highPrice"&gt;$1495&lt;/span&gt;
	from &lt;span property="offerCount"&gt;8&lt;/span&gt; sellers
  &lt;/div&gt;

  Sellers:
  &lt;div property="offers" typeof="Offer" &gt;
    &lt;a property="url" href="save-a-lot-monitors.com/dell-30.html"&gt;
     Save A Lot Monitors - $1250&lt;/a&gt;
  &lt;/div&gt;
  
  &lt;div property="offers" typeof="http://schema.org/Offer"&gt;
    &lt;a property="url" href="jondoe-gadgets.com/dell-30.html"&gt;
    Jon Doe's Gadgets - $1350&lt;/a&gt;
  &lt;/div&gt;
  ...
&lt;/div&gt;     </pre>
    <p>This is clearly significantly simpler than the <a href="http://schema.org/docs/datamodel.html">previous version</a>. Indeed, the compelling reasons for the changes in RDFa 1.1 (compared to its previous versions) was to achieve that simplicity. </p>
    <p>If you are interested in some of the technical details… Some of
      the notable differences, compared to the previous versions of RDFa
      1.1 (and also shown on that example) are:</p>
    <ul>
      <li>The behavior of <code>@property</code> has become richer. For
        example, when used on the <code>&lt;img&gt;</code>
        element, it results in a triple with an IRI reference as a
        subject, rather than a literal. This was (and still is!) the
        behavior of <code>@rel</code> but, in this case, <code>@property</code>
        can also be used with a similar result. (That is also the reason why <code>@rel</code> is not used in RDFa 1.1 Lite any more.)</li>
      <li>The combination of <code>@property</code> and <code>@typeof</code>
        has also changed. <code>@typeof</code> generates a new blank
        node (<code></code>it had a similar effect in RDFa 1.0 as well
        as in the earlier versions of RDFa 1.1, although some of the
        details have changed) but, and that is a new
        feature, this blank node is also used as an object for <code>@property</code>
        (again, instead of generating a literal). One could consider
        this combination as a shorthand for an extra <code>@resource</code> or <code>@href</code>
        attribute using a (new) blank node identifier. </li>
      <li>Another feature bound to the combination of <code>@property</code> and <code>@typeof</code>:
        the generated blank node “chains”, i.e., is used as a subject
        for subsequent triples in the sub-tree. This makes a very
        frequent idiom (repeated several times in the example) simpler
        than before. </li>
    </ul>
    <p>For reference, a portion of the generated RDF is as follows:</p>
    <pre>@prefix schema: &lt;http://schema.org&gt; .
[ a schema:Product ;
  schema:image &lt;dell-30in-lcd.jpg&gt; ;
  schema:name "Dell UltraSharp 30" LCD Monitor ;
  schema:aggregateRating [
    a schema:AggregateRating ;
    schema:ratingValue "87" ;
    schema:bestRating "100" ;
    schema:ratingCount "24" 
  ] ;
  schema:offers [
    a schema:AggregateOffer ;
    schema:lowPrice "$1250" ;
    schema:highPrice "$1495" ;
    schema:offerCount "8" 
  ] ;
  schema:offers [
    a schema:Offer ;
    schema:url &lt;save-a-lot-monitors.com/dell-30.html&gt; 
  ] ;
  ...
]
</pre>
]]>
        
    </content>
</entry>

<entry>
    <title>Open Web Platform Weekly Summary - 2011-10-31 - 2011-11-06</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/11/openweb-weekly-18.html" />
    <id>tag:www.w3.org,2011:/QA//1.9251</id>
    
    <published>2011-11-07T21:36:17Z</published>
    <updated>2011-11-07T21:39:13Z</updated>
    
    <summary type="html">Last week, there was the annual W3C TPAC. The HTML Working Group met (day 1, day 2) and many other groups for discussing general issues. I introduced the Open Web Platform weekly summary and asked feedback on how to improve...</summary>
    <author>
        <name>Karl Dubost</name>
        <uri>http://my.opera.com/karlcow/blog/</uri>
    </author>
    
        <category term="HTML" />
    
        <category term="Open Web" />
    
        <category term="W3C Life" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[<p>Last week, there was the annual <a href="http://www.w3.org/2011/11/TPAC/">W3C TPAC</a>. The <a href="http://www.w3.org/html/wg/">HTML Working Group</a> met  (<a href="http://www.w3.org/2011/11/03-html-wg-minutes">day 1</a>, <a href="http://www.w3.org/2011/11/04-html-wg-minutes">day 2</a>) and many other groups for discussing general issues. I introduced 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 and <a href="http://www.w3.org/2011/11/03-html-wg-minutes#item10">asked feedback</a> on how to improve it or if I should drop it. I got mostly positive feedback and I will improve it in the next few weeks.</p>

<p>There are a lot of things to say about the <a href="http://www.w3.org/wiki/TPAC2011">fruitful meetings</a> we had during this week. Maybe another time.</p>

<h3>HTML5</h3>

<p>The <code>time</code> element was dropped from the specification, but the community <a href="http://lists.w3.org/Archives/Public/public-html/2011Nov/0011">requested to be restored</a>.</p>

<p>There is yet <a href="http://lists.w3.org/Archives/Public/public-html/2011Oct/thread.html#msg146">another difficult discussion</a> on extensibility and how to handle it properly. Time to time, this topic will happen. This time, it is related to <a href="http://www.w3.org/html/wg/wiki/ChangeProposals/av_param">specifying arbitrary  attributes for Audio-Video</a>.</p>

<p>The <code>hgroup</code> element is not satisfying. Kornel Lesiński is proposing to replace it with the <a href="http://lists.w3.org/Archives/Public/public-html/2011Nov/0042"><code>hsub</code></a> element with a simpler content model.</p>

<p>(<strong>Do not copy that code in your pages</strong>.)</p>

<pre><code>&lt;body&gt;
&lt;h1&gt;Title&lt;/h1&gt;
&lt;hsub&gt;Subtitle&lt;/hsub&gt;

&lt;h1&gt;Second Title&lt;/h1&gt;
&lt;div&gt;
    &lt;hsub&gt;Second Subtitle 1&lt;/hsub&gt;
    &lt;hsub&gt;Second Subtitle 2&lt;/hsub&gt;
&lt;/div&gt;
&lt;/body&gt;

&lt;article&gt;
    &lt;hsub&gt;The Magical&lt;/hsub&gt;
    &lt;h1&gt;Title&lt;/h1&gt;
    &lt;hsub&gt;That Has&lt;/hsub&gt;
    &lt;hsub&gt;Multiple Subtitles&lt;/hsub&gt;
&lt;/article&gt;
</code></pre>

<h3>AppCache</h3>

<p>When <a href="http://www.w3.org/TR/html5/offline.html#offline">developping offline applications</a>, we are using a <code>manifest</code> file containing the file to cache.  There is a proposal to add syntax to the manifest that would to <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=14702">allow always request files when online</a>, but not when offline. There is also a proposal to be less <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=14704">dependent on the URL and have an additional identifier</a> to cope with minted URLs which tries to avoid caching (which IMHO is circular).</p>

<h3>Canvas</h3>

<blockquote><p>one feature Web developers are asking for is the ability to draw DOM objects to an HTML canvas. — Robert O'Callahan, Mozilla — <a href="http://robert.ocallahan.org/2011/11/drawing-dom-content-to-canvas.html">Drawing DOM Content To Canvas</a></p></blockquote>

<h3>DRM</h3>

<p>There is a <a href="http://www.w3.org/2011/11/03-html-wg-minutes#item04">discussion brought to the HTML WG by the WebTV task force</a> to know if there is a possibility to add a mechanism to protect content. There is no resolution yet. On this same topic, an interesting article has been published on the history of the different systems proposed in the past.</p>

<blockquote><p>There are more than a few reasons digital rights management (DRM) has been largely unsuccessful. But the easiest way to explain to a consumer why DRM doesn&rsquo;t work is to put it in terms he understands: &ldquo;What happens to the music you paid for if that company changes its mind?&rdquo; It was one thing when it was a theoretical question. Now it&rsquo;s a historical one. — <a href="http://opensource.com/life/11/11/drm-graveyard-brief-history-digital-rights-management-music">The DRM graveyard: A brief history of digital rights management in music</a></p></blockquote>

<h3>HTTP</h3>

<p>A new draft has been published by James Snell for <a href="http://www.ietf.org/id/draft-snell-http-prefer-04.txt">Prefer Header for HTTP</a>. The Prefer request-header is used to indicate that particular server behaviors are preferred by the user-agent, but not required for successful completion of the request.</p>

<p>The <a href="http://lists.w3.org/Archives/Public/ietf-http-wg/2011OctDec/0152.html">version 17 of HTTPbis drafts</a> has been published too.</p>

<h3>Last Call Working Drafts</h3>

<ul>
<li><a href="http://www.w3.org/TR/2011/WD-touch-events-20111027/">Touch Events version 1 Last Call Working Draft</a>. Comment deadline is November 17.</li>
<li><a href="http://www.w3.org/TR/2011/WD-webstorage-20111025/">Web Storage Last Call Working Draft</a>. Comment deadline is November 15.</li>
</ul>


<h2>Tools</h2>

<ul>
<li><a href="http://www.andismith.com/blog/2011/11/25-dev-tool-secrets/">25 Secrets of the Browser Developer Tools</a></li>
<li><a href="http://lists.w3.org/Archives/Public/www-archive/2011Nov/0006">patch for HTML5 in Tidy</a></li>
<li><a href="http://rdf-translator.appspot.com/">RDF Translator</a> is a multi-format conversion tool for structured markup.</li>
</ul>


<p>This week, the theme of <a href="http://annevankesteren.nl/">Anne Van Kesteren</a>&rsquo;s <a href="http://blog.whatwg.org/weekly-time-data">report</a> is mainly about <code>&lt;time&gt;</code> and <code>&lt;data&gt;</code>.</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>]]>
        
    </content>
</entry>

<entry>
    <title>Serving XHTML with math: a recipe for Apache</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/10/serving_xhtml_with_math_a_reci.html" />
    <id>tag:www.w3.org,2011:/QA//1.9187</id>
    
    <published>2011-10-19T10:35:20Z</published>
    <updated>2011-10-21T09:38:13Z</updated>
    
    <summary type="html">The future version 5 of HTML will allow math in a Web page, but the current version 4 does not. You can use XHTML instead, but not all Web clients understand it. Here is a recipe for the Apache Web server to make it return XHTML as HTML to such clients. That HTML will be invalid, of course, because it contains math, but the non-math parts are still handled. It&apos;s not as good a solution as having two versions of a page, but it&apos;s cheap.</summary>
    <author>
        <name>Bert Bos</name>
        <uri>http://www.w3.org/People/Bos/</uri>
    </author>
    
        <category term="HTML" />
    
        <category term="HTTP" />
    
        <category term="Tutorials" />
    
        <category term="Web Design" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[<p>It is slowly becoming easier to include mathematics in Web pages. Ten years ago, the only way was still to write in <a href="http://www.latex-project.org/">LaTeX</a> and apply <a href="http://www.ctan.org/pkg/latex2html" title="LaTeX2HTML">some software</a> that turned the result into HTML with images of math. Later, some plug-ins and JavaScript-based tricks helped a bit, but now several browsers and other HTML viewers have started to understand <a href="/Math/">MathML</a> directly. Especially if you limit yourself to the subset of MathML called the <a href="/TR/mathml-for-css/">“MathML for CSS Profile,”</a> it works quite nicely. And with MathML-compatible mark-up an integral part of the next (fifth) version of <a href="/html/">HTML,</a> that is only going to improve.</p><p>W3C's Math working group maintains a page with information about the various <a href="/Math/Documents/putting">ways to put math on the Web</a> and this article is only about one aspect: configuring an <a href="http://httpd.apache.org/">Apache server</a> to serve XHTML. That won't help people with older user agents to see the math, but it is necessary for newer software.</p><p>Until HTML version 5 is ready, the only way to put math in HTML is to use XHTML instead. But not all user agents accept XHTML. Which gives us at least three choices: offer them the XHTML file anyway (they might not be able to do anything more with it than save it to disk), give them an alternative without math instead (the best solution, but it requires writing a second file), or give them the same file and pretend it is HTML. That last solution isn't very nice: we're serving invalid HTML to those clients. But the XHTML specification has some <a href="/TR/2002/REC-xhtml1-20020801/#guidelines" title="HTML Compatibility Guidelines">guidelines for how to limit the damage</a> with a reasonable chance that the result is readable. The math won't show correctly, but everything else probably will. So that is the solution we assume in this article.</p><p>Aside: Some browsers don't distinguish HTML and XHTML. They assume that an author who used a &lt;math&gt; tag in HTML just forgot to use XHTML (or is trying to use HTML5 already). But Opera (the current version is 11) is an example of a browser that does not do that. It only treats a document as XHTML if you say that it <em>is</em> XHTML. Which is probably the better approach. At least it complies with the standards.</p><p>User agents send a so-called <a href="http://tools.ietf.org/html/rfc2616#section-14.1"">Accept header</a> in each request to a Web server with the list of formats they understand. Each format is identified by its <a href="http://www.iana.org/assignments/media-types/index.html">Internet Media Type.</a> The list typically includes things like PNG (“image/png”), JPEG (“image/jpeg”) and, of course, HTML (“text/html”). User Agents often also indicate which formats they prefer over others, but we'll ignore that here, for simplicity. Specifically, we'll check the list for XHTML (“application/xhtml+xml”).</p><p>Microsoft's Internet Explorer version&nbsp;8 is an example of a client that does not accept XHTML, unless the browser has been extended with a plug-in that handles such files, such as <a href="http://www.dessci.com/en/products/mathplayer/">MathPlayer.</a></p><p>To summarize: If a request to our Web server indicates that the client accepts XHTML, we'll respond with our XHTML file and label it correctly, i.e., as application/xhtml+xml; if not, we'll send the XHTML file anyway, but tell the client that it is HTML, i.e., text/html.</p><p>Different Web servers have different ways to make that happen. Here is a recipe for the <a href="http://httpd.apache.org/">Apache</a> server. It relies on Apache's mod_rewrite module. That is an optional module, so make sure that it is enabled. (It usually is.)</p><p>We're assuming that our XHTML files have names that end in the extension “.xhtml”. If the extension is different, you'll have to modify the first and third lines in the code below.</p><p>In the same directory as those files, we create a file called “.htaccess” with the following content. (If the file already exist, you'll have to find some way to integrate these lines with what is already there. You may need to read the Apache documentation…)</p><pre>
AddType application/xhtml+xml .xhtml
RewriteEngine on
RewriteCond %{REQUEST_FILENAME} \.xhtml$
RewriteCond %{HTTP_ACCEPT} !application/xhtml\+xml
RewriteRule .* - [type=text/html]
</pre><p>It may be necessary to add a <a href="http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html#rewritebase">RewriteBase</a> directive as well, depending on how the Web server is set up. If in doubt, add</p><pre>RewriteBase /path/to/my/files</pre><p>where “/path/to/my/files” is the part of the URL after the name of the server and before the actual file name. (With a slash at the start and not at the end.)</p><p>The first line above tells the Apache server that all files ending in “.xhtml” are XHTML files. The other lines define the exception: when the name of the file that was requested ends in “.xhtml” and the client does <em>not</em> accept “application/xhtml+xml”, we return the file with a media type of “text/html” instead. Note that the “!” on the fourth lines means “not.”</p><p>For an example of this recipe in action, try the <a href="/standards/webdesign/math">Math on the Web</a> page. With most recent browsers, the three examples in the middle of the page will show up as actual mathematical formulas. User agents that do not understand the math will show just a string of letters there, but should still show the rest of the page correctly. If your browser offers something like a “View document information” or “Page information” menu, you can check what type the document has: text/html or application/xhtml+xml.</p><p>For a page such as this one, where the correct display of the formulas is desired, but not essential, this is good enough.</p><hr /><p>And if the degraded display of the math is <em>not</em> good enough? Then you will have to do the extra work and write an HTML version with the math replaced by something else: images (such as made with the already mentioned <a href="http://www.ctan.org/pkg/latex2html">LaTeX2HTML</a>), some JavaScript to simulate math with HTML (such as <a href="/Math/MJ/Overview.html">MathJax</a>), or a textual description of the formulas. The choice depends on the Web clients you want the HTML to be used by.</p><p>No need for the “Rewrite…” rules in that case. Just give the XHTML version the file extension “.xhtml” and the HTML one “.html” and let Apache do the rest. </p><p> </p>]]>
        
    </content>
</entry>

<entry>
    <title>HTML Slidy on smart phones and tablets</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/10/html_slidy_on_smart_phones_and.html" />
    <id>tag:www.w3.org,2011:/QA//1.9227</id>
    
    <published>2011-10-08T18:59:52Z</published>
    <updated>2011-10-08T19:14:32Z</updated>
    
    <summary type="html">Slidy is a free web application for slide presentations, and makes use of a simple HTML microformat for slides. Until recently, Slidy was difficult or impossible to use on keyboard-less touch screen devices like the iPhone or Android phones. I...</summary>
    <author>
        <name>Dave Raggett</name>
        
    </author>
    
        <category term="HTML" />
    
        <category term="Usability" />
    
        <category term="Web Applications" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[<p><a href="http://www.w3.org/Talks/Tools/Slidy2/">Slidy</a> is a free web application for slide presentations, and makes use of a simple HTML microformat for slides. Until recently, Slidy was difficult or impossible to use on keyboard-less touch screen devices like the iPhone or Android phones. I am pleased to announce that Slidy can now be used on these devices with touch gestures:</p>

<ul>
<li>swipe right to go to next page or reveal next item</li>
<li>swipe left to do the reverse</li>
<li>swipe up or down to show/hide the table of contents</li>
</ul>

<p>You have to swipe reasonably quickly. If you want to scroll the viewport, drag your finger slowly across the screen in the direction you want to scroll. Of course, this all depends on how much content people cram into their slides. You should be able to use the native pinch/stretch gestures to change the zoom factor. There is further work to do, e.g. on device detection and on expanding the size of the table of contents. However, I very much look forward to your feedback and suggestions for improvements.
]]>
        
    </content>
</entry>

<entry>
    <title>Impressions on the Schema.org Workshop</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/09/impressions_on_the_schemaorg_w.html" />
    <id>tag:www.w3.org,2011:/QA//1.9220</id>
    
    <published>2011-09-30T06:06:22Z</published>
    <updated>2011-09-30T06:54:36Z</updated>
    
    <summary type="html"> (This blog should have gone out about a week ago. By an unlucky clashes in my agenda, the trip to Mountain View was immediately followed by another trip, which made it difficult to publish this in a really timely...</summary>
    <author>
        <name>Ivan Herman</name>
        <uri>http://www.w3.org/People/Ivan</uri>
    </author>
    
        <category term="HTML" />
    
        <category term="Meetings" />
    
        <category term="Semantic Web" />
    
        <category term="Web Applications" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[    <p>(This blog should have gone out about a week ago. By an unlucky
      clashes in my agenda, the trip to Mountain View was immediately
      followed by another trip, which made it difficult to publish this
      in a really timely manner…)
    </p>
    <p>Structured data is picking up in the search world. The example
      that took the headlines in the blogosphere (and beyond) this
      summer: schema.org, jointly initiated by Google, Microsoft, and
      Yahoo! On 21 September, the three initiators of schema.org
      co-organized a workshop held on the Microsoft Campus in Mountain
      View.</p>
    <p>Since the original announcement of schema.org in June this year
      there has been quite a lot of discussions on the blogosphere and
      elsewhere on the role, importance, and the future of the
      initiative. There were also lots of miscommunications on all
      sides, which is rarely helpful. It is important to find the common
      ground in a community, which, after all, has the general goal of
      helping the evolution of structured data on the Web. Clearly, the
      search engines have a major role to play here. The workshop—which
      gathered around 70-80 people all across the community, including
      producers of structured data, experts in the field, and
      representatives from search engines like <a href="http://ir.baidu.com/phoenix.zhtml?c=188488&amp;p=irol-homeprofile"
        checked="true">Baidu</a> or <a href="http://about.yandex.com/">Yandex</a>
      which don't
      (yet?)  participate in schema.org—was therefore an important step
      toward building broader buy-in and, eventually, consensus. </p>
    <p>The event schedule included <a href="http://schemaorg.cloudapp.net/2011Workshop/">presentations</a>, break-out groups on
      specific technical issues, and a panel. The technical topics
      focused on two issues: the structure and the role of the
      schema.org vocabulary, and the syntax to express those in HTML.</p>
    <p><span style="font-weight: bold;">Vocabularies</span>. Schema.org,
      as it stands today, provides a fairly detailed, but high level
      vocabulary on specific subjects that can be used in an HTML page.
      Mark-up in that vocabulary can be consumed directly by a dedicated
      application (like indeed the search engines), or it can be
      integrated with other data, e.g., by converting the structured
      data into RDF and using the usual data integration approaches
      provided by Semantic Web techniques. (Note that schema.org has
      published, quite some time ago, an <a href="http://www.schema.org/docs/schemaorg.owl">OWL
        version of the vocabulary</a>). The main issue for the future,
      however, is how this vocabulary will evolve, and how it will
      relate to other vocabularies on the Web, and how schema.org will
      relate to other efforts to develop such vocabularies.</p>
    <p>At present, the schema.org vocabulary can readily be used in an
      HTML content mixed with other terms and classes as long as those
      are identified using full URIs of those (the details depend on the
      exact syntax). In particular, HTML page using a mix of schema.org
      and any other terms is accepted by the search engines. The
      presence of non-schema.org classes or properties does not have any
      negative side effects. Although this might sound obvious now, it
      was one of the issues that weren't clear when schema.org was
      initially announced; this led some to believe that such HTML
      content would be rejected as invalid. The opposite is the case. At
      the workshop, Martin Hepp <a href="http://schemaorg.cloudapp.net/2011Workshop/sw1109_Vocabulary_GoodRelations.pdf">presented</a>
      practical examples of how schema.org vocabularies can be mixed
      with outside vocabularies in the case of the <a href="http://purl.org/goodrelations/v1">GoodRelations</a>
      ontology. </p>
    <p>Schema.org also provides an <a href="http://www.schema.org/docs/extension.html">extension
        mechanism</a> within its own vocabulary. Existing schema.org
      URI-s can be extended using a "/" character concatenated with
      other user-defined strings. While simple, this mechanism raises a
      number of questions that were discussed at the workshop. For
      example, how would one find out what that specific new term means
      (the new URI cannot be dereferenced, as these are still on the
      schema.org domain)? How would term equivalences be secured? As one
      of the presenters put it, the current extension mechanism is
      hardly more than a specialized tagging syntax and we all know the
      issues around similar but non-identical tags on sites like
      Delicious or Flickr. One interesting approach that surfaced during
      the discussion, was that search engines will have crawl data
      available on these “tags” and, maybe, by publishing those data,
      some of the widely used extensions may converge into something
      more stable. Some sort of a crowd-sourced term definition
      mechanism. The future will tell whether this is a viable option,
      but it certainly is an interesting direction. </p>
    <p>In some cases the schema.org initiative might choose to adopt
      vocabularies developed by other communities, and include them into
      into the “official” schema.org vocabulary hierarchy. Evan Sandhaus
      and Andreas Gebhard <a href="http://data.nytimes.com/ppt/schema.pdf">told
        us</a> about the process that is expected to lead to the
      adoption of the <a href="http://dev.iptc.org/rNews">rNews</a>
      vocabulary by schema.org. (This was <a href="http://www.iptc.org/site/Home/Media_Releases/schema.org_adopts_IPTC%27s_rNews_for_news_markup">officially
        announced</a> by IPTC since.) The journey to achieve that was
      interesting and did raise some questions, too. For example,
      vocabularies are not just simply included; instead, each and every
      term had to be discussed with the schema.org owners, possibly
      leading to some changes and even exclusions. Issues resulting from
      this include general process, public accountability, etc., and
      still need to be clarified and possibly developed further.
      Additionally, there are questions around the exact names, the URIs
      used to identify terms: will there be a term in the rNews name
      space (i.e., <code>http://www.iptc.org/ns/1.0/</code>) and a
      sibling with a similar role in the <code>schema.org</code> name
      space? Will the vocabulary owner publish a separate vocabulary
      files containing, for example, <code>owl:equivalentProperty</code>
      statements for those terms? While this might not be a problem for
      the relatively new rNews (they may decide to simply adopt <code>schema.org</code>
      URIs), it is likely to become an issue for more established
      vocabularies.</p>
    <p>In general, there was an agreement in the room that extensibility
      of vocabularies is important, and that more work is needed beyond
      the . While the schema.org vocabulary will play a hugely important
      role in future, it cannot (and, as the schema.org partners
      emphasized, does not intend to!) cover all areas of structured
      data. As <a href="http://www.w3.org/QA/2011/09/proposing_two_new_sw_interest.html">announced
        earlier</a>, the new <a href="http://www.w3.org/2001/sw/interest/webschema.html">W3C
        SWIG Task Force on Web Schemas</a> (led by R.V. Guha, from
      Google) will become the main discussion forum to discuss those
      questions.</p>
    <p><span style="font-weight: bold;">Syntax</span>. The other major
      thread of discussion in the past few months was the syntax to be
      used to include structured data in conjunction with schema.org.
      Should it be only <a href="http://dev.w3.org/html5/md/">microdata</a>
      (as suggested by the schema.org site)? Should it also be based on
      <a href="http://microformats.org/">microformats</a> or on <a href="http://www.w3.org/TR/rdfa-core/">RDFa</a>?
      All of the above?</p>
    <p>In a separate break-out discussion Ben Adida made a <a href="http://ben.adida.net/presentations/rdfa-2011-09-21/#1">presentation</a>
      on <a href="http://www.w3.org/TR/rdfa-core/">RDFa 1.1</a>,
      showing how this upcoming version of RDFa provides a level of
      simplicity that may make it suitable for the purposes of
      schema.org, too. The discussion that followed, beyond some
      technical issues (e.g., whether RDFa should retain the duality of
      using <code>@rel</code> and <code>@property</code> attributes),
      concentrated on the more general question whether search engines
      should accept multiple syntaxes or whether there should be only
      one. After some discussions it was felt that by <span style="font-style: italic;">not</span>
      allowing multiple syntaxes a number of long tail applications
      could be excluded. Indeed, some applications may need more complex
      expressions than what microdata provides today, but those
      applications may also want to use schema.org vocabularies for
      consumption by search engines. The consensus in the room was that
      multiple syntaxes ought to be accepted, although it was also
      necessary to look at some technical issues around, for example,
      RDFa 1.1 to possibly simplify it and make it (or a subset thereof)
      more suitable for average Web authors. The <a href="http://www.w3.org/wiki/Html-data-tf">W3C
        SWIG Task Force on HTML Data</a>, led by Jeni Tennison, will
      play a major role in fleshing out those technical issues. Although
      there was no clear commitment (yet?) from the search engines that
      RDFa <span style="font-style: italic;">would</span> be accepted
      alongside microdata, the feeling was that there is indeed a high
      probability that this may happen at some point. The syntax
      sessions felt like an important break-through after what had been
      a period of contentious discussions. </p>
    <p>All in all, it was good day, which may be remembered in future as
      an important milestone in the evolution of Structured Data on Web
      sites, and, as a consequence, in the future of the Semantic Web.
      Thanks to all the organizers, and also to RV Guha, Jeni Tennison, and
      Dan Brickley for helping to set up the SWIG Task Forces! </p>
]]>
        
    </content>
</entry>

<entry>
    <title>Proposing two new SW Interest Group Task Forces</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/09/proposing_two_new_sw_interest.html" />
    <id>tag:www.w3.org,2011:/QA//1.9207</id>
    
    <published>2011-09-20T03:57:03Z</published>
    <updated>2011-09-20T16:37:26Z</updated>
    
    <summary type="html">One of the exciting events of the past few months was the joint announcement of schema.org from three major search engine providers (Google, Yahoo, and Microsoft). It was a major step in the recognition that structured data, embedded in Web...</summary>
    <author>
        <name>Ivan Herman</name>
        <uri>http://www.w3.org/People/Ivan</uri>
    </author>
    
        <category term="HTML" />
    
        <category term="Semantic Web" />
    
        <category term="Web Applications" />
    
        <category term="Web Design" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[<p>One of the exciting events of the past few months was the joint announcement of <a href="http://www.schema.org">schema.org</a> from three major search engine providers (Google, Yahoo, and Microsoft). It was a major step in the recognition that structured data, embedded in Web pages or otherwise, has a huge role to play on the Web. Put another way: structured data on web sites is definitely now mainstream.
</p>

<p>
The role of the schema.org site is twofold. It defines a family of vocabularies that search engines "understand"; although these vocabularies are still evolving, they reflect the areas that search engines consider as most important for average Web pages. Independent of the vocabularies, schema.org also defines the syntax that search engines understand, i.e., how the vocabularies should be embedded in an HTML page. At the moment the emphasis from schema.org is on the usage of <a href="http://dev.w3.org/html5/md/">microdata</a>.</p>

<p>As with all such important events, the announcement of the schema.org site has generated lots of discussion on the blogosphere, on different mailing lists, twitter, and so on. The discussion crystallized around two, technically different set of issues:</p>

<ul>
<li>What is the evolution path of the schema.org vocabularies; how do they relate to vocabulary developments around the world that has already brought us such widely used vocabularies like <a href="http://dublincore.org/documents/dcmi-terms/">Dublin Core</a>, <a href="http://www.heppnetz.de/projects/goodrelations/">GoodRelations</a>, <a href="http://xmlns.com/foaf/spec/">FOAF</a>, <a href="http://www.w3.org/TR/vcard-rdf/">vCard</a>, the different <a href="http://microformats.org/">microformat vocabularies</a>, etc?</li>

<li>
What is the role of <a href="http://www.w3.org/TR/rdfa-core/">RDFa</a> and <a href="http://microformats.org/">microformats</a> for search engines; would search providers also accept RDFa 1.1 or microformats as an alternative encoding of structured data? This also raises the more general issue on how microdata and RDFa relate to one another as W3C specifications, and to microformats, independently of the specific vocabularies.</li>
</ul>

<p>
These issues will be discussed on the upcoming schema.org workshop in Mountain View, CA, on 21 September. They are also within scope of discussion within  <a href="http://www.w3.org/2001/sw/interest/">Semantic Web Interest Group (SWIG)</a>. Accordingly, as a result of a variety of discussions, I am proposing two new SWIG Task Forces to discuss these and flesh out solutions.  Note that this is also related to a <a href="http://lists.w3.org/Archives/Public/public-html/2011Jun/0366.html">TAG request from June</a>.  Assuming the proposals are approved, the two Task Forces will be:
</p>

<ol>
<li>
<a href="http://www.w3.org/2001/sw/interest/webschema.html">Web Schemas Task Force</a>, to be chaired by R.V. Guha (Google), concentrating on general vocabulary-related discussions. The Task Force's focus should be on collaboration around vocabularies, mappings between them, and around syntax-neutral vocabulary design and tooling. Issues like convergence of various vocabulary schemas, use cases, tools and techniques, documentation of mappings and equivalences between schemas, should all be in scope for this Task Force.</li>

<li>
<a href="http://www.w3.org/wiki/Html-data-tf">HTML Data Task Force</a>, to be chaired by Jeni Tennison, should conduct a technical analysis on the relationship between RDFa and microdata and how data expressed in the different formats can be combined by consumers. This Task Force may propose modifications in the form of bug reports and change proposals on the microdata and/or RDFa specifications where they would help users to easily translate between the two syntaxes or use them together. The Task Force should also work on a general approach for the mapping of microdata to RDF, as well as the mapping of RDFa to microdata JSON.</li>
</ol>

<p>Both Task Forces should be public, both in terms of joining the respective mailing lists or following the discussions via the public archives. </p>


<p>Everybody is welcome!</p>
]]>
        
    </content>
</entry>

<entry>
    <title>Open Web Platform Weekly Summary - 2011-08-30 - 2011-09-11</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/09/openweb-weekly-17.html" />
    <id>tag:www.w3.org,2011:/QA//1.9199</id>
    
    <published>2011-09-12T20:22:22Z</published>
    <updated>2011-09-12T20:24:52Z</updated>
    
    <summary type="html">In my tracking of the Open Web Platform for writing the weekly summary, I decided to be a bit more careful on what is happening on the HTML WG bug tracker. A lot of the discussion is happening there too. The biggest issue being the number of useless comments or spam.</summary>
    <author>
        <name>Karl Dubost</name>
        <uri>http://my.opera.com/karlcow/blog/</uri>
    </author>
    
        <category term="HTML" />
    
        <category term="Open Web" />
    
        <category term="W3C Life" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[<p>In my tracking of the <a href="http://www.w3.org/wiki/Open_Web_Platform">Open Web Platform</a> for writing the <a href="http://www.w3.org/QA/archive/open_web/">weekly</a> summary, I decided to be a bit more careful on what is happening on the <a href="http://www.w3.org/Bugs/Public/describecomponents.cgi?product=HTML%20WG">HTML WG bug tracker</a>. A lot of the discussion is happening there too. The biggest issue being the number of useless comments or spam. </p>

<h3 id="internationalizationi18n">Internationalization (I18N)</h3>

<p>The I18N Core Working Group has raised an <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13398">issue</a> about the HTML5 <a href="http://www.w3.org/TR/html5/text-level-semantics.html#the-q-element">definition of quotes property</a>. The default property should be defined by the language of the text and not by the locale of the browsers.</p>

<h3 id="webarchitecture">Web Architecture</h3>

<p>Tim Berners-Lee explains the architectural decision on <a href="http://lists.w3.org/Archives/Public/www-tag/2011Sep/0006">why fragment identifiers are not sent to the server</a> when they are deferenced.</p>

<h3 id="accessibilitya11y">Accessibility (A11y)</h3>

<p>Laura Carlson  <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13960">proposed</a> to change example on how the <code>article</code> element is used. In HTML5 examples, the article element contains <code>heading</code> and <code>nav</code> elements. She is proposing to reserve the article for pure content in a way which enable screen readers to jump directly to the content avoiding navigation elements. </p>

<h3 id="htmlmarkup">HTML Markup</h3>

<p>Shaun Moss wants to <a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-September/thread.html#33083">propose a <code>comment</code> element for blog posts</a>. A long discussion started.</p>

<h3 id="layout">Layout</h3>

<p>Eric Muller (Adobe) <a href="http://lists.w3.org/Archives/Public/www-style/2011Aug/0655">has sent</a> to the Unicode Consortium a <a href="http://lists.w3.org/Archives/Public/www-style/2011Aug/att-0655/11327-vertical.html">proposal</a> to develop a Unicode property and algorithm to support Japanese layout. Japanese can be <a href="http://www.w3.org/TR/jlreq/">written horizontally or vertically</a> and it is important to be able to determine the orientation of the characters in vertical lines.</p>

<p>HTML5 Forms have client side validation with error messages. The tooltip is browser dependant and varies widely in style. Peter Gasston is <a href="http://lists.w3.org/Archives/Public/www-style/2011Aug/0670">proposing</a> to add new properties for <a href="http://www.broken-links.com/2011/03/28/html5-form-validation/">styling these form validation messages</a>.  </p>

<p>Peter Lins (HP) announced the new <a href="http://test.csswg.org/shepherd/">CSS Test Suite Management System</a>.</p>

<h3 id="dom">DOM</h3>

<p>Aryeh Gregor (Google) <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13974">would like to extend</a> the selection property in the <a href="http://dvcs.w3.org/hg/domcore/raw-file/tip/dom-core.html">DOM</a> for allowing more than one creating the possibility of buffering, manipulating, deleting them. He also proposed to <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13975">remove the multiple ranges selection</a>. This property allows to select a piece of text in a Web page and then holding the command key to select another part of the text without having to do two operations. Only Firefox currently implements this feature.</p>

<p>Ryosuke Niwa (Google) <a href="http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/1121">needs</a> events that <a href="http://ehsanakhgari.org/blog/2011-08-31/future-editing-web">fire before/after user editing action</a> and execCommand take place. He proposed the name <code>beforeEditAction</code> and <code>afterEditAction</code>.</p>

<p>Dominic Cooney (Google, Chromium) wants a way to <a href="http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/1139">register new elements not necessary described in the specification</a>. For example, it could work doing something ala </p>

<pre><code>HTMLElement.register('x-contacts', ContactPicker);
</code></pre>

<blockquote>
  <p>The first argument is an element name. The second is a constructor
function, whose prototype property points to an object which
introduces the API for contacts (eg a refresh method) and is wired up
to HTMLElement.prototype.</p>
</blockquote>

<p>Anne van Kesteren (Opera) notes that its the <a href="http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/1142">backdoor to introduce proprietary markup</a> on the Web. The fallback behavior in absence of scripting is another issue. The discussion is still going on.</p>

<p>Anne van Kesteren (Opera) has removed the entity references from DOM Core (DOM4) and <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13980">then it modifies</a> the HTML5 specification. Entity references were enabling the creation of markup constructs in the doctype. It introduces a lot of complexities in the management of DOM Nodes. </p>

<p>Kentaro Hara (Google) has requested <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13991"><code>HashChangeEvent</code> constructor</a> to make all events constructable as well a <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13993"><code>PageTransitionEvent</code> constructor</a>. It has been <a href="http://html5.org/tools/web-apps-tracker?from=6550&amp;to=6551">integrated right away in HTML5</a> specification. </p>

<p>Boris Zbarsky (Mozilla) notes that Gecko, WebKit and Presto have three different <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=14037">implementations of <code>window.XMLDocument</code></a>.  There are discussions going on how it should be properly specced still taking into account the differences of implementations across browsers and the interoperability issues on legacy code.</p>

<h3 id="graphicscanvaswebgl">Graphics (Canvas, WebGL, …)</h3>

<p>Charles Pritchard (Jumis) needs a <code>baseline</code> property on the <a href="http://www.w3.org/TR/2dcontext/#textmetrics"><code>TextMetrics</code></a> object from <a href="http://dev.w3.org/html5/2dcontext/Overview.html">Canvas 2d</a>. <q>The baseline corresponds to the vertical offset of the anchor point</q>.</p>

<pre><code>var t = ctx.measureText('text span');
t == { width: int, baseline: int };
</code></pre>

<p>David Geary proposes the <a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-August/033052.html">creation of two new methods in canvas 2D: Path</a> <code>getPath()</code>, which would return a path object representing the context’s current path, and <code>setPath(Path)</code>, which would set the current path. That would make it easier to drag objects on a path.</p>

<h3 id="performances">Performances</h3>

<p>Three Last Call Working Draft documents, <a href="http://www.w3.org/TR/2011/WD-performance-timeline-20110901/">Performance Timeline</a>, <a href="http://www.w3.org/TR/2011/WD-user-timing-20110901/">User Timing</a>, <a href="http://www.w3.org/TR/2011/WD-resource-timing-20110811/">Resource Timing</a>, have been published. The deadline of comments on the first two documents is September 22 and Resource Timing is September 15.</p>

<h3 id="protocolhttpxhr2">Protocol (HTTP, XHR2, …)</h3>

<p>To avoid having to rebuild mime messages from scratch, Charles Pritchard (Jumis) would like to <a href="http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/1127">extend <code>FormData</code> object</a>. He is taking example in the <a href="http://code.google.com/apis/picasaweb/docs/2.0/developers_guide_protocol.html#PostPhotos">Picasa developer guide on posting photos</a> and a code <a href="http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/1143">example</a>:</p>

<pre><code>var callback = function(blob) { xhr.send(blob); };
formData.toBlob(callback, 'multipart/form-data');
</code></pre>

<p>Julian Reschke () has rewritten the HTTPbis Working Draft to add information about the <a href="http://lists.w3.org/Archives/Public/ietf-http-wg/2011JulSep/0443">history of HTTP Redirection (3xx)</a> </p>

<p>Joel Martin wanted to be able to <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13984">detect if the connection allows for binary data transmission</a> in Websockets. Simon Pieters (Opera) proposed to use the already existing <code>binaryType</code>. </p>

<pre><code>var binarySupported = typeof WebSocket.prototype.binaryType != 'undefined';
</code></pre>

<p>It seems that <a href="https://bugs.webkit.org/show_bug.cgi?id=67335">chrome implementation is incomplete</a> creating interoperability issues. It might be fixed in future versions.</p>

<h3 id="misc">Misc</h3>

<p>This week, the theme of <a href="http://annevankesteren.nl/">Anne Van Kesteren</a>&#8217;s <a href="http://blog.whatwg.org/weekly-end-of-last-call">report</a> is Parsing APIs.</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 &amp; Tools</a> at <a href="http://www.opera.com/">Opera Software</a>.</p>
]]>
        
    </content>
</entry>

<entry>
    <title>Open Web Platform Monthly Summary - 2011-07-29 - 2011-08-29</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/08/openweb-weekly-16.html" />
    <id>tag:www.w3.org,2011:/QA//1.9186</id>
    
    <published>2011-08-30T20:17:10Z</published>
    <updated>2011-09-12T15:32:32Z</updated>
    
    <summary type="html"> I have decided to change a bit the style of weekly summary of the Open Web Platform. Instead of just going through the list of mails, I will try to focus on more specific things and give more context...</summary>
    <author>
        <name>Karl Dubost</name>
        <uri>http://my.opera.com/karlcow/blog/</uri>
    </author>
    
        <category term="HTML" />
    
        <category term="Open Web" />
    
        <category term="W3C Life" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[
<p>I have decided to change a bit the style of  <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>. Instead of just going through the list of mails, I will try to focus on more specific things and give more context about them. <a href="http://annevankesteren.nl/">Anne Van Kesteren</a> published his <a href="http://blog.whatwg.org/weekly-undomanager">report</a> on August 24.</p>


<ul>
<li><p>&#8220;How to organize a W3C Specification&#8221; is a <a href="http://www.w3.org/mid/4E43C13B.4010706@gmail.com">common question</a> at W3C. This time it started about the DOM specifications. The argument falls both on side of the consistency, work style, and technology design. There is no ultimate and definitive answer. In my opinion, you need to choose the format that will maximize participation for your context. The <a href="http://www.w3.org/TR/qaframe-spec/">specification organization</a> might be also influenced by the way you want to <a href="http://www.w3.org/TR/spec-variability/">design the technology</a>.</p><li>
<li><p>A new group for the <a href="http://www.w3.org/community/webed/">Web Education/Evangelization community</a> has been opened. Chris Mills is the co-chair of the group with Doug Scheppers. People on the <a href="http://lists.w3.org/Archives/Public/public-webed/">mailing-list</a> have started to introduce themselves. Join! It is free.</p><li>
<li><p>A while ago, I have talked about the Shadow DOM. The <a href="http://www.w3.org/mid/CADh5Ky04=OEjoQ48FR+Xtcq5_936NmT=acJs9QGVVN891bkS5g@mail.gmail.com">discussion evolved</a> led by Dimitri Glazkov (Google) and Dominic Cooney (Google) into the <a href="http://wiki.whatwg.org/wiki/Component_Model">Component Model</a>, a way to introduce support for creating custom DOM elements enabling layout managers or author UI elements included in the page, but not really part of the page. It inherits from the work done on XBL, XBL2 and MS HTML components, but will be more modular. See also <a href="http://www.w3.org/mid/CADh5Ky0Zd8MSOpf9CzvbBTWpArQEjNDDVwcN8_WL+ka5MvdjTw@mail.gmail.com">Component Model Update</a> mail and also <a href="http://www.w3.org/mid/CAHnmYQ_y4kPW64HPh4RFKmf7cCc-9+XvDprCqMDOeRofC6adaw@mail.gmail.com">this one</a>. </p><li>
<li><p>Your days of DukeNukem are not over. There is a proposal floating for a <a href="https://wiki.mozilla.org/JoystickAPI">Joystick API</a>. With the rise of HTML5 games popularity, there is a growing interest for this proposal.</p><li>
<li><p><a href="http://www.w3.org/wiki/DOM/domcore/nagivator.registerProtocolHandler">registerProtocolHandler</a> gives the possibility to Web sites to <a href="http://updates.html5rocks.com/2011/06/Registering-a-custom-protocol-handler">become handlers for specific protocols</a>. It is currently implemented in Chrome 13. There was a proposal on the list to <a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-August/032738.html">extend the protocol</a>. </p><li>
<li><p>Would it be nice to be able to define how to proceed with undo/redo features but inside the browser? Ryosuke Niwa (Google) has <a href="https://rniwa.com/editing/undomanager.html">proposed a specification</a> along <a href="https://rniwa.com/editing/undomanager-usecases.html">use cases</a>. Ian Hickson decided to <a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-August/032987.html">remove the old UndoManager</a> so that people could focus on Ryosuke Niwa&#8217;s proposal.</p><li>
<li><p><a href="http://www.w3.org/mid/BANLkTinV0oMZ1yE4ctVx5ZYsZgjZfZLEzgb8eFWETHBQ4VKmow@mail.gmail.com">MouseLock</a> is a proposed API to give the possibility to block the mouse in some circumstances. Vincent Scheib (Google) covered some of the issues <a href="http://www.w3.org/mid/CAK-EfXn_9xCBXJcW4TE_1r==wqR-T1jOkJgwkcuM+rcM5AnNFA@mail.gmail.com">identified</a> with the proposal.</p><li>
<li><p>Digital images contains a lot of hidden metadata such as date, focal length, etc. These are contained in the <a href="http://en.wikipedia.org/wiki/Exif">EXIF</a> part of the image. Some camera includes the orientation of the image when taken. Tab Atkins (Google) is proposing to <a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-August/032988.html">add a <code>naturalOrientation</code> property to the <code>img</code> element</a> so it could be used in-browser photo-editing tools.</p><li>
<li><p><strong>Be careful</strong> with the <a href="http://www.w3.org/TR/css3-flexbox/">CSS Flexbox</a> (a feature giving you the possibility to reorder the boxes in CSS). This is one of the CSS module which has been quickly implemented by some browsers vendors. Too quickly? Web developers have started to use it and there is already some legacy code online. Why legacy? Flexbox is going through major revisions with backward incompatible changes. Tab Atkins (Google) is working right <a href="http://www.w3.org/mid/CAAWBYDB8_XvrYKOrGU+mXB2BW9EpivT86JAPUGmO4hhn6cXBcg@mail.gmail.com">now on the layout algorithm</a>.</p><li>
<li><p>The Web is evolving from a Web of documents to a Web of applications. This creates new constraints and usages to the system. HTML5 created <code>history.pushState()</code> and <code>history.replaceState()</code> for managing the history of a navigation and gives proper and usable URIs. Ashok Malhotra (Oracle) <a href="http://www.w3.org/mid/4E58F166.2050802@oracle.com">published</a> a new version of a <a href="http://www.w3.org/2001/tag/">W3C TAG</a> finding on <a href="http://www.w3.org/2001/tag/doc/IdentifyingApplicationState-20110830.html">Identifying Application State</a>. </p><li>
<li><p>There is a <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13942">request</a> on allowing @autofocus for any elements having @tabindex property in HTML. This would give the possibility to get a frame like behavior for some blocks in the document. When people create non scrollable section in a Web page, it creates a load of secondary issues.</p><li>
<li><p>Channy Yunn has proposed a <a href="http://www.w3.org/community/groups/proposed/">Web Crypto API Community Group</a>. It has not been accepted yet. If you are interested, join the effort. If you need more information about the topic, see <a href="http://html5.creation.net/webcrypto-api/">Web Crypto API</a> and <a href="https://wiki.mozilla.org/Privacy/Features/DOMCryptAPISpec/Latest">DOM Crypto API</a></p><li>
<li><p>Aryeh Gregor (Google) has proposed to extend the DOM for allowing authors to <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13958">specify modifiers for accesskeys</a>. Right now, it is not possible to reassign the modifier which is dependent on the system (for example, the command on macosx and Ctrl on windows).</p><li>
<li><p>When dealing with a document, you might want to change the name of an element in the DOM by another name.  Aryeh Gregor (Google) has <a href="http://aryeh.name/spec/editing/editing.html#set-the-tag-name">defined in the editing specification</a> an algorithm for it. The discussion revived an existing feature called <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#Document3-renameNode">renameNode</a>. The current property is still <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=13971">missing features</a>, but there is a will to include it in DOMCore.</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>]]>
        
    </content>
</entry>

<entry>
    <title>Open Web Platform Weekly Summary - 2011-07-13 - 2011-07-28</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/07/openweb-weekly-15.html" />
    <id>tag:www.w3.org,2011:/QA//1.9162</id>
    
    <published>2011-07-29T19:44:07Z</published>
    <updated>2011-07-29T19:46:35Z</updated>
    
    <summary type="html">The weekly summary of the Open Web Platform is out. A lot of discussion about HTTP. The IETF has been meeting recently in Canada. Anne Van Kesteren covers what I have not in his report.

HTML5 is still in Last Call but the last call is finishing on August 3, 2011</summary>
    <author>
        <name>Karl Dubost</name>
        <uri>http://my.opera.com/karlcow/blog/</uri>
    </author>
    
        <category term="HTML" />
    
        <category term="Open Web" />
    
        <category term="W3C Life" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[<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. A lot of discussion about HTTP. The IETF has been meeting recently in Canada. <a href="http://annevankesteren.nl/">Anne Van Kesteren</a> covers what I have not in his <a href="http://blog.whatwg.org/weekly-end-of-last-call">report</a>.</p>

<p><a href="http://w3.org/html5/">HTML5</a> is still in Last Call but the <strong>last call is finishing on August 3, 2011</strong></p>

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

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

<ul>
<li>Rich Tibbett (Opera) proposed a <a href="http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/0331">Local-Networked Service [Discovery and] Messaging API</a></li>
<li><a href="http://lists.w3.org/Archives/Public/public-html/2011Jul/0286">Thoughts on restricting non-bugzilla-driven spec changes during Last Call</a></li>
<li>Aryeh Gregor published <a href="http://aryeh.name/spec/editing/editing.html">HTML Editing APIs specification</a> which is ready for <a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-July/032630.html">implementers feedback</a></li>
</ul>

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

<ul>
<li>A draft has been published for a <a href="http://www.w3.org/2011/tracking-protection/charter-draft.html">Tracking Protection Working Group Charter</a> and the <a href="http://www.w3.org/2011/07/privacy-ig-charter">Privacy Interest Group Charter</a>. Comments are welcome.</li>
<li><a href="http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/0443">Last Call of Page Visibility API</a>; deadline August 18</li>
<li>Anne van Kesteren <a href="http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/thread.html#msg448">fixed the DOM Core Traversal</a> specification to adjust with the new requirements. </li>
<li>First Public Working Draft for the <a href="http://www.w3.org/TR/from-origin/">From-Origin Header specification</a></li>
</ul>

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

<ul>
<li>Henry S. Thompson reviewed the <a href="http://lists.w3.org/Archives/Public/www-tag/2011Jul/0055">XML parsing and external entities in HTML5</a></li>
<li>The content of the HTML/XML Task Force report is not clear enough for some participants. A <a href="http://lists.w3.org/Archives/Public/public-html-xml/2011Jul/thread.html#msg4">discussion</a> has been started on what should be the output and what are the difficulties.</li>
<li>Geoffrey Sneddon (Opera) asked a lot of question about <a href="http://lists.w3.org/Archives/Public/public-html/2011Jul/thread.html#msg261">Window security policy</a>.</li>
<li>Robert O&#8217;Callahan (Mozilla) gave background on <a href="http://lists.w3.org/Archives/Public/public-html/2011Jul/thread.html#msg248">SVG vs canvas performance</a></li>
<li>What is happening when a browser sends an <code>Accept:</code> HTTP header specifying a language that the server can&#8217;t provide?  Mark Nottingham is proposing to send either a <a href="http://lists.w3.org/Archives/Public/ietf-http-wg/2011JulSep/thread.html#msg113">default format or a 406</a>.</li>
<li><a href="http://lists.w3.org/Archives/Public/ietf-http-wg/2011JulSep/thread.html#msg112">1xx HTTP responses are non-final</a>. How do we clarify HTTP specification about it?</li>
<li>The issue on <a href="http://lists.w3.org/Archives/Public/public-html/2011Jul/thread.html#msg77">tab states</a> will be reopened because there is still no implementable proposal so far.</li>
<li>A thread interesting to read on the <a href="http://lists.w3.org/Archives/Public/public-html/2011Jul/thread.html#msg202">correct and incorrect uses of canvas API</a></li>
<li><a href="http://lists.w3.org/Archives/Public/ietf-http-wg/2011JulSep/thread.html#msg124">How the browsers redirect on non-GET methods</a></li>
<li><a href="http://lists.w3.org/Archives/Public/ietf-http-wg/2011JulSep/thread.html#msg204">Motivate one-year limit for Expires</a></li>
<li>Aryeh Gregor (Google) brought <a href="http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/thread.html#msg476">more use cases</a> to the long never-ending discussion on <a href="http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/thread.html#msg0">mutation events</a>.</li>
<li>Clarification on the <a href="http://lists.w3.org/Archives/Public/ietf-http-wg/2011JulSep/thread.html#msg208">relationship between 401, Authorization and WWW-Authenticate in HTTP</a>.</li>
<li>If you wonder if the browsers have <a href="http://lists.w3.org/Archives/Public/www-dom/2011JulSep/0039">extension over the basic Event object</a>, Anne van Kesteren (Opera) has created a good list.</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>
]]>
        
    </content>
</entry>

<entry>
    <title>Open Web Platform Weekly Summary - 2011-07-06 - 2011-07-12</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/07/openweb-weekly-14.html" />
    <id>tag:www.w3.org,2011:/QA//1.9152</id>
    
    <published>2011-07-14T20:46:19Z</published>
    <updated>2011-07-14T20:49:42Z</updated>
    
    <summary type="html">The weekly summary of the Open Web Platform is out. The big discussions from last week have continued this week. Mutation and Canvas accessibility. Anne Van Kesteren covers what I have not in his report.

HTML5 is still in Last Call.</summary>
    <author>
        <name>Karl Dubost</name>
        <uri>http://my.opera.com/karlcow/blog/</uri>
    </author>
    
        <category term="HTML" />
    
        <category term="Open Web" />
    
        <category term="W3C Life" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[<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. The big discussions from last week have continued this week. Mutation and Canvas accessibility. <a href="http://annevankesteren.nl/">Anne Van Kesteren</a> covers what I have not in his <a href="http://blog.whatwg.org/weekly-microdata-websocket-webidl">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><a href="http://lists.w3.org/Archives/Public/public-html/2011Jul/0133">RFC from implementers on Element.innerText</a> by Aryeh Gregor</p></li>
</ul>

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

<ul>
<li><p>Björn Höhrmann created a <a href="http://lists.w3.org/Archives/Public/www-archive/2011Jul/thread.html#msg3">prototype for a framework and a test suite for specifications</a> using Javascript.</p></li>
<li><p>The big all W3C Working groups meeting, <a href="http://lists.w3.org/Archives/Public/public-html/2011Jul/0075">TPAC 2011</a>, has been opened for registration. The Plenary day is an open session but you have to register. The meeting will be held from October 31 to November 4, 2011 in Santa Clara, California, USA. </p></li>
<li><p>A Web site with a list <a href="http://platform.html5.org/">Open Web Platform technologies</a></p></li>
<li><p>A new draft of <a href="http://lists.w3.org/Archives/Public/uri/2011Jul/0009">URI template</a> has been published. </p></li>
</ul>

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

<ul>
<li><p>The discussion highlighted <a href="http://www.w3.org/QA/2011/07/openweb-weekly-13">last week</a> about SVG, Canvas and accessibility has been going on for the full week, also the discussion about mutation events.</p></li>
<li><p>A discussion about <a href="http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/thread.html#msg53">test suites and RFC2119</a> shows the misunderstanding people have in between conformance, technology organization and certification.</p></li>
<li><p>A long HTTP <a href="http://lists.w3.org/Archives/Public/ietf-http-wg/2011JulSep/thread.html#msg37">discussion</a>  on the meaning and implementations of <a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics#section-8.1.2"><code>101 Switching Protocols</code></a></p></li>
<li><p><a href="http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/thread.html#msg144">update on a cursor index with a unique value  constraint</a></p></li>
<li><p>A new Exception model has been defined in WebIDL. The consequence is that other specifications might have to change. Anne van Kestern is <a href="http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/thread.html#msg133">asking</a> if it&#8217;s an issue for the specifications editors.</p></li>
<li><p>Last tweaks for getting <a href="http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/thread.html#msg193">WebSockets API to Last Call</a></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>]]>
        
    </content>
</entry>

<entry>
    <title>Open Web Platform Weekly Summary - 2011-06-29 - 2011-07-05</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/07/openweb-weekly-13.html" />
    <id>tag:www.w3.org,2011:/QA//1.9142</id>
    
    <published>2011-07-06T20:16:42Z</published>
    <updated>2011-07-07T20:23:15Z</updated>
    
    <summary type="html">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...</summary>
    <author>
        <name>Karl Dubost</name>
        <uri>http://my.opera.com/karlcow/blog/</uri>
    </author>
    
        <category term="HTML" />
    
        <category term="Open Web" />
    
        <category term="W3C Life" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[<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>]]>
        
    </content>
</entry>

<entry>
    <title>Open Web Platform Weekly Summary - 2011-06-21 - 2011-06-28</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/06/openweb-weekly-12.html" />
    <id>tag:www.w3.org,2011:/QA//1.9137</id>
    
    <published>2011-06-29T21:00:55Z</published>
    <updated>2011-06-29T23:23:04Z</updated>
    
    <summary type="html">The weekly summary of the Open Web Platform is out. I like the fact that Anne Van Kesteren has a different overview than mine. His last report. HTML5 is still in Last Call. Conversations Proposals WebKit Team has been experimenting...</summary>
    <author>
        <name>Karl Dubost</name>
        <uri>http://my.opera.com/karlcow/blog/</uri>
    </author>
    
        <category term="HTML" />
    
        <category term="Open Web" />
    
        <category term="W3C Life" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[<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. I like the fact that <a href="http://annevankesteren.nl/">Anne Van Kesteren</a> has a different overview than mine. His last  <a href="http://blog.whatwg.org/weekly-event-constructors">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>WebKit Team has been <a href="http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/thread.html#msg1345">experimenting</a> with a <a href="http://glazkov.com/2011/01/14/what-the-heck-is-shadow-dom/">Shadow DOM</a> API.</li>
<li><a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/032242.html">web standards based model for Augmented Reality</a></li>
</ul>

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

<ul>
<li>The HTTPbis WG is <a href="http://www.ietf.org/proceedings/81/agenda/httpbis.txt">meeting</a> in Quebec city for the IETF 81 meetings. </li>
<li>HTML WG Chairs have <a href="http://www.w3.org/mid/7EB63AAD-3DFC-40A6-A149-04D9761684F0@apple.com">appointed</a> Aryeh Gregor (Google), Anne van Kesteren (Opera), Simon Pieters (Opera) and Henri Sivonen (Mozilla) as Editorial Assistants for HTML5, HTML Microdata and HTML Canvas 2D Context to help Ian Hickson (Google) tasks.</li>
</ul>

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

<ul>
<li>HTTPbis WG is wondering if they should change the <a href="http://lists.w3.org/Archives/Public/ietf-http-wg/2011AprJun/thread.html#msg390">version number of HTTP</a> and in which ways. </li>
<li>Server-Sent specificiation has <a href="http://www.w3.org/mid/op.vxr2r5y164w2qv@anne-van-kesterens-macbook-pro.local">implications</a> on HTTP redirects and might require the design of <a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/231">new HTTP headers</a>. </li>
<li>What should be the <a href="http://lists.w3.org/Archives/Public/ietf-http-wg/2011AprJun/thread.html#msg386">strength of requirements on Accept header</a>.</li>
<li>Should the <a href="http://lists.w3.org/Archives/Public/ietf-http-wg/2011AprJun/thread.html#msg389">HTTP headers have a minimal acceptable floor in size</a>? Some people have tendency to use them abusively such as very verbose cookies but some implementations on the server side seems to limit also the size.</li>
<li>There is a debate around <a href="http://lists.w3.org/Archives/Public/public-html/2011Jun/thread.html#msg246">adding retained-mode features to the Canvas API</a>. Some people think it is a bad idea and it would be better to just use SVG. Using SVG seems a difficult option for accessibility reasons. Then some proposed that it would be better to fix SVG.</li>
<li><a href="http://lists.w3.org/Archives/Public/public-html/2011Jun/thread.html#msg425">Styling date/time related input types</a> is a big issue. Every Web designers seem not very satisfied with the native implementations of input and want the ability to style these form widgets to the style of their own Web site.</li>
<li>The Technical Architecture Group of W3C has <a href="http://www.w3.org/mid/4E04A795.5020609@arcanedomain.com">raised issues</a> about the interaction between HTML microdata and HTML+RDFa. </li>
<li><a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/thread.html#32229">drawing with singular transforms and zero-sized gradients</a></li>
<li><a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/thread.html#32243">multiple itemtypes in microdata</a></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>
]]>
        

    </content>
</entry>

<entry>
    <title>Open Web Platform Weekly Summary - 2011-05-17 - 2011-06-20</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/06/openweb-weekly-11.html" />
    <id>tag:www.w3.org,2011:/QA//1.9130</id>
    
    <published>2011-06-21T20:08:05Z</published>
    <updated>2011-06-22T20:58:22Z</updated>
    
    <summary type="html">Let&apos;s restart the Openweb platform weekly summary. It has been almost one month since the last time. HTML5 is in Last Call and there were a lot of discussions on many mailing lists. </summary>
    <author>
        <name>Karl Dubost</name>
        <uri>http://my.opera.com/karlcow/blog/</uri>
    </author>
    
        <category term="HTML" />
    
        <category term="Open Web" />
    
        <category term="W3C Life" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[<p>I dropped the ball since the last <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>. A lot of trips, jetlag, preparing talks didn&#8217;t help. <a href="http://annevankesteren.nl/">Anne Van Kesteren</a> is back from his long trip in South America and has <a href="http://blog.whatwg.org/weekly-back">taken over</a> the wonderful job that <a href="http://burningbird.net/">Shelley Powers</a> did for the last few weeks.</p>

<p><a href="http://w3.org/html5/">HTML5</a> is in Last Call. The <a href="http://w3.org/html/wg/">HTML WG</a> may expect a lot of comments.</p>

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

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

<ul>
<li>Mark Nottingham <a href="http://www.w3.org/mid/04FFD657-4CF3-44EE-A7DA-3BC533ACA001@mnot.net">created</a> a RFC draft for <a href="http://tools.ietf.org/html/draft-nottingham-linked-cache-inv-00.html">Linked Cache Invalidation</a>. It defines Web link types that invalidate HTTP caches, along with an HTTP cache-control extension that allows caches that understand those link types to use responses containing them. Yngve N. Pettersen has a similar document called <a href="http://datatracker.ietf.org/doc/draft-pettersen-cache-context/">Cache Context</a> and Mark pointed to a paper by Bala and Craig Wills on <a href="http://www2.research.att.com/~bala/papers/">Piggyback Cache Invalidation</a> as well sharing working and deployed code for <a href="https://github.com/mnot/squid-lci">Squid</a></li>
<li>There is a <a href="http://lists.w3.org/Archives/Public/ietf-http-wg/2011AprJun/thread.html#msg207">new proposal</a> for HTTP authentication scheme using a MAC algorithm to authenticate requests (via a pre-arranged MAC key): <a href="http://tools.ietf.org/html/draft-hammer-oauth-v2-mac-token">HTTP MAC Authentication Scheme</a></li>
<li>Marcos Caceres <a href="http://www.w3.org/mid/4DDA3B21.4090104@gmail.com">has</a> updated the <a href="http://dev.w3.org/2006/waf/widgets-digsig/test-suite/">test suite</a> for Widgets Digital Signature.</li>
<li>There has been a <a href="http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/thread.html#msg795">proposal</a> for a <a href="https://wiki.mozilla.org/Privacy/Features/DOMCryptAPISpec/Latest">DOMCrypt API</a>. The crypto API in browsers would allow the creation of secure communications. There are cases where it should not be required to rely only on the good will of the servers. </li>
<li>Adam Barth has been working on a <a href="https://docs.google.com/document/edit?id=1r_VTFKApVOaNIkocrg0z-t7lZgzisTuGTXkdzAk4gLU&amp;hl=en&amp;pli=1">URL Interface</a>. There was a strong <a href="http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/thread.html#msg778">interest</a> from the community. </li>
<li><a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-May/thread.html#31768">Proposal for separating script downloads and execution</a></li>
<li>Guha proposed a <a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-May/thread.html#31822">simplification to Microdata</a></li>
</ul>

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

<ul>
<li>A new version of the <a href="http://dev.w3.org/html5/decision-policy/decision-policy-v2.htm">Decision policy</a> for the HTML WG is being drafted. This document explains how decisions are made, what are the mechanisms to push further an issue, etc.</li>
<li><a href="http://www.w3.org/mid/E3EACD022300B94D88613639CF4E25F81AB65D2F@TK5EX14MBXC138.redmond.corp.microsoft.com">There</a> is also a <a href="http://www.w3.org/TR/2011/WD-DOM-Level-3-Events-20110531/">Last Call for DOM 3 Events</a>. Implementers have until June 28 for commenting on the implementability of the specification.</li>
<li>There is a <a href="http://www.w3.org/mid/92138C83-7747-47FE-B2D8-ED52189D8066@apple.com">request to give help</a> to Ian Hickson for dealing with the issues brought to the HTML WG. It is the time you could get involved in HTML5 Specification.</li>
<li>A new version of <a href="https://datatracker.ietf.org/doc/draft-vandesompel-memento/">Memento-ID</a> has been published which proposes a mechanism for keeping dated archives of content.</li>
<li><a href="http://www.w3.org/TR/2011/WD-widgets-20110607/">Widget Packaging &amp; XML Configuration</a>, <a href="http://www.w3.org/TR/2011/WD-widgets-apis-20110607/">Widget Interface</a> and <a href="http://www.w3.org/TR/2011/WD-widgets-digsig-20110607/">Widget Digital Signature</a> have been published as Last Call Working Drafts.</li>
<li>A Last Call Working Draft has been published for the <a href="http://www.w3.org/TR/2011/WD-contacts-api-20110616/">Contact API</a>. The comment deadline is July 14. The goal is to have a way to make the addressbook portable between Web applications.</li>
<li><a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/thread.html#31881">Enhancement request: change EventSource to allow cross-domain access</a></li>
</ul>

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

<ul>
<li><a href="http://lists.w3.org/Archives/Public/public-html/2011May/thread.html#msg386">Adapative images</a> are an issue for content negotiation based on the device capabilities. Right now there is no easy way to send a different image depending on the screen size. It becomes important in terms of usability and performances.</li>
<li>Getting the right feedback on a specification can be challenging. The tools might create an additional burden for the commenters. <a href="http://www.twitter.com/stevefaulkner">Steve Faulkner</a> is <a href="http://lists.w3.org/Archives/Public/public-html/2011May/thread.html#msg268">proposing</a> to improve Bugzilla which has been used for the HTML WG. Mike Smith is <a href="http://www.w3.org/html/wg/tracker/actions/203">working on a solution</a>.</li>
<li>There is a <a href="http://lists.w3.org/Archives/Public/public-html/2011Jun/thread.html#msg28">long dicussion</a> about where should lie the HTML5 normative requirements for <strong>Web Authors</strong>. Right now the HTML5 Specification contains the requirements for the different class of products (parser, authors, etc.). A view has been created for authors but which is for now informative only. The question is then &#8220;Should there be an easily readable normative specification for Web authors only?&#8221; </li>
<li>Is the <a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-14#section-8.2.4">HTTP code <code>203 Non-Authoritative</code></a> used and <a href="http://lists.w3.org/Archives/Public/ietf-http-wg/2011AprJun/thread.html#msg271">should it be deprecated</a>?</li>
<li>Vincent Scheib (Google) has <a href="http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/thread.html#msg1095">worked</a> on an implementation of mouse lock in Chrome</li>
<li>Israel Hilerio (Microsoft) proposed for IndexedDB: <a href="http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/thread.html#msg898">Using WebIDL Dictionary in IDBObjectStore.createIndex  for optionalParameters</a>, <a href="http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/thread.html#msg1062">Should deleteDatabase return IDBVersionChangeRequest?</a>, <a href="http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/thread.html#msg916">IDBDatabase.setVersion non-nullable parameter has a  default for null</a></li>
<li><q>Gecko, Presto, and Webkit all support on* event attributes on all DOM elements, not just HTMLElement. IE9 seems to only support them on HTMLElement.</q> Boris Zbarsky (Mozilla) <a href="http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/thread.html#msg717">proposed</a> to be supported on all DOM elements but element-specific (e.g. &#8220;click&#8221;).</li>
<li>Some changes are <a href="http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/thread.html#msg805">proposed</a> for the <a href="http://dev.w3.org/html5/postmsg/">Web Messaging specification</a></li>
<li>Aryeh Gregor has <a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-May/thread.html#31765">asked for feedback</a> on  <a href="http://aryeh.name/gitweb.cgi?p=editcommands;a=blob_plain;f=editcommands.html;hb=4a898d7#the-formatblock-command">supported elements for formatBlock</a></li>
<li><a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-May/thread.html#31866">Generalized execCommand() alternatives, or standardized selection and range handling</a></li>
<li><a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/thread.html#31928">WebVTT feedback</a> and <a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/thread.html#31898">Video feedback</a></li>
<li><a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/thread.html#32056">Selectors within <code>&lt;style scoped&gt;</code></a></li>
<li><a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/thread.html#32109">Hashing Passwords Client-side</a></li>
<li><a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/thread.html#32078">getSelection().modify() in vertical writing modes</a></li>
</li><a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-June/thread.html#32187">Handling of collapsed whitespace in contenteditable</a></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>]]>
        
    </content>
</entry>

<entry>
    <title>Ensuring Accessibility Support in HTML5</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/05/html5-lastcall-accessibility.html" />
    <id>tag:www.w3.org,2011:/QA//1.9109</id>
    
    <published>2011-05-31T05:35:55Z</published>
    <updated>2011-06-02T19:50:24Z</updated>
    
    <summary type="html">HTML5 was announced as a W3C Last Call Working Draft on 25 May 2011. The W3C press release  invites broad review to determine to what extent HTML5 has met its technical requirements and dependencies. The  Web Accessibility Initiative (WAI) encourages your comments and participation.</summary>
    <author>
        <name>Judy Brewer</name>
        <uri>http://www.w3.org/People/Brewer/</uri>
    </author>
    
        <category term="Accessibility" />
    
        <category term="HTML" />
    
        <category term="eGov" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[<p>HTML5 was <a href="http://www.w3.org/News/2011#entry-9105">announced as a W3C Last Call Working Draft</a> on 25 May 2011. The <a href="http://www.w3.org/2011/05/html5lc-pr.html">W3C press release </a> invites broad review to determine to what extent HTML5 has met its technical requirements and dependencies. The <a href="http://www.w3.org/WAI/"> Web Accessibility Initiative (WAI)</a> encourages your comments and participation.</p>

<p>HTML5 is the next revision in the core markup language of the Web, and offers powerful tools for creating Web-based applications that will run on any device. It is imperative that HTML5 meet the needs of all Web users, including those with disabilities.</p>

<h2>Information on Accessibility Gaps</h2>

<p>HTML5 includes new features, such as media and Canvas, for which WAI is working to ensure comprehensive accessibility support. WAI is also working to address current gaps in support for other accessibility requirements. Accessibility features missing at the time of the last call publication are listed within the <a href="http://www.w3.org/TR/html5/#status-of-this-document">status section of the HTML5 draft</a>. Updated details on the status of gaps in accessibility support are available on the <a href="http://www.w3.org/WAI/PF/HTML/wiki/Work_Topics"> HTML Accessibility Task Force Wiki</a>.</p> 

<h2>Coordination with the Accessibility Task Force</h2>

<p>WAI has been working with the HTML Working Group through the <a href="http://www.w3.org/WAI/PF/html-task-force"> Joint HTML and PFWG Accessibility Task Force (A11Y TF)</a>. Task Force Sub-Groups in the areas of text alternatives, Canvas, media, and WAI-ARIA will continue their work on accessibility feature support. The Task Force will closely monitor the processing of accessibility issues during the Last Call period. <strong>We encourage people to coordinate with the Task Force on improving accessibility support in HTML5.</strong> Comments describing unmet use cases, as well as technical details, are particularly useful.</p>

<h2>Comments welcome through 3 August 2011</h2>

<p>W3C has made it clear that <a href="http://www.w3.org/2011/05/html5lc-pr.html">HTML5 must meet W3C's commitment to accessibility</a>. Your comments can help clarify what is needed to ensure that HTML5 provides support for accessibility.</p> 
<br />
]]>
        
    </content>
</entry>

<entry>
    <title>HTML5: Are We There Yet?</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/05/html5_are_we_there_yet.html" />
    <id>tag:www.w3.org,2011:/QA//1.9107</id>
    
    <published>2011-05-25T21:50:22Z</published>
    <updated>2011-05-25T22:03:57Z</updated>
    
    <summary type="html">The HTML Working Group published 6 of their
documents as Last Call documents. It&apos;s time to get more people to look
at those documents and give some feedback.
</summary>
    <author>
        <name>Philippe Le Hégaret</name>
        <uri>http://www.w3.org/People/LeHegaret/</uri>
    </author>
    
        <category term="HTML" />
    
        <category term="Open Web" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[<p>
Back in September 2010, the HTML Chairs produced a timeline to advance
<a
href='http://www.w3.org/QA/2010/09/html5_getting_to_last_call.html'>HTML5
to Last Call</a>. Today, the HTML Working Group published <a href='http://www.w3.org/News/2011#entry-9105'>6 of their
documents as Last Call documents</a>. It's time to get more people to look
at those documents and give some feedback.
</p>

<p>
Due to the timeline, the group postponed resolving some <a
href='http://www.w3.org/html/wg/tracker/issues/open'>issues</a> that
were raised prior to Last Call; the group will now address them. In
addition, there were objections to some decisions made prior to last
call, and the group may revisit some of those. Other issues that were
closed may be reopened based on <a
href='http://dev.w3.org/html5/status/new-information-status.html'>new
information</a> (the accessibility issue related to the <a
href='http://www.w3.org/html/wg/tracker/issues/30'>longdesc
attribute</a> is already reopened for example). The Working Group will
use its <a
href="http://dev.w3.org/html5/decision-policy/decision-policy.html">decision
policy</a> to address these issues.
</p>

<p>So while HTML5 is not yet a standard, we are making tangible
progress, which is very exciting.</p>

<p>
The <a
href='http://lists.w3.org/Archives/Public/public-html/2011May/0165.html'>Last Call review period</a> extends until 3 August and we welcome your feedback. Note that the group will use the same process for managing issues in order to reach the next process transition by January 2012.
</p>

<p> In the meantime, the <a
href='http://www.w3.org/2011/Talks/0516-htmlupdate/#%289%29'>testing
effort</a> is continuing. We have 1276 approved test cases, and 28,858
submitted ones. We still need more tests to ensure better
coverage. The Group will also open itself to discussion on what to do
for "HTML.next". We welcome <a
href='http://www.w3.org/wiki/HTML/next'>ideas</a>.
</p>
]]>
        
    </content>
</entry>

<entry>
    <title>RDFa 1.1 with a rich snippet example</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/05/rdfa_11_with_a_rich_snippet_ex.html" />
    <id>tag:www.w3.org,2011:/QA//1.9102</id>
    
    <published>2011-05-23T10:39:20Z</published>
    <updated>2011-05-23T18:18:56Z</updated>
    
    <summary type="html"> With RDFa 1.1 making its way out of last call, I looked at the examples from Google’s Webmaster Central to see what RDFa 1.1 brings to those. A typical example is the one on reviews; here s where it...</summary>
    <author>
        <name>Ivan Herman</name>
        <uri>http://www.w3.org/People/Ivan</uri>
    </author>
    
        <category term="HTML" />
    
        <category term="Open Web" />
    
        <category term="Semantic Web" />
    
        <category term="Technology 101" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[    <p>With <a href="http://www.w3.org/TR/rdfa-core/">RDFa 1.1</a>
      making its way out of last call, I looked at the examples from
      Google’s Webmaster Central to see what RDFa 1.1 brings to those. A
      typical example is the one on <a
href="http://www.google.com/support/webmasters/bin/answer.py?answer=146645">reviews</a>;
      here s where it starts out in RDF 1.0:<br />
    </p>
    <pre>&lt;div <span style="color: rgb(0, 102, 0);">xmlns:v="http://rdf.data-vocabulary.org/#"</span> <span style="color: rgb(0, 102, 0);">typeof="v:Review"</span>&gt;
   &lt;span <span style="color: rgb(0, 102, 0);">property="v:itemreviewed"</span>&gt;L’Amourita Pizza&lt;/span&gt;
   Reviewed by
   &lt;span <span style="color: rgb(0, 102, 0);">property="v:reviewer"</span>&gt;Ulysses Grant&lt;/span&gt; on
   &lt;span <span style="color: rgb(0, 102, 0);">property="v:dtreviewed"</span> <span style="color: rgb(0, 102, 0);">content="2009-01-06"</span>&gt;Jan 6&lt;/span&gt;.
   &lt;span <span style="color: rgb(0, 102, 0);">property="v:summary"</span>&gt;Delicious, tasty pizza on Eastlake!&lt;/span&gt;
   &lt;span <span style="color: rgb(0, 102, 0);">property="v:description"</span>&gt;L'Amourita serves up traditional wood-fired 
   Neapolitan-style pizza, brought to your table promptly and without fuss. 
   An ideal neighborhood pizza joint.&lt;/span&gt;
   Rating:
   &lt;span <span style="color: rgb(0, 102, 0);">property="v:rating"</span>&gt;4.5&lt;/span&gt;
&lt;/div&gt;</pre>
    <p> The most important change is that RDFa 1.1 has moved away from
      using XML namespaces as a syntax for identifying vocabularies. In
      the simplest case, the <a
        href="http://www.w3.org/TR/2011/WD-rdfa-core-20110331/#A-vocab"><code>@vocab</code></a>
      attribute can be used to identify a vocabulary as follows:<br />
    </p>
    <pre>&lt;div <span style="color: rgb(0, 102, 0);">vocab="http://rdf.data-vocabulary.org/#"</span> <span style="color: rgb(0, 102, 0);">typeof="Review"</span>&gt;
   &lt;span <span style="color: rgb(0, 102, 0);">property="itemreviewed"</span>&gt;L’Amourita Pizza&lt;/span&gt;
   Reviewed by
   &lt;span <span style="color: rgb(0, 102, 0);">property="reviewer"</span>&gt;Ulysses Grant&lt;/span&gt; on
   &lt;span <span style="color: rgb(0, 102, 0);">property="dtreviewed"</span> <span style="color: rgb(0, 102, 0);">content="2009-01-06"</span>&gt;Jan 6&lt;/span&gt;.
   &lt;span <span style="color: rgb(0, 102, 0);">property="summary"</span>&gt;Delicious, tasty pizza on Eastlake!&lt;/span&gt;
   &lt;span <span style="color: rgb(0, 102, 0);">property="description"</span>&gt;L'Amourita serves up traditional wood-fired 
   Neapolitan-style pizza, brought to your table promptly and without fuss. 
   An ideal neighborhood pizza joint.&lt;/span&gt;
   Rating:
   &lt;span <span style="color: rgb(0, 102, 0);">property="rating"</span>&gt;4.5&lt;/span&gt;
&lt;/div&gt;<br /></pre>
    <p>The change looks small, but it means that the author has less
      complexity to worry about. Of course, the <code>@vocab</code>
      attribute may be placed somewhere up in the hierarchy, e.g., on
      the <code>body</code> element; this may become interesting if the
      same page reviews not only a pizza but, say, cannelloni, too.</p>
    <p>It is also interesting to compare the last code extract with the
      microdata example provided by Google for the same case:</p>
    <pre>&lt;div <span style="color: rgb(0, 102, 0);">itemscope</span> <span style="color: rgb(0, 102, 0);">itemtype="http://data-vocabulary.org/Review"</span>&gt;
  &lt;span <span style="color: rgb(0, 102, 0);">itemprop="itemreviewed"</span>&gt;L’Amourita Pizza&lt;/span&gt;
  Reviewed by <br />  &lt;span <span style="color: rgb(0, 102, 0);">itemprop="reviewer"</span>&gt;Ulysses Grant&lt;/span&gt; on
  &lt;time <span style="color: rgb(0, 102, 0);">itemprop="dtreviewed"</span> <span style="color: rgb(0, 102, 0);">datetime="2009-01-06"</span>&gt;Jan 6&lt;/time&gt;.
  &lt;span <span style="color: rgb(0, 102, 0);">itemprop="summary"</span>&gt;Delicious, tasty pizza in Eastlake!&lt;/span&gt;
  &lt;span <span style="color: rgb(0, 102, 0);">itemprop="description"</span>&gt;L'Amourita serves up traditional wood-fired <br />   Neapolitan-style pizza, brought to your table promptly and without fuss. <br />   An ideal neighborhood pizza joint.&lt;/span&gt;
  Rating: <br />   &lt;span <span style="color: rgb(0, 102, 0);">itemprop="rating"</span>&gt;4.5&lt;/span&gt;
&lt;/div&gt;
</pre>
    <p> Almost identical in terms of simplicity (or complexity, if you
      prefer); there is no real difference between the two. Which is,
      actually, to be expected: indeed, the example concentrates on what
      one could call a “single-vocabulary” case (whereby I mean that the
      structured data uses terms from within the same vocabulary). One
      of the main design goals of <a
        href="http://www.w3.org/TR/rdfa-core/">RDFa 1.1</a> (compared to
      the <a href="http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014">previous
        RDFa version</a>) was to simplify such simple cases.<br />
    </p><p>
    However, the same structured data in HTML may be used for other
    purposes, in which case one would possibly prefer to add additional
    terms. As a simple example, one might want to add the address of the
    restaurant using the <a
      href="http://www.w3.org/Submission/vcard-rdf/">vcard vocabulary</a>;
    this is the case where prefixes <span style="font-style: italic;">do</span>
    come handy. Indeed, one could add a few lines:</p>
    <pre>&lt;div <span style="color: rgb(0, 102, 0);">vocab="http://rdf.data-vocabulary.org/#"</span> <span style="color: rgb(0, 102, 0);">typeof="Review"</span>&gt;
   &lt;span <span style="color: rgb(0, 102, 0);">property="itemreviewed"</span>&gt;L’Amourita Pizza&lt;/span&gt;
   Reviewed by
   &lt;span <span style="color: rgb(0, 102, 0);">property="reviewer"</span>&gt;Ulysses Grant&lt;/span&gt; on
   &lt;span <span style="color: rgb(0, 102, 0);">property="dtreviewed"</span> <span style="color: rgb(0, 102, 0);">content="2009-01-06"</span>&gt;Jan 6&lt;/span&gt;.
   &lt;span <span style="color: rgb(0, 102, 0);">property="summary"</span>&gt;Delicious, tasty pizza on Eastlake!&lt;/span&gt;
   &lt;span <span style="color: rgb(0, 102, 0);">property="description"</span>&gt;L'Amourita serves up traditional wood-fired 
   Neapolitan-style pizza, brought to your table promptly and without fuss. 
   An ideal neighborhood pizza joint.&lt;/span&gt;
   Rating:
   &lt;span <span style="color: rgb(0, 102, 0);">property="rating"</span>&gt;4.5&lt;/span&gt;;
   Address:
   &lt;span <span style="color: rgb(204, 0, 0);">property="vcard:street-address"</span>&gt;111 Lake Drive&lt;/span&gt;,
   &lt;span <span style="color: rgb(204, 0, 0);">property="vcard:locality"</span>&gt;WonderCity&lt;/span&gt;, 
   &lt;span <span style="color: rgb(204, 0, 0);">property="vcard:postal-code"</span>&gt;5555&lt;/span&gt;, 
   &lt;span <span style="color: rgb(204, 0, 0);">property="vcard:country-name"</span>&gt;Australia&lt;/span&gt;.<br /> &lt;/div&gt;</pre>
    <p>which is just marginally more complicated than the previous case
      with the additional <code>vcard</code> properties. One could have
      sprinkled the code with other vocabulary elements, using Dublin
      Core or other review vocabularies, etc.<br />
    </p>
    <p>At first glance, this code does not look valid in RDFa 1.1,
      because there is no prefix declaration for <code>vcard</code>.
      This is correct, and should be added using the <a
        href="http://www.w3.org/TR/2011/WD-rdfa-core-20110331/#A-prefix"><code>@prefix</code></a>
      attribute. Except that… the profile mechanism of RDFa might become
      handy here: one could imagine Google (or the site hosting the
      review) defining a snippet profile including all the terms that
      Google recognizes directly but which could also contain prefixes
      for a number of well known other vocabularies (whether Google uses
      it in the search pages or not). If so, the only change to the code
      could be:</p>
    <pre>&lt;div <span style="color: rgb(0, 102, 0);">profile="http://google.profile.example.org"</span> <span style="color: rgb(0, 102, 0);">typeof="Review"</span>&gt;
   &lt;span <span style="color: rgb(0, 102, 0);">property="itemreviewed"</span>&gt;L’Amourita Pizza&lt;/span&gt;
   Reviewed by
   &lt;span <span style="color: rgb(0, 102, 0);">property="reviewer"</span>&gt;Ulysses Grant&lt;/span&gt; on
   &lt;span <span style="color: rgb(0, 102, 0);">property="dtreviewed"</span> <span style="color: rgb(0, 102, 0);">content="2009-01-06"</span>&gt;Jan 6&lt;/span&gt;.
   &lt;span <span style="color: rgb(0, 102, 0);">property="summary"</span>&gt;Delicious, tasty pizza on Eastlake!&lt;/span&gt;
   &lt;span <span style="color: rgb(0, 102, 0);">property="description"</span>&gt;L'Amourita serves up traditional wood-fired 
   Neapolitan-style pizza, brought to your table promptly and without fuss. 
   An ideal neighborhood pizza joint.&lt;/span&gt;
   Rating:
   &lt;span <span style="color: rgb(0, 102, 0);">property="rating"</span>&gt;4.5&lt;/span&gt;;
   Address:
   &lt;span <span style="color: rgb(204, 0, 0);">property="vcard:street-address"</span>&gt;111 Lake Drive&lt;/span&gt;,
   &lt;span <span style="color: rgb(204, 0, 0);">property="vcard:locality"</span>&gt;WonderCity&lt;/span&gt;, 
   &lt;span <span style="color: rgb(204, 0, 0);">property="vcard:postal-code"</span>&gt;5555&lt;/span&gt;, 
   &lt;span <span style="color: rgb(204, 0, 0);">property="vcard:country-name"</span>&gt;Australia&lt;/span&gt;.
&lt;/div&gt;</pre>
    <p>Actually… the <code>vcard</code> case, specifically, may be even
      easier. Indeed, RDFa 1.1 has the notion of a <a
        href="http://ivan-herman.name/2011/04/01/2nd-last-call-for-rdfa-1-1/">default
        profile</a>, i.e., a small set of vocabulary prefixes that are
      “predefined”. Although the exact list of those prefixes is not yet
      fixed, we can expect that <code>vcard</code> will be one of
      those, being one of the most widely used vocabularies around.
      I.e., the code may be valid RDFa 1.1 after all…</p>
    <p>The key point here: RDFa 1.1 brings in an open architecture that
      scales to authors adding structured data mixing in with ease
      whatever vocabulary their application needs. Scaling, the
      possibility to use several vocabularies with ease is RDFa’s real
      strength, though this is often forgotten. And that openness
      matters.  Take, for example, <a
href="http://priyankmohan.blogspot.com/2009/12/online-retail-how-best-buy-is-using.html">the
        BestBuy case</a>. They started with the simple snippet case
      (yielding real benefit from it, thanks to Google or Yahoo!) but
      then they added new features with new vocabularies, and <a
href="http://jay.beweep.com/2011/04/26/released-human-product-discovery-via-machines-rdfa-and-shop-urls/">extended
        the functionality for other uses</a> (e.g., to identify shops
      where a specific item is to available). As so often, openness
      counts in the long term, also for structured data…
    </p>]]>
        
    </content>
</entry>

<entry>
    <title>Open Web Platform Weekly Summary - 2011-05-09 - 2011-05-16</title>
    <link rel="alternate" type="text/html" href="http://www.w3.org/QA/2011/05/openweb-weekly-10.html" />
    <id>tag:www.w3.org,2011:/QA//1.9101</id>
    
    <published>2011-05-16T20:22:35Z</published>
    <updated>2011-05-18T20:28:15Z</updated>
    
    <summary type="html">The HTML WG is about to reach a very important step of the current W3C Process: Last Call. For a W3C Technology, it is the moment where the WG members think, they have solve any major issues. The document is considered mature and stable enough. Last Call is here to give another chance for all participants to review a stable version of the specification. All comments will be formally recorded and answered.</summary>
    <author>
        <name>Karl Dubost</name>
        <uri>http://my.opera.com/karlcow/blog/</uri>
    </author>
    
        <category term="HTML" />
    
        <category term="Open Web" />
    
        <category term="W3C Life" />
    
    <content type="html" xml:lang="en" xml:base="http://www.w3.org/QA/">
        <![CDATA[<p>The <a href="http://w3.org/html/wg/">HTML WG</a> is about to reach a very important step of the current W3C Process: Last Call. For a <a href="http://www.w3.org/TR/">W3C Technology</a>, it is the moment where the WG members think, they have solve any major issues. The document is considered mature and stable enough. Last Call is here to give another chance for all participants to review a stable version of the specification. All comments will be formally recorded and answered. Then once all comments have been answered with satisfaction for both parties, the specification is  entering Candidate Recommendation. It is the opportunity for the group to produce an implementation report. James Graham (Opera) <a href="http://www.w3.org/mid/4DD234D3.2030201@opera.com">asked specifically</a> on how the HTML WG should define the <acronym title="Proposed Recommendation">PR</acronym> entrance criteria.</p>

<p>The HTML WG is a bit specific though. A lot of what is inside in the <a href="http://w3.org/html5/">HTML5</a> specification has been motivated by describing what browsers were already doing on the Web. This is far to be perfect. There is still discrepancies in between implementations, but it is a lot better than before. If you authorize me to share <strong>my own opinion</strong>, the specification needs to be implemented by more authoring tools developers to be able to give practical feedback on the specification.</p>

<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> might then change a bit. Though there is more to cover than just the HTML WG.</p>

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

<p>There was no <a href="http://w3.org/html/wg/">HTML WG</a> desisions this week. Paul Cotton (Microsoft, co-chair) has <a href="http://www.w3.org/mid/E3EACD022300B94D88613639CF4E25F81A2CBE99@TK5EX14MBXC132.redmond.corp.microsoft.com">sent</a> a Last Call <a href="http://www.w3.org/2002/09/wbs/40318/html5-last-call-poll/">decision poll</a>. These following documents are covered by the poll.</p>

<ol>
<li><a href="dev.w3.org/html5/spec/">HTML5</a></li>
<li><a href="dev.w3.org/html5/rdfa/">HTML+RDFa</a></li>
<li><a href="dev.w3.org/html5/md/">HTML Microdata</a></li>
<li><a href="dev.w3.org/html5/2dcontext/">HTML Canvas 2D Context</a></li>
<li><a href="dev.w3.org/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html">HTML/XHTML  Compatibility Authoring Guidelines</a></li>
<li><a href="dev.w3.org/html5/alt-techniques/">HTML5: Techniques for providing useful text alternatives</a></li>
</ol>

<p>Paul Cotton also sent a <a href="http://www.w3.org/mid/E3EACD022300B94D88613639CF4E25F81A2CBE6E@TK5EX14MBXC132.redmond.corp.microsoft.com">detailed timeline for Last Call</a>.</p>

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

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

<ul>
<li><a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-May/031538.html">FullScreen API</a> second round with feedback. WebKit is in the process of implementing Mozilla&#8217;s proposed <a href="https://wiki.mozilla.org/Gecko:FullScreenAPI">Full Screen API</a>.</li>
<li><a href="http://www.w3.org/mid/BANLkTik4BzGwGuVevwL6gQpctpy-OyoJFA@mail.gmail.com">Changing the angles in CSS gradients</a></li>
</ul>

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

<ul>
<li><a href="http://www.w3.org/2011/Talks/0516-htmlupdate/">HTML WG status report</a> has been presented by Sam Ruby (IBM) and Paul Cotton (Microsoft), co-chairs, to the W3C Advisory Committee meeting, this week in Bilbao, Spain.</li>
<li><a href="http://dev.w3.org/html5/decision-policy/decision-policy-v2.html">Revised HTML WG Decision Policy</a></li>
<li>Call for publishing <a href="http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html">DOM3 Events</a> as Last Call WD</li>
<li>Changes on the <a href="http://www.w3.org/mid/4DCB1274.6090900@mozilla.com">FileAPI</a> Editors draft</li>
<li><a href="http://www.w3.org/wiki/Standards_for_Web_Applications_on_Mobile">Overview of W3C technologies for mobile Web applications</a></li>
<li><a href="http://www.w3.org/2011/05/05-webapps-minutes">Minutes, 05 May 2011 DOM3 Events Telcon</a></li>
<li><a href="http://www.w3.org/2011/05/11-webapps-minutes">Web Applications Working Group Teleconference</a></li>
</ul>

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

<ul>
<li><a href="http://blog.whatwg.org/whatwg-weekly-week-ending-may-16th">WHATWG Weekly: Week ending May 16th</a> by Shelley Powers</li>
<li><a href="http://www.w3.org/mid/BANLkTim60-UuyQJQ_DVz87H4zE8M0zYgoA@mail.gmail.com"> General Questions on HTML5 Link Relations, Registries, etc.</a></li>
<li><a href="http://www.w3.org/mid/20110510212615.GA504@1wt.eu">On the abuse of chunking for interactive usages</a> by Willy Tarreau in HTTP WG</li>
<li>A question from OAuth WG to the HTTP WG: <a href="http://www.w3.org/mid/90C41DD21FB7C64BB94121FBBC2E723447581DA816@P3PW5EX1MB01.EX1.SECURESERVER.NET">BCP for returning HTTP Authentication (2617) Error Status</a></li>
<li>Arun Ranganathan (Mozilla) asked about <a href="http://www.w3.org/mid/4DCC3CD1.4030503@mozilla.com">Blob URI Scheme for Binary Data Access</a> to the HTTP WG</li>
<li><a href="http://www.w3.org/mid/BANLkTik6pnJhgqSNSbXgc+p8ecYs-tm5gw@mail.gmail.com">[widgets] WARP usability issue</a></li>
<li><a href="http://www.w3.org/mid/BANLkTikDQXLW+gQVEvuMp_iuk=OAKSDmDA@mail.gmail.com">Synchronous XMLHttpRequest and events</a></li>
<li><a href="http://www.w3.org/mid/op.vvlx3fafa3v5gv@hr-opera.oslo.opera.com">safeguarding a live getData() against looping scripts?</a></li>
<li><a href="http://www.w3.org/mid/op.vvc0ywo16ugkrk@rabdomant-ubuntu">Target of onkeyup/down/press events</a></li>
<li><a href="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-May/031535.html">The PeerConnection onmessage function attribute</a></li>
<li><a href="http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2011-May/031577.html">Pressing Enter in contenteditable</a> is implemented with a lot of variations.</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>
]]>
        
    </content>
</entry>

</feed>