openweb-weekly-20.html
16.3 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<style type="text/css" media="all">
@import "/QA/2006/01/blogstyle.css";
</style>
<meta name="keywords" content='css, dom, html5, openweb, w3c, web architecture, webapps' />
<meta name="description" content="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!" />
<meta name="revision" content="$Id: openweb-weekly-20.html,v 1.12 2011/12/16 03:00:32 gerald Exp $" />
<link rel="alternate" type="application/atom+xml" title="Atom" href="http://www.w3.org/QA/atom.xml" />
<link rel="alternate" type="application/rss+xml" title="RSS 1.0" href="http://www.w3.org/QA/news.rss" />
<title>Open Web Platform Weekly Summary - 2011-11-14 - 2011-11-20 - W3C Blog</title>
<link rel="start" href="http://www.w3.org/QA/" title="Home" />
<link rel="prev" href="http://www.w3.org/QA/2011/11/from_hypertext_to_hyperdevices.html" title="From hypertext to hyperdevices" />
<link rel="next" href="http://www.w3.org/QA/2011/11/rdfa_11_meets_json-ld_in_the_d.html" title="RDFa 1.1 meets JSON-LD in the Distiller…" />
<!--
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"
xmlns:dc="http://purl.org/dc/elements/1.1/">
<rdf:Description
rdf:about="http://www.w3.org/QA/2011/11/openweb-weekly-20.html"
trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/445"
dc:title="Open Web Platform Weekly Summary - 2011-11-14 - 2011-11-20"
dc:identifier="http://www.w3.org/QA/2011/11/openweb-weekly-20.html"
dc:subject="Open Web"
dc:description="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!"
dc:creator="Karl Dubost"
dc:date="2011-11-22T20:05:39+00:00" />
</rdf:RDF>
-->
<!-- <script type="text/javascript" src="http://www.w3.org/QA/mt.js"></script>-->
</head>
<body class="layout-one-column">
<div id="banner">
<h1 id="title">
<a href="http://www.w3.org/"><img height="48" alt="W3C" id="logo" src="http://www.w3.org/Icons/WWW/w3c_home_nb" /></a>
W3C Blog
</h1>
</div>
<ul class="navbar" id="menu">
<li><strong><a href="/QA/" title="W3C Blog Home">[ W3C Blog ]</a></strong></li>
<li><a href="/QA/Library/" title="Documents and Publications on Web and Quality">Documents</a></li>
<li><a href="/QA/Tools/" accesskey="3" title="Validators and other Tools">Tools</a></li>
<li><a href="/2007/12/qa-blog-help/index#feedback">Feedback</a></li>
</ul>
<div id="searchbox">
<form method="get" action="http://www.google.com/custom" enctype="application/x-www-form-urlencoded">
<p id="formbox"><input type="text" size="15" class="textfield" name="q" accesskey="E" maxlength="255" /> <input type="submit" class="submitfield" value="Search" id="goButton" name="sa" accesskey="G" /> <input type="hidden" name="cof" value="T:black;LW:72;ALC:#ff3300;L:http://www.w3.org/Icons/w3c_home;LC:#000099;LH:48;BGC:white;AH:left;VLC:#660066;GL:0;AWFID:0b9847e42caf283e;" /><input type="hidden" id="searchW3C" name="sitesearch" checked="checked" value="www.w3.org/QA" /><input type="hidden" name="domains" value="www.w3.org/QA" /></p>
</form>
</div>
<div id="main"><!-- This DIV encapsulates everything in this page - necessary for the positioning -->
<p class="content-nav">
<a href="http://www.w3.org/QA/2011/11/from_hypertext_to_hyperdevices.html">« From hypertext to hyperdevices</a> |
<a href="http://www.w3.org/QA/">Main</a>
| <a href="http://www.w3.org/QA/2011/11/rdfa_11_meets_json-ld_in_the_d.html">RDFa 1.1 meets JSON-LD in the Distiller… »</a>
</p>
<h2 class="entry-header">Open Web Platform Weekly Summary - 2011-11-14 - 2011-11-20</h2>
<div class="entry-body">
<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><template></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><p id="item1" typeof="ex:item" about="#item1">
<span property="item_name">An interesting item (1)</span>
</p>
</code></pre>
<p>His proposal is to reduce it to:</p>
<pre><code><p id="item1" typeof="ex:item">
<span property="rdfs:label">An interesting item (1)</span>
</p>
</code></pre>
<p>which would produced the triples of information.</p>
<pre><code> <http://example.org/document1#item1> rdf:type <http://example.org/ns/item> .
<http://example.org/document1#item1> 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’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 “new” <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><audio></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>’s <a href="http://blog.whatwg.org/weekly-time-police">report</a> is about <code><time></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’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>
</div>
<div id="more" class="entry-more">
</div>
<p class="postinfo">Filed by <a href="http://my.opera.com/karlcow/blog/">Karl Dubost</a> on November 22, 2011 8:05 PM in <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/open_web/">Open Web</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/w3c_life/">W3C Life</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2011/11/openweb-weekly-20.html">Permalink</a>
| <a href="http://www.w3.org/QA/2011/11/openweb-weekly-20.html#comments">Comments (0)</a>
| <a href="http://www.w3.org/QA/2011/11/openweb-weekly-20.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="9266" />
<input type="hidden" name="__lang" value="en" />
<label for="comment-author">Your Name</label>
<input id="comment-author" name="author" size="30" value="" />
</div>
<div id="comment-form-email">
<label for="comment-email">Your Email Address</label>
<input id="comment-email" name="email" size="30" value="" />
</div>
<div id="comments-open-footer">
<input type="submit" accesskey="s" name="post" id="comment-submit" value="Submit" />
</div>
</form>
</div>
</div>
<p id="gentime">This page was last generated on $Date: 2011/12/16 03:00:32 $</p>
</div><!-- End of "main" DIV. -->
<address>
This blog is written by W3C staff and working group participants,<br />
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> © 1994-2011
<a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a>®
(<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>