W3C WBS Home

Results of Questionnaire ISSUE-92: Re-write the Table section to remove extraneous material, and provide cleaner description - Straw Poll for Objections

The results of this questionnaire are available to anybody.

This questionnaire was open from 2010-09-28 to 2010-10-06.

8 answers have been received.

Jump to results for question:

  1. Objections to the Change Proposal to Replace table description and examples with alternate example.
  2. Objections to the Change Proposal to Move table and examples to a separate section

1. Objections to the Change Proposal to Replace table description and examples with alternate example.

We have a Change Proposal to Replace table description and examples with alternate example. If you have strong objections to adopting this Change Proposal, please state your objections below.

Keep in mind, you must actually state an objection, not merely cite someone else. If you feel that your objection has already been adequately addressed by someone else, then it is not necessary to repeat it.

Details

Responder Objections to the Change Proposal to Replace table description and examples with alternate example.
Ian Hickson I think it's highly inappropriate to use this change proposal as a "stealth" way to reintroduce the summary="" attribute, given how controversial that issue has been.
Tab Atkins Jr. This Change Proposal misses the entire point of the example in the spec, which is to illustrate a table which has a structure that *can't* be easily and automatically inferred by just naively inspecting the first row/columns for headers, and thus actually has need of a structural description.

Replacing the current spec example and text with the example and text given in this Change Proposal would remove important and useful information in return for a basic tutorial example.
John Foliot Chairs,

I find myself in a weird situation in that I actually support both proposals, but for different reasons.

I support the basic intent of the "Move table and examples to a separate section." proposal as it makes good sense to place this type of authoring guidance in its own location within the specification - technically it is the better editorial choice. Thus I endorse and support this proposal.

However, the 'counter proposal' is not really a counter proposal regarding the placement of the advisory text, but rather of the nature and content of that advisory text.

It is my belief that the advisory text supplied in this Change Proposal is, in general, better than the current text, and thus I support and endorse the adoption of this text over the current text, as the proposed revised text is technically superior to the current text, as it more closely resembles real world examples. I dismiss the editor's complaints that this is somehow a back-door re-insertion of the @summary attribute into HTML5, as @summary *is* in HTML5, albeit in a weird twilight zone of conformant but obsolete that triggers a warning (advisory) that there *may* be a better way to deliver this type of advice:

"Note: The summary attribute, <em>defined in the table section</em>, will also trigger a warning." - http://www.w3.org/TR/html5/obsolete.html#obsolete-but-conforming-features (emphasis mine)

However, since @summary *is* in HTML5 today, it is wholly appropriate to provide an example of how it is used, and how it should be written (if an author chooses to use this mechanism)

Thus my <em>strongest objection</em> is to linking two different change proposals as addressing the same problem, as they do not. If pressed by the Chairs to choose one over the other, then I must pick the "Change Proposal to Replace table description and examples with alternate example".
Laura Carlson
Henri Sivonen I object to this change proposal containing a resolution to ISSUE 32 as a rider.
Martin Kliehm The table example in the proposal is too complex. The text is more readable, but doesn't address large sections of what's included in the current spec text.

Concerning more readable text, I prefer the following text from the change proposal over the current two introductory paragraphs:

"The table element represents data with more than one dimension, organized into non-empty columns and rows. It is the primary component of the table model.

"Tables are used for data display, only, and should not be used for layout purposes. In particular, users of accessibility tools like screen readers are likely to find it difficult to navigate pages with tables used for layout."

Otherwise I can live with the text, given that the @summary discussion is a different issue.
Julian Reschke I support the change proposal, but:

- it should be clarified that inclusion of @summary depends on the outcome of ISSUE-32

- it may make sense to preserve some of the current text and move it somewhere else, as suggested by the other change proposal
David Singer While supportive of good examples, there are problems here:

