tpac-2007-openness.html
13.4 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
<?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='conference, tpac, tpac2007, w3c, w3c_tpac07' />
<meta name="description" content="The participants of the W3C tech plenary are back from their lunch overlooking the gorgeous Charles river, to tackle the question of "openness". This is a development from a topic already raised today: a lot of people's lives and living..." />
<meta name="revision" content="$Id: tpac-2007-openness.html,v 1.52 2011/12/16 02:58:39 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>TPAC 2007 - Openness of W3C Working Groups - W3C Blog</title>
<link rel="start" href="http://www.w3.org/QA/" title="Home" />
<link rel="prev" href="http://www.w3.org/QA/2007/11/tpac-2007-html-5-xhtml-20-fun.html" title="TPAC 2007 - HTML 5, XHTML 2.0, Future Formats" />
<link rel="next" href="http://www.w3.org/QA/2007/11/tpac-2007-uri-extensibility.html" title="TPAC 2007 - URI-Based Extensibility: Benefits, Deviations, Lessons-Learned" />
<!--
<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/11/tpac-2007-openness.html"
trackback:ping="http://www.w3.org/QA/sununga/mt-tb.cgi/92"
dc:title="TPAC 2007 - Openness of W3C Working Groups"
dc:identifier="http://www.w3.org/QA/2007/11/tpac-2007-openness.html"
dc:subject="Meetings"
dc:description="The participants of the W3C tech plenary are back from their lunch overlooking the gorgeous Charles river, to tackle the question of "openness". This is a development from a topic already raised today: a lot of people's lives and living..."
dc:creator="olivier Théreaux"
dc:date="2007-11-07T13:30:57+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/11/tpac-2007-html-5-xhtml-20-fun.html">« TPAC 2007 - HTML 5, XHTML 2.0, Future Formats</a> |
<a href="http://www.w3.org/QA/">Main</a>
| <a href="http://www.w3.org/QA/2007/11/tpac-2007-uri-extensibility.html">TPAC 2007 - URI-Based Extensibility: Benefits, Deviations, Lessons-Learned »</a>
</p>
<h2 class="entry-header">TPAC 2007 - Openness of W3C Working Groups</h2>
<div class="entry-body">
<p>The participants of the <a href="http://www.w3.org/2007/11/07-TechPlenAgenda.html">W3C tech plenary</a> are back from their lunch overlooking the gorgeous Charles river, to tackle the question of "openness".</p>
<p>This is a development from a topic already raised today: a lot of people's lives and living depend on Web technologies, and there is an enormous pool of opinions and contributions to the work now being done at W3C.</p>
<p><em>Update 2007-11-08</em> The <a href="http://disruptive-innovations.com/zoo/slides/20071107-TPAC2007/index.xhtml">slides of the panelists' presentations</a> are now available:</p>
<ul>
<li>Deborah Dahl (Conversational Technologies, HyperText <abbr title="coordination group">CG</abbr>, Multimodal Interaction <abbr title="working group">WG</abbr> chair.</li>
<li><a href="http://disruptive-innovations.com/zoo/slides/20071107-TPAC2007/ArtBarstow.pdf">Art Barstow</a> (Nokia, Web Application Formats WG chair)</li>
<li><a href="http://disruptive-innovations.com/zoo/slides/20071107-TPAC2007/IanHickson.txt">Ian Hickson</a> (Google, WHAT-WG, HTML WG, CSS WG, ...)</li>
<li><a href="http://disruptive-innovations.com/zoo/slides/20071107-TPAC2007/PaulCotton.pdf">Paul Cotton</a> (Microsoft, Web Services Policy WG chair)</li>
</ul>
<p>I get the impression that a lot is being crammed into this topic of "openness", which seems a bit dangerous. Is allowing public feedback openness? Is letting anyone with enough time and energy participate, in effect keeping out people not able to follow an enormous volume of discussion (in english only...) a real open process? As one contributor from the floor notes, open does not imply inclusive, and "openness" as a mostly US-communities-based mindset defines still has issues of language barriers, not reaching all the communities you need to reach. Also, are we talking about openness, or transparency, or both?</p>
<p>Terminology and definition of openness notwithstanding, getting more people to contribute does have a great appeal: this means more ideas, more pairs of eyes and brains to look at the specification. All this, so far, was covered by a W3C process ensuring public reviews of every specification at every stage of their maturity, but for many, this was not sufficient: there is a clear wish for direct involvement in the decision making. </p>
<p>This indeed has some serious advantages: in the development of our <a href="/Status">Open source tools</a>, I have observed that contributors react very differently when they feel they are "outside", as bug reporters for instance, and "inside", as part of the development team. Being part of the process means that you have a better chance of understanding it, and, sometimes, go and explain it to others. </p>
<p>In this way I feel that opening working groups to the public in a process similar to what has been done with the <a href="/html/wg">HTML Working Group</a> since March this year not only made a lot of people happy and brought up tons (too much too soon?) of ideas, but it also made a lot of people who may have kept a cynical outlook on the new HTML work, ambassadors of this work, genuinely excited by the work.</p>
<p>There are a lot of good concerns about making groups working on specifications more open, and as I write this, Art Barstow of Nokia, on stage, works on debunking them one by one...</p>
<ul>
<li>Openness brings too much input? that's the point, he thinks, to get feedback early, not too late. </li>
<li>IPR and licensing terms become a hairy subject with hundreds of participants, not always clear on their affiliations? Ensuring that patent policy commitment gets signed prior to joining the group would (should?) solve most of the issue. </li>
</ul>
<p>Does this mean that an open working group is the perfect solution, or are there technologies where a small task force, with frequent calls for feedback on the material they process, is more efficient? Standards veteran Paul Cotton tells us that you can have a very healthy community without needing a lot of "invited experts", if there is a solid submission with early support from a community. And eventually, you get down to a core group that actually does the work.</p>
<p>Which model will W3C adopt for its future? This is hard to tell. we know that the small group, public feedback scheme has worked well (and less well) for many specs in the past, whereas the recently born HTML working group, yet to have its first face-to-face meeting or publish a snapshot of its specification(s), is still an experiment.</p>
</div>
<div id="more" class="entry-more">
</div>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/olivier/">olivier Théreaux</a> on November 7, 2007 1:30 PM in <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/meetings/">Meetings</a>, <a href="http://www.w3.org/QA/archive/web_spotting/opinions_editorial/">Opinions &amp; Editorial</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/2007/11/tpac-2007-openness.html">Permalink</a>
| <a href="http://www.w3.org/QA/2007/11/tpac-2007-openness.html#comments">Comments (0)</a>
| <a href="http://www.w3.org/QA/2007/11/tpac-2007-openness.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="100" />
<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:39 $</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>