open_web_platform_weekly_summa.html 16 KB

Raw Blame History Permalink

<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
  <head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <style type="text/css" media="all">
    @import "/QA/2006/01/blogstyle.css";
    </style>
    <meta name="keywords" content='css, html, html5, http, openweb, w3c, web architecture, webapps' />
    <meta name="description" content="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." />
    <meta name="revision" content="$Id: open_web_platform_weekly_summa.html,v 1.12 2011/12/16 03:00:37 gerald Exp $" />
   <link rel="alternate" type="application/atom+xml" title="Atom" href="http://www.w3.org/QA/atom.xml" />
   <link rel="alternate" type="application/rss+xml" title="RSS 1.0" href="http://www.w3.org/QA/news.rss" />
   <title>Open Web Platform Weekly Summary - 2011-12-05 - 2011-12-11 - W3C Blog</title>

   <link rel="start" href="http://www.w3.org/QA/" title="Home" />
   <link rel="prev" href="http://www.w3.org/QA/2011/12/web_and_tv_ig_note_on_home_net.html" title="Web and TV IG note on Home Networking Scenarios published" />
   <link rel="next" href="http://www.w3.org/QA/2011/12/interview_pearson_company_on_o.html" title="Interview: Pearson Company on Open Web Platform and Publishing" />

   <!--
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
         xmlns:dc="http://purl.org/dc/elements/1.1/">
<rdf:Description
    rdf:about="http://www.w3.org/QA/2011/12/open_web_platform_weekly_summa.html"
    trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/452"
    dc:title="Open Web Platform Weekly Summary - 2011-12-05 - 2011-12-11"
    dc:identifier="http://www.w3.org/QA/2011/12/open_web_platform_weekly_summa.html"
    dc:subject="Open Web"
    dc:description="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."
    dc:creator="Karl Dubost"
    dc:date="2011-12-12T23:32:24+00:00" />
</rdf:RDF>
-->

    <!-- <script type="text/javascript" src="http://www.w3.org/QA/mt.js"></script>-->

</head>
<body class="layout-one-column">
      <div id="banner">
      <h1 id="title">
	<a href="http://www.w3.org/"><img height="48" alt="W3C" id="logo" src="http://www.w3.org/Icons/WWW/w3c_home_nb" /></a>
W3C Blog
</h1>
    </div>

    <ul class="navbar" id="menu">
        <li><strong><a href="/QA/" title="W3C Blog Home">[ W3C Blog ]</a></strong></li>
        <li><a href="/QA/Library/" title="Documents and Publications on Web and Quality">Documents</a></li>
        <li><a href="/QA/Tools/" accesskey="3" title="Validators and other Tools">Tools</a></li>
        <li><a href="/2007/12/qa-blog-help/index#feedback">Feedback</a></li>
    </ul>
<div id="searchbox">
<form method="get" action="http://www.google.com/custom" enctype="application/x-www-form-urlencoded">
<p id="formbox"><input type="text" size="15" class="textfield" name="q" accesskey="E" maxlength="255" /> <input type="submit" class="submitfield" value="Search" id="goButton" name="sa" accesskey="G" /> <input type="hidden" name="cof" value="T:black;LW:72;ALC:#ff3300;L:http://www.w3.org/Icons/w3c_home;LC:#000099;LH:48;BGC:white;AH:left;VLC:#660066;GL:0;AWFID:0b9847e42caf283e;" /><input type="hidden" id="searchW3C" name="sitesearch" checked="checked" value="www.w3.org/QA" /><input type="hidden" name="domains" value="www.w3.org/QA" /></p>
</form>
</div>


    <div id="main"><!-- This DIV encapsulates everything in this page - necessary for the positioning -->

                     <p class="content-nav">
                        <a href="http://www.w3.org/QA/2011/12/web_and_tv_ig_note_on_home_net.html">&laquo; Web and TV IG note on Home Networking Scenarios published</a> |
                        <a href="http://www.w3.org/QA/">Main</a>
                        | <a href="http://www.w3.org/QA/2011/12/interview_pearson_company_on_o.html">Interview: Pearson Company on Open Web Platform and Publishing &raquo;</a>
                     </p>

                        <h2 class="entry-header">Open Web Platform Weekly Summary - 2011-12-05 - 2011-12-11</h2>
                           <div class="entry-body">
                              <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>

                           </div>
                           <div id="more" class="entry-more">

                           </div>
                       <p class="postinfo">Filed by <a href="http://my.opera.com/karlcow/blog/">Karl Dubost</a> on December 12, 2011 11:32 PM in <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/technology/http/">HTTP</a>, <a href="http://www.w3.org/QA/archive/open_web/">Open Web</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/w3c_life/">W3C Life</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2011/12/open_web_platform_weekly_summa.html">Permalink</a>
                                 | <a href="http://www.w3.org/QA/2011/12/open_web_platform_weekly_summa.html#comments">Comments (0)</a>
                                 | <a href="http://www.w3.org/QA/2011/12/open_web_platform_weekly_summa.html#trackback">TrackBacks (0)</a>