- This proposal, in addition to changing the examples, changes the description of the table attribute in unrelated ways, and some of these changes are dubious. More specifically:
-- "The table element represents data with more than one dimension, organized into non-empty columns and rows." -- this replaces a must-level requirement not to have empty rows or columns with a phrase not expressed as a conformance requirement.
-- "Tables are used for data display, only, and should not be used for layout purposes." -- This sentence (replacing "Tables must not be used as layout aid") makes a false statement of fact about how tables *are* used in place of a conformance requirement, makes ungrammatical use of the comma, and replaces a must-level requirement with a should-level for no reason stated in the Change Proposal.
- The replacement text is more vague about when additional structural description for a table should be provided, using the vague "complex table" instead of the more informative "tables that consist of more than just a grid of cells with headers in the first row and headers in the first column, and for any table in general where the reader might have difficulty understanding the content"
- The replacement omits examples or even mention of additional techniques that could be used to describe a table's structure, besides the summary attribute. These techniques can be useful in a variety of circumstances, and omitting them makes the spec less useful to authors on the whole.

2. Objections to the Change Proposal to Move table and examples to a separate section

We have a Change Proposal to Move table and examples to a separate section. If you have strong objections to adopting this Change Proposal, please state your objections below.

Keep in mind, you must actually state an objection, not merely cite someone else. If you feel that your objection has already been adequately addressed by someone else, then it is not necessary to repeat it.

Details

Responder Objections to the Change Proposal to Move table and examples to a separate section
Ian Hickson
Tab Atkins Jr.
John Foliot Chairs,

I find myself in a weird situation in that I actually support both proposals, but for different reasons.

I support the basic intent of the "Move table and examples to a separate section." proposal as it makes good sense to place this type of authoring guidance in its own location within the specification - technically it is the better editorial choice. Thus I endorse and support this proposal.

However, the 'counter proposal' is not really a counter proposal regarding the placement of the advisory text, but rather of the nature and content of that advisory text.

It is my belief that the advisory text supplied in this Change Proposal is, in general, better than the current text, and thus I support and endorse the adoption of this text over the current text, as the proposed revised text is technically superior to the current text, as it more closely resembles real world examples. I dismiss the editor's complaints that this is somehow a back-door re-insertion of the @summary attribute into HTML5, as @summary *is* in HTML5, albeit in a weird twilight zone of conformant but obsolete that triggers a warning (advisory) that there *may* be a better way to deliver this type of advice:

"Note: The summary attribute, <em>defined in the table section</em>, will also trigger a warning." - http://www.w3.org/TR/html5/obsolete.html#obsolete-but-conforming-features (emphasis mine)

However, since @summary *is* in HTML5 today, it is wholly appropriate to provide an example of how it is used, and how it should be written (if an author chooses to use this mechanism)

Thus my <em>strongest objection</em> is to linking two different change proposals as addressing the same problem, as they do not. If pressed by the Chairs to choose one over the other, then I must pick the "Change Proposal to Replace table description and examples with alternate example".
Laura Carlson The current text is inappropriate and unclear. It should be replaced and a simple, clear, relevant example provided. The other change proposal does this very well.
Henri Sivonen
Martin Kliehm I object to this proposal since examples that are contained in the element description are more consistent with previous versions of HTML. It's easier for developers to find the example, as it is unlikely that someone will read the entire spec, but rather small sections found through search engines. Therefore it makes more sense to keep the information non-fragmented.
Julian Reschke I agree that the text should be moved somewhere else (with the details depending on the outcome of ISSUE-32).

I disagree that this is sufficient; there should be a good example for a table in the text (as suggested by the other change proposal)
David Singer

More details on responses

Non-responders

