the_need_for_diversity.html
14 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
<?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='html, implementation, quality' />
<meta name="description" content="Chris Wilson (Microsoft) in a recent interview with Kevin Yank at Sitepoint stressed the need of diversity for a healthy Web Ecosystem: Chris Wilson: As for building on WebKit or Gecko or any of the other engines, part of that..." />
<meta name="revision" content="$Id: the_need_for_diversity.html,v 1.45 2011/12/16 02:58:42 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>The Need for Diversity - W3C Blog</title>
<link rel="start" href="http://www.w3.org/QA/" title="Home" />
<link rel="prev" href="http://www.w3.org/QA/2007/12/ncz.html" title="Nicholas Zakas on HTML5" />
<link rel="next" href="http://www.w3.org/QA/2007/12/is_wcag_20_almost_done.html" title="Is WCAG 2.0 almost done?!" />
<!--
<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/2007/12/the_need_for_diversity.html"
trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/111"
dc:title="The Need for Diversity"
dc:identifier="http://www.w3.org/QA/2007/12/the_need_for_diversity.html"
dc:subject="HTML"
dc:description="Chris Wilson (Microsoft) in a recent interview with Kevin Yank at Sitepoint stressed the need of diversity for a healthy Web Ecosystem: Chris Wilson: As for building on WebKit or Gecko or any of the other engines, part of that..."
dc:creator="Karl Dubost"
dc:date="2007-12-10T21:10:05+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/2007/12/ncz.html">« Nicholas Zakas on HTML5</a> |
<a href="http://www.w3.org/QA/">Main</a>
| <a href="http://www.w3.org/QA/2007/12/is_wcag_20_almost_done.html">Is WCAG 2.0 almost done?! »</a>
</p>
<h2 class="entry-header">The Need for Diversity</h2>
<div class="entry-body">
<p><a href="http://blogs.msdn.com/cwilso/">Chris Wilson</a> (Microsoft) in a recent <a href="http://www.sitepoint.com/article/ie-standards-chris-wilson">interview</a> with <a href="http://www.sitepoint.com/articlelist/48">Kevin Yank</a> at Sitepoint stressed the need of diversity for a healthy <a href="http://www.w3.org/QA/2007/06/the_web_as_an_ecosystem">Web Ecosystem</a>:</p>
<blockquote>
<p><strong>Chris Wilson</strong>: As for building on WebKit or Gecko or any of the other engines, part of that I'm sure probably is that we would have to leap through some licensing challenges there. But, the biggest reason for me is that there's a real responsibility when we ship code, particularly to half a billion people, and we would be taking on that responsibility for a set of code that we don't own, we didn't come up with it, we're not experts in it, and there's a lot of code there. But we're blamed if something goes wrong; even further than that, we're responsible for it if something goes wrong. So, you know, if there's a security exploit, we have to go fix it, we have to go deliver the fix immediately, or it's-- we're on the line for that. And that makes it a bit challenging. And when I look at the other toolkits out there, I think that on the amount of work that they've put in to completing some standards work or, you know, taking on a bunch of different standards that we haven't gotten to yet, I think they've done some great things; I don't think it's so great that the only answer really should be, "Let's go take that engine." One of the things that I know that I really would like to see from the standardization side of my job, you know, from my <a href="http://www.w3.org/html/wg/">HTML Working Group</a> co-chair, and kind of co-ordinating our other standards involvement -- One of the things that I would point out too is that, really, the more implementations that you have that work differently, the better you make your standards. Because, otherwise, you end up just relying on one implementation to define what the standard is, and in a way that sort of happened with IE for awhile. Before that, it absolutely was happening that Netscape defined what the standard was. I mean, we had to be compatible with Netscape, because that's what people wrote their content to. So I think that having multiple implementations is really a good thing; that's why the W3C requires it.</p>
</blockquote>
<p>An ecosystem is healthy when its constituents are diverse. In November 2004, <a href="http://standblog.org/">Tristan Nitot</a> (Mozilla) was <a href="http://standblog.org/blog/post/2004/11/19/93113814-two-interesting-posts-on-mozillian-blogs">saying</a>:</p>
<blockquote>
<p>I don't believe in the "one size fits all" approach. Diversity and standards-compliance are the key to a healthy Web.</p>
</blockquote>
<p>It's not the only key to success but it is definitely part of the answer.</p>
</div>
<div id="more" class="entry-more">
</div>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/karl/">Karl Dubost</a> on December 10, 2007 9:10 PM in <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/web_spotting/opinions_editorial/">Opinions &amp; Editorial</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2007/12/the_need_for_diversity.html">Permalink</a>
| <a href="http://www.w3.org/QA/2007/12/the_need_for_diversity.html#comments">Comments (2)</a>
| <a href="http://www.w3.org/QA/2007/12/the_need_for_diversity.html#trackback">TrackBacks (0)</a>
</p>
<h3 class="comments-header" id="comments">Comments</h3>
<div class="comment" id="comment-91710">
<p class="comment-meta" id="c091710">
<span class="comment-meta-author"><strong>Marc J. Driftmeyer </strong></span>
<span class="comment-meta-date"><a href="#c091710">#</a> 2007-12-13</span>
</p>
<div class="comment-bulk">
<p>``Chris Wilson (Microsoft) in a recent interview with Kevin Yank at Sitepoint stressed out the need of diversity for an healty Web Ecosystem:''</p>
<p>Try this on for size:</p>
<p>``Chris Wilson (Microsoft) in a recent interview with Kevin Yank at Sitepoint stressed the need of diversity for a healthy Web Ecosystem:''</p>
<p>The an' precedes a word beginning with a vowel. Thea' precedes a word beginning with a consonant.</p>
<p>Ex: an answer, an interview, an idea, etc.
Ex: a heart, a job, a wish, a game, etc.</p>
<p>healty->healthy.</p>
<p>stressed out--> stressed. Just bad grammar.</p>
<p>Regarding Mr. Wilson,</p>
<p>He has a fiduciary responsibility to down play technologies that directly attack their business model, regardless of the fact that they represent a collaborative effort of major US Corporations to individuals whose collaborative work has produced frameworks which more closely support the W3C standards than his company technologies.</p>
<p>Simply put, if Microsoft can't buy it or copy it and muck it up they down play their competition and proclaim technologies surpassing their competition that are in the works, but never materialize. Repeat and rinse.</p>
<p>I would appreciate, as a developer, that Mr. Wilson could articulate his disdain more clearly than he does. I don't fault him for giving back handed compliments on other technologies and his half-hearted attempt that he [Microsoft] is for choice first, business second.</p>
<p>It's bad enough we have slang sprinkled in articles throughout the Internet blogs that people overlook because it's not a traditional printing business model. However, it's even worse when people whose salaries are quite large can't manage to write a statement devoid of grammatical errors.</p>
</div>
</div>
<div class="comment" id="comment-91874">
<p class="comment-meta" id="c091874">
<span class="comment-meta-author"><strong>karl dubost, w3c </strong></span>
<span class="comment-meta-date"><a href="#c091874">#</a> 2007-12-13</span>
</p>
<div class="comment-bulk">
<p>Hi Marc,</p>
<p>Thanks for the grammar suggestions. It illustrates my Frenglish.
The rest of your comment is addressed at Chris Wilson and Microsoft, so I leave it to them if they happen to read it. </p>
<p>In case, it was not understood, I was suggesting that more players create a system where standards are a necessity. </p>
</div>
</div>
<div class="comments-open" id="comments-open">
<h3 class="comments-open-header">Leave a comment</h3>
<div class="comments-open-moderated">
<p>
Note: this blog is intended to foster <strong>polite
on-topic discussions</strong>. Comments failing these
requirements and spam will not get published. Please,
enter your real name and email address. Every
individual comment is reviewed by the W3C staff.
This may take some time, thank you for your patience.
</p>
<p>
You can use the following HTML markup (a href, b, i,
br/, p, strong, em, ul, ol, li, blockquote, pre)
and/or <a href="http://daringfireball.net/projects/markdown/syntax">Markdown syntax</a>.</p>
</div>
<div id="comments-open-data">
<form method="post" action="http://www.w3.org/QA/sununga/beach.pl" id="comments-form">
<h4>Your comment</h4>
<div id="comments-open-text">
<textarea id="comment-text" name="text" rows="20" cols="100"></textarea><br />
<label for="comment-text">Write your comment text here. Remember, keep the discussion on topic and courteous.</label>
</div>
<h4>About you</h4>
<div id="comment-form-name">
<input type="hidden" name="static" value="1" />
<input type="hidden" name="entry_id" value="120" />
<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 02:58:42 $</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>