</p>


  <div class="comments-open" id="comments-open">
<h3 class="comments-open-header">Leave a comment</h3>

<div class="comments-open-moderated">
   <p>
   Note: this blog is intended to foster <strong>polite
   on-topic discussions</strong>. Comments failing these
   requirements and spam will not get published. Please,
   enter your real name and email address. Every
   individual comment is reviewed by the W3C staff.
   This may take some time, thank you for your patience.
   </p>
   <p>
   You can use the following HTML markup (a href, b, i,
   br/, p, strong, em, ul, ol, li, blockquote, pre)
   and/or <a href="http://daringfireball.net/projects/markdown/syntax">Markdown syntax</a>.</p>
</div>

<div id="comments-open-data">
<form method="post" action="http://www.w3.org/QA/sununga/beach.pl" id="comments-form">
<h4>Your comment</h4>
<div id="comments-open-text">
  <textarea id="comment-text" name="text" rows="20" cols="100"></textarea><br />
<label for="comment-text">Write your comment text here. Remember, keep the discussion on topic and courteous.</label>
</div>

<h4>About you</h4>
<div id="comment-form-name">
  <input type="hidden" name="static" value="1" />
<input type="hidden" name="entry_id" value="9291" />
<input type="hidden" name="__lang" value="en" />
<label for="comment-author">Your Name</label>
<input id="comment-author" name="author" size="30" value="" />
</div>
<div id="comment-form-email">
<label for="comment-email">Your Email Address</label>
<input id="comment-email" name="email" size="30" value="" />
</div>

<div id="comments-open-footer">
<input type="submit" accesskey="s" name="post" id="comment-submit" value="Submit" />

</div>
</form>
</div>
</div>


<p id="gentime">This page was last generated on $Date: 2011/12/16 03:00:37 $</p>

      </div><!-- End of "main" DIV. -->

<address>

This blog is written by W3C staff and working group participants,<br />
&nbsp;and maintained by <a href="/People/CMercier/">Coralie Mercier</a>.<br />
Authorized parties may <a href="/QA/new">log in</a> to create a new entry.<br/>
<span id="poweredby">Powered by Movable Type, magpierss and a lot of Web Technology</span>
    </address>


    <p class="copyright">
      <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> &copy; 1994-2011
      <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a>&reg;
      (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>,
      <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
      <a href="http://www.keio.ac.jp/">Keio</a>),
      All Rights Reserved.
      W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
      <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>,
      <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a>
      and <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/copyright-software">software licensing</a>
      rules apply. Your interactions with this site are in accordance
      with our <a href="http://www.w3.org/Consortium/Legal/privacy-statement#Public">public</a> and
      <a href="http://www.w3.org/Consortium/Legal/privacy-statement#Members">Member</a> privacy
      statements.
    </p>

  </body>
</html>