The following persons have not answered the questionnaire:

  1. Tantek Çelik <tantek@cs.stanford.edu>
  2. Patrick D F Ion <ion@ams.org>
  3. Richard Schwerdtfeger <schwer@us.ibm.com>
  4. Judy Brewer <jbrewer@w3.org>
  5. Wayne Carr <wayne.carr@linux.intel.com>
  6. Liam Quin <liam@w3.org>
  7. Richard Ishida <ishida@w3.org>
  8. Chris Wilson <cwilso@google.com>
  9. Wendy Chisholm <wendc@microsoft.com>
  10. David Carlisle <davidc@nag.co.uk>
  11. James Helman <jhelman@movielabs.com>
  12. Jim Allan <jimallan@tsbvi.edu>
  13. Chris Marrin <cmarrin@apple.com>
  14. Charles McCathie Nevile <chaals@yandex-team.ru>
  15. Philippe Le Hégaret <plh@w3.org>
  16. Don Brutzman <brutzman@nps.edu>
  17. T.V. Raman <raman@google.com>
  18. Cynthia Shelly <cyns@microsoft.com>
  19. Daniel Glazman <daniel.glazman@disruptive-innovations.com>
  20. Sean Hayes <sean.hayes@microsoft.com>
  21. Karl Dubost <karl@la-grange.net>
  22. Larry Masinter <masinter@adobe.com>
  23. David Baron <dbaron@dbaron.org>
  24. Lisa Seeman <lisa.seeman@zoho.com>
  25. Paul Cotton <Paul.Cotton@microsoft.com>
  26. Shane McCarron <shane@aptest.com>
  27. wu chou <wu.chou@huawei.com>
  28. Katsuhiko Momoi <momoi@google.com>
  29. Kangchan Lee <chan@w3.org>
  30. Roy Fielding <fielding@gbiv.com>
  31. Silvia Pfeiffer <silviapfeiffer1@gmail.com>
  32. Johnny Stenback <jst@mozilla.com>
  33. Janina Sajka <janina@rednote.net>
  34. Deborah Dahl <dahl@conversational-technologies.com>
  35. Michael Cooper <cooper@w3.org>
  36. Glenn Adams <glenn@skynav.com>
  37. Jonathan Jeon <hollobit@etri.re.kr>
  38. David Hyatt <hyatt@apple.com>
  39. Robin Berjon <robin@w3.org>
  40. WonSuk Lee <wonsuk11.lee@samsung.com>
  41. Maciej Stachowiak <mjs@apple.com>
  42. Robert Accettura <robert@accettura.com>
  43. Jonathan Watt <jwatt@jwatt.org>
  44. Steve Faulkner <faulkner.steve@gmail.com>
  45. Emmanuelle Gutiérrez y Restrepo <emmanuelle@sidar.org>
  46. Patrick Lauke <redux@splintered.co.uk>
  47. David MacDonald <David100@sympatico.ca>
  48. Jack Jansen <jack@cwi.nl>
  49. Boris Zbarsky <bzbarsky@mit.edu>
  50. Kazuhito Kidachi <k-kidachi@mitsue.co.jp>
  51. Markku Hakkinen <mhakkinen@ets.org>
  52. Cyril Concolato <cyril.concolato@telecom-paristech.fr>
  53. Gez Lemon <glemon@paciellogroup.com>
  54. Pasquale Popolizio <p.popolizio@webprofession.com>
  55. Luca Mascaro <l.mascaro@webprofession.com>
  56. Markus Mielke <mmielke@microsoft.com>
  57. Arun Ranganathan <arun@mozilla.com>
  58. Jens Meiert <jens@meiert.com>
  59. Felix Sasaki <fsasaki@w3.org>
  60. Kazuyuki Ashimura <ashimura@w3.org>
  61. Daniel Burnett <dburnett@voxeo.com>
  62. Tomas Caspers <tomas@tomascaspers.de>
  63. Han Xu <collin@w3china.org>
  64. Sam Ruby <rubys@intertwingly.net>
  65. Jonas Sicking <jonas@sicking.cc>
  66. Mark Crawford <mark.crawford@sap.com>
  67. Doug Schepers <schepers@w3.org>
  68. Ian Fette <ifette@google.com>
  69. Michael[tm] Smith <mike@w3.org>
  70. Kelly Ford <kelly.ford@microsoft.com>
  71. Cameron McCormack <cam@mcc.id.au>
  72. Jirka Kosek <jirka@kosek.cz>
  73. Robert O'Callahan <robert@ocallahan.org>
  74. Travis Leithead <Travis.Leithead@microsoft.com>
  75. Youngsun Ryu <ysryu@samsung.com>
  76. Sierk Bornemann <sierkb@gmail.com>
  77. Martijn Wargers <martijn.martijn@gmail.com>
  78. Simon Pieters <simonp@opera.com>
  79. James Graham <james@hoppipolla.co.uk>
  80. Lachlan Hunt <lachlan.hunt@lachy.id.au>
  81. Krijn Hoetmer <w3c@qontent.nl>
  82. Markus Fischer <markus@fischer.name>
  83. Dean Edridge <dean@dean.kiwi>
  84. Channy Yun <channy@gmail.com>
  85. Shane Thacker <shanethacker@gmail.com>
  86. Bill Mason <billm@accessibleinter.net>
  87. Vilem Malek <murphy@malek.cz>
  88. Zhihong Mao <zhihong.mao@gmail.com>
  89. Benoit Piette <benoit.piette@gmail.com>
  90. Erik van Kempen <erikvankempen@gmail.com>
  91. Jude Robinson <dotcode+w3@gmail.com>
  92. Dimitri Glazkov <dglazkov@google.com>
  93. Diego La Monica <d.lamonica@webprofession.com>
  94. Nick Fitzsimons <w3@nickfitz.co.uk>
  95. Josh Lawton <w3c@joshlawton.com>
  96. Giovanni Gentili <giovanni.gentili@gmail.com>
  97. Adele Peterson <adele@apple.com>
  98. S Emerson <w3c@accretewebsolutions.ca>
  99. Morten Tollefsen <morten@medialt.no>
  100. Daniel Schattenkirchner <schattenkirchner.daniel@gmx.de>
  101. Edward O'Connor <eoconnor@apple.com>
  102. Justin Anthony Knapp <justinkoavf@gmail.com>
  103. Simon Myers <Smylers@stripey.com>
  104. Samuel Weinig <weinig@apple.com>
  105. Alexey Proskuryakov <ap@webkit.org>
  106. Alejandro Fernandez <alejandro@mediadvanced.com>
  107. Doug Jones <doug_b_jones@me.com>
  108. Marc Drumm <mdrumm@wcupa.edu>
  109. Danny Liang <danny.glue@gmail.com>
  110. Arne Johannessen <arne@thaw.de>
  111. Michael Puls II <shadow2531@gmail.com>
  112. Ron Reisor <ron@udel.edu>
  113. Marat Tanalin <mtanalin@yandex.ru>
  114. Andrew Norman <idonothaveacat@gmail.com>
  115. Craig Buckler <craigbuckler@gmail.com>
  116. Matthew Turvey <mcturvey@gmail.com>
  117. Dale Hudjik <dale.hudjik@gmail.com>
  118. James Cassell <w3c@cyberpear.com>
  119. Joseph D'Andrea <jdandrea@gmail.com>
  120. Pietro Russo <p.russo@webprofession.com>
  121. Moto Ishizawa <summerwind.jp+w3c@gmail.com>
  122. Chris Adams <chris@tuesdaybegins.com>
  123. Eric Carlson <eric.carlson@apple.com>
  124. Don Kiely <donkiely@computer.org>
  125. Robert Marshall <rdm@rdmsoft.com>
  126. Jane Lee <applegoddess@gmail.com>
  127. David Child <dave@addedbytes.com>
  128. Mark DuBois <Mark@webprofessionals.org>
  129. David Choi <daaave@gmail.com>
  130. David Bills <w3@dfbills.com>
  131. Nik Thierry <me@thisemail.ca>
  132. Andrew Ramsden <andrew@irama.org>
  133. Shefik Macauley <allknightaccess@gmail.com>
  134. Joe Steele <steele@adobe.com>
  135. John Vernaleo <john@netpurgatory.com>
  136. Jeremy Keith <jeremy@adactio.com>
  137. Jedi Lin <JediLin@Gmail.com>
  138. Manu Sporny <msporny@digitalbazaar.com>
  139. Kenny Johar <kensingh@microsoft.com>
  140. Jon Hughes <jon@phazm.com>
  141. Anssi Kostiainen <anssi.kostiainen@intel.com>
  142. Samuel Santos <samaxes@gmail.com>
  143. Dean Jackson <dino@apple.com>
  144. Mohammed DADAS <mohammed.dadas@orange.com>
  145. Sally Cain <sally.cain@rnib.org.uk>
  146. Dan Romascanu <dromasca@avaya.com>
  147. David Bolter <dbolter@mozilla.com>
  148. Chris Double <cdouble@mozilla.com>
  149. Jeanne F Spellman <jeanne@w3.org>
  150. James Craig <jcraig@apple.com>
  151. MING JIN <ming.jin.web@gmail.com>
  152. Leonard Rosenthol <lrosenth@adobe.com>
  153. Philip Jägenstedt <philipj@opera.com>
  154. Adrian Bateman <adrianba@microsoft.com>
  155. Dionysios Synodinos <synodinos@gmail.com>
  156. Jean-Pierre EVAIN <evain@ebu.ch>
  157. Mark Pilgrim <pilgrim@google.com>
  158. Matt Lee <mattl@cnuk.org>
  159. Magnus Olsson <magnus.olsson@ericsson.com>
  160. Chris Pearce <cpearce@mozilla.com>
  161. Dzung Tran <dzung.d.tran@intel.com>
  162. Mark Miller <erights@google.com>
  163. Andrew Wilson <atwilson@google.com>
  164. Per-Erik Brodin <per-erik.brodin@ericsson.com>
  165. Ojan Vafai <ojan@chromium.org>
  166. Martin McEvoy <martin@weborganics.co.uk>
  167. Aryeh Gregor <ayg@aryeh.name>
  168. Gavin Carothers <gavin@carothers.name>
  169. Eliot Graff <eliotgra@microsoft.com>
  170. Frank Olivier <frank.olivier@microsoft.com>
  171. Jonathan Griffin <jgriffin@mozilla.com>
  172. Kris Krueger <krisk@microsoft.com>
  173. Erik Isaksen <erik_isaksen@hotmail.com>
  174. Anders Bondehagen <anders@bondehagen.com>
  175. Steven Pemberton <Steven.Pemberton@cwi.nl>
  176. Raul Hudea <rhudea@adobe.com>
  177. Raghavan Gurumurthy <raghavan@adobe.com>
  178. Mayank Kumar <mayankk@adobe.com>
  179. Monikandan S <smonikan@adobe.com>
  180. Dragos Georgita <dgeorgit@adobe.com>
  181. Christopher Bank <cbank@adobe.com>
  182. Dominik Tomaszuk <ddooss@wp.pl>
  183. Ole Riesenberg <or@oleriesenberg.com>
  184. Takuya Oikawa <takuya@google.com>
  185. Jatinder Mann <jmann@microsoft.com>
  186. Robert Stern <rstern@gmail.com>
  187. Dean Leigh <dean.leigh@deanleigh.co.uk>
  188. Eihab Ibrahim <eihabibrahim@gmail.com>
  189. Kensaku KOMATSU <kensaku.komatsu@gmail.com>
  190. Ian Pouncey <w3c@ipouncey.co.uk>
  191. Jer Noble <jer.noble@apple.com>
  192. Léonie Watson <lwatson@paciellogroup.com>
  193. Masatomo Kobayashi <mstm@jp.ibm.com>
  194. Grant Simpson <glsimpso@gmail.com>
  195. Peter Beverloo <beverloo@google.com>
  196. Andrew Scherkus <scherkus@google.com>
  197. Greg Johnson <greg.johnson@gmail.com>
  198. Martijn Croonen <martijn@martijnc.be>
  199. John Jansen <johnjan@microsoft.com>
  200. Stanley Manoski <manoski@mitre.org>
  201. Jonas Schneider <js.sokrates@gmail.com>
  202. Yosuke Funahashi <yosuke@funahashi.cc>
  203. Mounir Lamouri <mlamouri@google.com>
  204. Mike Amundsen <mamund@yahoo.com>
  205. Tony Gentilcore <tonyg@google.com>
  206. Jacob Rossi <Jacob.Rossi@microsoft.com>
  207. Joseph Pecoraro <pecoraro@apple.com>
  208. Othmane Benyoucef <othmane_benyoucef@hotmail.com>
  209. Shoko Okuma <okuma@tomo-digi.co.jp>
  210. Fumitaka Watanabe <fwtnb@tomo-digi.co.jp>
  211. Yoshimitsu Tsurimaki <tsurimaki@tomo-digi.co.jp>
  212. Bob Lund <b.lund@cablelabs.com>
  213. Tatsuya Igarashi <Tatsuya.Igarashi@jp.sony.com>
  214. John Simmons <johnsim@microsoft.com>
  215. Mathias Bynens <mathias@qiwi.be>
  216. Mark Watson <watsonm@netflix.com>
  217. Clarke Stevens <c.stevens@cablelabs.com>
  218. Mark Vickers <mark_vickers@cable.comcast.com>
  219. Sree Kotay <Sree_Kotay@cable.comcast.com>
  220. Cameron Jones <cmhjones@gmail.com>
  221. Rik Cabanier <Cabanier@adobe.com>
  222. Denis Ah-Kang <denis@w3.org>
  223. Alvar Laigna <laigna@gmail.com>
  224. Kunio Ito <kunio.ito@mail.rakuten.com>
  225. David Mays <david_mays@comcast.com>
  226. Michael Chen <michael_chen@cable.comcast.com>
  227. jongyoul Park <jongyoul@etri.re.kr>
  228. Adrian Roselli <roselli@algonquinstudios.com>
  229. Colin Ihrig <cjihrig@gmail.com>
  230. Kilroy Hughes <kilroy.hughes@microsoft.com>
  231. Reinaldo Ferraz <reinaldo@nic.br>
  232. Bill Mandel <bill.mandel@nbcuni.com>
  233. Jonas Jacek <w3c@jonas.me>
  234. Eva Lingyun Jing <jinglingyun@baidu.com>
  235. GANG LIANG <gang.liang@huawei.com>
  236. Ryosuke Niwa <rniwa@apple.com>
  237. Jason Kiss <jason@accessibleculture.org>
  238. Gian Luca Marroni <gmarroni@libero.it>
  239. Ian Devlin <ian@iandevlin.com>
  240. Greg Billock <gbillock@google.com>
  241. Xingrong Guo <guoxingrong@baidu.com>
  242. Jet Villegas <w3c@junglecode.net>
  243. Anas R. <anas.ram@gmail.com>
  244. Alexander Surkov <surkov.alexander@gmail.com>
  245. wilfred nas <wilfred@wnas.nl>
  246. Hasan Savran <hsavran@kent.edu>
  247. Ben Dalton <bendalton@gmail.com>
  248. Marco Kotrotsos <Marco@mlabs.nl>
  249. Brian Blakely <anewpage.media@gmail.com>
  250. Eric VonColln <eric.voncolln@navy.mil>
  251. Jason Boyd <jason@pixelboxdesign.co.uk>
  252. Jerry Jiang <jerry@ucweb.com>
  253. Jungkee Song <jungkee.song@samsung.com>
  254. Huan Ren <renhuan@360.cn>
  255. Xitong Huang <stonehuang@tencent.com>
  256. Songnan Ran <ransn@ucweb.com>
  257. Rayi Lei <leiyi@baidu.com>
  258. Daniel Austin <daniel.austin@grintech.net>
  259. David Dorwin <ddorwin@google.com>
  260. jiexuan gao <gaojiexuan@baidu.com>
  261. Mathew Marquis <mat@matmarquis.com>
  262. Xiaoqing Yang <yangxiaoqing@baidu.com>
  263. Aaron Colwell <acolwell@google.com>
  264. Alex Giladi <alex.giladi@huawei.com>
  265. Motomasa Futagami <Motomasa.Futagami@jp.sony.com>
  266. Kevin Streeter <kstreete@adobe.com>
  267. jean-baptiste henry <j.henry.ext@viaccess.com>
  268. Christian Kaiser <kaiserc@google.com>
  269. François REMY <francois.remy.dev@outlook.com>
  270. Xuejian Li <lixuejian@baidu.com>
  271. Zuncheng Yang <yangzuncheng@baidu.com>
  272. Qianglong Zheng <zhengqianglong@baidu.com>
  273. Zhou Shen <shenzhou@baidu.com>
  274. Duoyi Wu <wuduoyi@baidu.com>
  275. Zheng Jia <jiazheng@baidu.com>
  276. Weifeng Feng <fengweifeng@baidu.com>
  277. Damin Hu <hudamin@baidu.com>
  278. Yang Liu <liuyang12@baidu.com>
  279. Zhixing Lei <leizhixing@baidu.com>
  280. Honggang Tang <tanghonggang@baidu.com>
  281. Kefeng Li <buaadallas@gmail.com>
  282. Manyoung Cho <manyoung@w3labs.kr>
  283. Xu Ma <maxu@baidu.com>
  284. Junzhong Liu <liujunzhong@baidu.com>
  285. Yusuke Maehama <maehama@tomo-digi.co.jp>
  286. Stefan Kaiser <stefan.kaiser@fokus.fraunhofer.de>
  287. Sheau Ng <Sheau.ng@nbcuni.com>
  288. Stefan Pham <stefan.pham@fokus.fraunhofer.de>
  289. Ami Fischman <fischman@google.com>
  290. Arnaud Braud <arnaud.braud@orange.com>
  291. Futomi Hatano <futomi.hatano@newphoria.co.jp>
  292. Bram Tullemans <tullemans@ebu.ch>
  293. Petr Peterka <ppeterka@verimatrix.com>
  294. lei wang <wanglei03@baidu.com>
  295. Milan Patel <Milan.Patel@huawei.com>
  296. Yiling Gu <guyiling@baidu.com>
  297. Yehuda Katz <wycats@gmail.com>
  298. Xueqing Huang <huangxueqing@baidu.com>
  299. Zefa Xiong <xiongzefa@baidu.com>
  300. shanglin chen <chenshanglin@baidu.com>
  301. Yaso Córdova <yaso@nic.br>
  302. Dongsheng Zhang <zhangdongsheng@baidu.com>
  303. Ping Wu <wuping02@baidu.com>
  304. Yao Tong <tongyao@baidu.com>
  305. Bin Chen <chenbin01@baidu.com>
  306. Youichi Takashima <takashima.youichi@lab.ntt.co.jp>
  307. Patrick Ladd <Pat_Ladd2@cable.comcast.com>
  308. Norifumi Kikkawa <norifumi.kikkawa@jp.sony.com>
  309. Billy Gregory <bgregory@paciellogroup.com>
  310. Hanrui Gao <gaohanrui@360.cn>
  311. Hao Jing <jh.jinghao@huawei.com>
  312. Glenn Deen <glenn.deen@nbcuni.com>
  313. Lei Wang <wanglei@baidu.com>
  314. Tom Handal <thandal@verimatrix.com>
  315. Tsutomu Ogasawara <tsutomu.ogasawara@mail.rakuten.com>
  316. Jose Segura <jose.segura@mail.rakuten.com>
  317. Pengcheng Guo <guopengcheng@baidu.com>
  318. Erika Doyle Navara <erika.doyle@microsoft.com>
  319. Tom Wiltzius <wiltzius@google.com>
  320. Pierre-Anthony Lemieux <pal@sandflow.com>
  321. Xie Jianhui <xiejianhui@baidu.com>
  322. Yujie Jiang <jiangyujie@baidu.com>
  323. Leslie Sikos <sikos@sikoswebconsulting.com.au>
  324. Mark Sadecki <mark.sadecki+w3c@gmail.com>
  325. Kazuhiko Takabayashi <kazuhiko.takabayashi@jp.sony.com>
  326. Brady Eidson <beidson@apple.com>
  327. Reimundo Garcia <reimundo.garcia@hbo.com>
  328. Jerry Smith <jdsmith@microsoft.com>
  329. Michael Thornburgh <mthornbu@adobe.com>
  330. Cyril Rickelton-Abdi <cyril.rickelton-abdi@turner.com>
  331. Andrew Davis <andrew@diff.mx>
  332. Mick Hakobyan <mhakobyan@netflix.com>
  333. Angela Ricci <contact@thecodeplayground.net>
  334. Mallory van Achterberg <stommepoes@stommepoes.nl>
  335. Vladimir Sinelnikov <sinelnikov@gmail.com>
  336. Chris Wong <huanghoujin@baidu.com>
  337. Yiliang LIU <liuyiliang@baidu.com>
  338. David Sleight <hello@stuntbox.com>
  339. Hernan Beati <hernanbeati@gmail.com>
  340. mingqiang zhang <imcnan@gmail.com>
  341. yubo zhou <zhouyubo@360.cn>
  342. Ben Barber <barberboy@gmail.com>
  343. Suzanne Taylor <Suzanne.Taylor@pearson.com>
  344. Grzegorz Babula <gbabula@gmail.com>
  345. xueliang fan <fanxueliang@baidu.com>
  346. Mikio Sasaki <Sasaki.Mikio@bc.MitsubishiElectric.co.jp>
  347. Niels Thorwirth <nthorwirth@verimatrix.com>
  348. David Evans <david.evans@rd.bbc.co.uk>
  349. Danny O'Brien <danny@eff.org>
  350. Joseph Karr O'Connor <josephoconnor@mac.com>
  351. Seth Schoen <schoen@eff.org>
  352. Jamil Ellis <jamil.ellis@hbo.com>
  353. Jim Walsh <jim@jwalshcreative.com>
  354. Greg Davis <greg.davis@pearson.com>
  355. Gabino Alonso <gabinovincent@gmail.com>
  356. Sam Langdon <sam.langdon@hachette.co.uk>
  357. Michael Kelly <mkelly@mozilla.com>
  358. Xiaoqian Wu <xiaoqian@w3.org>
  359. Yue Min <minyue@baidu.com>
  360. Min Li <limin04@baidu.com>
  361. A.S. Krishnakumar <ask@avaya.com>
  362. Shijun Sun <shijuns@microsoft.com>
  363. Jonathan Neal <jonathantneal@gmail.com>
  364. Joanmarie Diggs <jdiggs@igalia.com>
  365. Kei Gomita <Gomita.Kei@db.MitsubishiElectric.co.jp>
  366. Pedro Xavier Jorge <pedro.xavierjorge@gmail.com>
  367. diyar naozary <diyar.naozary@yahoo.com>
  368. Akira Torii <Torii.Akira@bp.MitsubishiElectric.co.jp>
  369. Tetsushi Matsuda <Matsuda.Tetsushi@dh.MitsubishiElectric.co.jp>
  370. So Vang <svang@nab.org>
  371. Ben Peters <ben.peters@microsoft.com>
  372. Amy Brown <hello@amybrowndesign.com>
  373. Nathalia Sautchuk Patrício <nathalia@nic.br>
  374. Deblyn prado <deblyn@nic.br>
  375. Vicente García Díaz <vicegd@live.com>
  376. Nan Jiang <ayajiang@hotmail.com>
  377. Nolan Butcher <nolan.butcher@hbo.com>
  378. Shinya Maruyama <Shinya.Maruyama@jp.sony.com>
  379. RAVI CHANDRA RAVULAPATI <ravichandra480@gmail.com>
  380. Yusuke Yokosuka <Yokosuka.Yusuke@bx.MitsubishiElectric.co.jp>
  381. John Riviello <john_riviello@comcast.com>
  382. yaolong wang <wangyaolong@baidu.com>
  383. Shun-ichi Sekiguchi <Sekiguchi.Shunichi@eb.MitsubishiElectric.co.jp>
  384. Tao Liang <liangtao01@baidu.com>
  385. Glenn Eguchi <geguchi@adobe.com>
  386. Hirofumi Nishikawa <Nishikawa.Hirofumi@cs.MitsubishiElectric.co.jp>
  387. Hiroyuki Yamada <Yamada.Hiroyuki@dn.MitsubishiElectric.co.jp>
  388. Chockalingam Muthian <chockam@gmail.com>
  389. Lukáš Čihák <lukas.cihak@mensa.cz>
  390. Anatoly Shikolay <shikolay@gmail.com>
  391. WOOGLAE KIM <wlkim@inswave.com>
  392. Min Ren <minren@tencent.com>
  393. Rustam Khashimkhodjaev <Rustam_Khashimkhodjaev@cable.comcast.com>
  394. Brian Evans <Brian.Evans@microsoft.com>
  395. Jason White <jjwhite@ets.org>
  396. Richard Grzeczkowski <richard_grzeczkowski@cable.comcast.com>

Send an email to all the non-responders.


Compact view of the results / list of email addresses of the responders

WBS home / Questionnaires / WG questionnaires / Answer this questionnaire


Completed and maintained by Dominique Hazaël-Massieux (dom@w3.org) on an original design by Michael Sperberg-McQueen $Id: showv.php3,v 1.124 2014-10-06 13:46:23 dom Exp $. Please send bug reports and request for enhancements to dom@w3.org with w3t-sys@w3.org copied (if your mail client supports it, send mail directly to the right persons)