W3C WBS Home

Results of Questionnaire ISSUE-66 - Image Analysis Heuristics - Straw Poll for Objections

The results of this questionnaire are available to anybody.

This questionnaire was open from 2010-05-12 to 2010-05-19.

10 answers have been received.

Jump to results for question:

  1. Objections to the Change Proposal to Strike Paragraph
  2. Objections to the Change Proposal to Keep The Paragraph As Is
  3. Objections to the Change Proposal to Be More Explicit

1. Objections to the Change Proposal to Strike Paragraph

We have a Change Proposal to remove the image heuristics paragraph from the img element 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 Strike Paragraph
Ian Hickson The first paragraph of the rationale suggests that it is impossible to "recover from images with missing" alternative text. This is a straw-man argument, since the text in the specification (or proposed in one of the other change proposals) does not claim to enable user agents to "recover", merely allows user agents to make best-effort attempts to help users try to interpret such images.

The second paragraph continues arguing against this straw-man, citing software that has shown a remarkable ability to identify images, and claiming that it cannot solve all problems. Yet no claim is made that any software can solve _all_ problems. Any improvement in accessibility is better than no improvement, even if the improvement is only helpful in limited case. For example, OCR is a mature technology that can be of huge help to users unable to see images, as there is a large class of images that merely consist of styled text. Certainly, relying on OCR software is no substitute for real alternative text, but no claim is made that it is — quite the contrary in fact — and _any_ improvement is an improvement, even if it is not a complete substitute.

The change proposal continues in this vein throughout.

Removing these paragraphs removes helpful text that might inspire user agent implementers to improve their accessibility. This would be a mistake, and I object strongly to doing so. It is always better to be explicit in stating what user agents are allowed to do than to rely on user agent implementers making educated guesses about what is likely to be the most helpful solution.
Matthew May
Larry Masinter
Laura Carlson
Julian Reschke
Cynthia Shelly
David Singer
Gregory Rosmaita
Martin Kliehm
Krzysztof Maczyński

2. Objections to the Change Proposal to Keep The Paragraph As Is

We have a Change Proposal to keep the HTML5 specification as is. 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 Keep The Paragraph As Is
Ian Hickson
Matthew May The rationale states that the current text should remain because "OCR has existed for decades". To be blunt, so what? OCR is not a specification in itself; it's an entire field of research, consisting of an unknown number of algorithms and processes, many if not most of them proprietary and patented. If you specify it further, you run the risk of patent challenges. If you leave it as vague as it is now, you will end up with numerous implementations of questionable value to the user. The editor cites OCR as "one simple and unambiguously possible technique" when it is neither.

Anyway, the original reason the issue was raised was the even more nebulous "image analysis heuristics" passage, which remains in part in the current draft. UA developers don't need to be told in the specification that they're allowed to do more for the user. One would hope they've got ideas of their own.

I'm in favor of either fleshing this out in a way that everyone can agree is actually beneficial for accessibility, or striking it. This is a half-step which is worse than either of the other two options.
Larry Masinter see 4 below
Laura Carlson 1. The spec mixes directives to authors and directives to user agents, which will cause confusion.

2. It is not clearly noted that the cited paragraph [1] is not an escape clause for authors to get out of writing text alternatives. Some authors may take the paragraph as saying,

If:

User agents can help users with visual disabilities make sense of an image

then:

I don't have to worry about it.

3. Any User Agent image repair verbiage should be left to or vetted and coordinated with User Agent Accessibility Guidelines Working Group (UAWG). They are the domain experts. Any such verbiage in HTML5 would need to be carefully worded so the two specs are harmonized. Currently the two specs are out of sync.
Julian Reschke I don't think the paragraph is helpful; of course UAs can apply whatever techniques they want. Also, even if the UA can detect the contents of the image it still has no idea about the intent for including it.
Cynthia Shelly There is no need to have this informative text in the spec, and there is consensus among accessibility experts that this is not useful, confusing, and potentially harmful. The spec is already too long, so let's remove this unnecessary and problematic text.
David Singer
Gregory Rosmaita the discussion of potential repair techniques, including the image heuristics paragraph belongs in the HTML5 Alt Techniques document, which has been compiled by Steve Faulkner and which can be found at:

http://dev.w3.org/html5/alt-techniques/

i have an action item from the HTML Accessibility Task Force (http://www.w3.org/WAI/PF/HTML/track/actions/28) to create an Appendix to the Alt Techniques document, which would address both "potential repair" techniques such as image heuristics and crowd-sourcing; as well as a discussion of existing techniques that enable authors to provide meaningful descriptions when uploading images to aggregator sites, using the W3C's RDFPic open source software:

http://jigsaw.w3.org/rdfpic/
http://jigsaw.w3.org/rdfpic/rdfpic-2/rdfpic-readme.html

as described in the W3C technical recommendation, "Describing and Retrieving Photos using RDF and HTTP"

http://www.w3.org/TR/photo-rdf/
Martin Kliehm
Krzysztof Maczyński see my Objections to the Change Proposal to Be More Explicit

3. Objections to the Change Proposal to Be More Explicit

We have a Change Proposal to be more explicit about potential repair techniques. 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 Be More Explicit
Ian Hickson
Matthew May
Larry Masinter The kind of activity to tell people what possible repair technologies might be to help a user understand an image are completely out of scope for the W3C HTML Working Group. Fundamental to having a "Web Architecture" is to accept that "Architecture" actually means something, and that a fundamental component of any kind of system architecture, a fundamental requirement, is the concept of "modularity". The justifications for modularity are broad, deep, and found in any text book on complex systems design and should not require review here. Among them is the notion that technologies evolve at different rates.

The mechanisms for repair techniques are likely to evolve considerably, especially as "accessibility" extends to universal access on mobile devices and not just assistive technology for those with personal persistent visual impairment (I can't watch my screen while I'm driving). As these technologies evolve, any list of explicit potential repair techniques will become out of date, inappropriate, or even misleading.

This kind of material does not belong in the HTML specification because it should be allowed to evolve independently.
Laura Carlson Any User Agent image repair verbiage should be left to or vetted and coordinated with User Agent Accessibility Guidelines Working Group (UAWG). They are the domain experts. Any such verbiage in HTML5 would need to be carefully worded so the two specs are harmonized. Currently the two specs are out of sync.
Julian Reschke I don't see any value in listing even more techniques; it doesn't help *any* consumer of the spec.
Cynthia Shelly Repair techniques are out of scope for HTML5. The spec is already too long, let's not add more stuff. That said, this proposal is preferable to no changes.
David Singer
Gregory Rosmaita any such information belongs in the HTML5 Alt Techniques document, and should be mirrored by/aligned with WCAG 2.0

http://dev.w3.org/html5/alt-techniques/
http://www.w3.org/TR/WCAG20/
Martin Kliehm I don't think the repair techniques should be part of HTML5, but belongs into the domain of the WAI UAAG and ATAG.

I'd like to point out that the issue should be addressed by authoring tools. An authoring tool can and should recommend authors to provide an alternative text. They interact with humans, so there's amuch better chance to get a good result than technically guessing what a human meant. Authoring tools accessibility guidelines are maintained by WAI. HTML5 should not be redundant.
Krzysztof Maczyński The paragraph and suggested longer replacement are disproved of by notable accessibility experts and are widely believed to be far from consensus and from providing best possible guidance for implementors and authors. Also from this WG's angle it doesn't belong in HTML because of broader applicability. The right document to whose WG the collected suggestions should be passed for due treatment with expert attention (not excluding ours, just moving responsibility), refinement and probable inclusion is UAAG. In this way spec bloat (our big problem) will be avoided, concerns decoupled, architectural consistency maintained and independent evolvability assured. The same reasoning pretty much applies against the Change Proposal to Keep The Paragraph As Is.

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. Daniel Glazman <daniel.glazman@disruptive-innovations.com>
  19. Sean Hayes <sean.hayes@microsoft.com>
  20. Karl Dubost <karl@la-grange.net>
  21. David Baron <dbaron@dbaron.org>
  22. Lisa Seeman <lisa.seeman@zoho.com>
  23. Paul Cotton <Paul.Cotton@microsoft.com>
  24. Shane McCarron <shane@aptest.com>
  25. wu chou <wu.chou@huawei.com>
  26. Katsuhiko Momoi <momoi@google.com>
  27. Kangchan Lee <chan@w3.org>
  28. Roy Fielding <fielding@gbiv.com>
  29. Silvia Pfeiffer <silviapfeiffer1@gmail.com>
  30. Johnny Stenback <jst@mozilla.com>
  31. Janina Sajka <janina@rednote.net>
  32. Deborah Dahl <dahl@conversational-technologies.com>
  33. Michael Cooper <cooper@w3.org>
  34. Glenn Adams <glenn@skynav.com>
  35. Jonathan Jeon <hollobit@etri.re.kr>
  36. David Hyatt <hyatt@apple.com>
  37. Robin Berjon <robin@w3.org>
  38. WonSuk Lee <wonsuk.lee@etri.re.kr>
  39. Maciej Stachowiak <mjs@apple.com>
  40. Robert Accettura <robert@accettura.com>
  41. Jonathan Watt <jwatt@jwatt.org>
  42. Steve Faulkner <faulkner.steve@gmail.com>
  43. Emmanuelle Gutiérrez y Restrepo <emmanuelle@sidar.org>
  44. Patrick Lauke <redux@splintered.co.uk>
  45. David MacDonald <David100@sympatico.ca>
  46. Jack Jansen <jack@cwi.nl>
  47. Boris Zbarsky <bzbarsky@mit.edu>
  48. Kazuhito Kidachi <k-kidachi@mitsue.co.jp>
  49. Markku Hakkinen <mhakkinen@ets.org>
  50. Cyril Concolato <cyril.concolato@telecom-paristech.fr>
  51. Gez Lemon <glemon@paciellogroup.com>
  52. Pasquale Popolizio <p.popolizio@webprofession.com>
  53. Luca Mascaro <l.mascaro@webprofession.com>
  54. Markus Mielke <mmielke@microsoft.com>
  55. Jens Meiert <jens@meiert.com>
  56. Felix Sasaki <fsasaki@w3.org>
  57. Kazuyuki Ashimura <ashimura@w3.org>
  58. Daniel Burnett <dburnett@voxeo.com>
  59. Tomas Caspers <tomas@tomascaspers.de>
  60. Han Xu <collin@w3china.org>
  61. Sam Ruby <rubys@intertwingly.net>
  62. Jonas Sicking <jonas@sicking.cc>
  63. Mark Crawford <mark.crawford@sap.com>
  64. Doug Schepers <schepers@w3.org>
  65. Ian Fette <ifette@google.com>
  66. Michael[tm] Smith <mike@w3.org>
  67. Kelly Ford <kelly.ford@microsoft.com>
  68. Cameron McCormack <cam@mcc.id.au>
  69. Stefan Schnabel <stefan.schnabel@sap.com>
  70. Jirka Kosek <jirka@kosek.cz>
  71. Robert O'Callahan <robert@ocallahan.org>
  72. Travis Leithead <Travis.Leithead@microsoft.com>
  73. Youngsun Ryu <ysryu@samsung.com>
  74. Sierk Bornemann <sierkb@gmail.com>
  75. Martijn Wargers <martijn.martijn@gmail.com>
  76. Simon Pieters <simonp@opera.com>
  77. James Graham <james@hoppipolla.co.uk>
  78. Henri Sivonen <hsivonen@hsivonen.fi>
  79. Lachlan Hunt <lachlan.hunt@lachy.id.au>
  80. Krijn Hoetmer <w3c@qontent.nl>
  81. Markus Fischer <markus@fischer.name>
  82. Dean Edridge <dean@dean.kiwi>
  83. Channy Yun <channy@gmail.com>
  84. Shane Thacker <shanethacker@gmail.com>
  85. Bill Mason <billm@accessibleinter.net>
  86. Vilem Malek <murphy@malek.cz>
  87. Zhihong Mao <zhihong.mao@gmail.com>
  88. Benoit Piette <benoit.piette@gmail.com>
  89. Erik van Kempen <erikvankempen@gmail.com>
  90. Jude Robinson <dotcode+w3@gmail.com>
  91. Dimitri Glazkov <dglazkov@google.com>
  92. Diego La Monica <d.lamonica@webprofession.com>
  93. Nick Fitzsimons <w3@nickfitz.co.uk>
  94. Josh Lawton <w3c@joshlawton.com>
  95. Giovanni Gentili <giovanni.gentili@gmail.com>
  96. Adele Peterson <adele@apple.com>
  97. S Emerson <w3c@accretewebsolutions.ca>
  98. Morten Tollefsen <morten@medialt.no>
  99. Daniel Schattenkirchner <schattenkirchner.daniel@gmx.de>
  100. Edward O'Connor <eoconnor@apple.com>
  101. Justin Anthony Knapp <justinkoavf@gmail.com>
  102. Simon Myers <Smylers@stripey.com>
  103. Samuel Weinig <weinig@apple.com>
  104. Alexey Proskuryakov <ap@webkit.org>
  105. Alejandro Fernandez <alejandro@mediadvanced.com>
  106. Doug Jones <doug_b_jones@me.com>
  107. Marc Drumm <mdrumm@wcupa.edu>
  108. Danny Liang <danny.glue@gmail.com>
  109. Arne Johannessen <arne@thaw.de>
  110. Michael Puls II <shadow2531@gmail.com>
  111. Ron Reisor <ron@udel.edu>
  112. Marat Tanalin <mtanalin@yandex.ru>
  113. Andrew Norman <idonothaveacat@gmail.com>
  114. Craig Buckler <craigbuckler@gmail.com>
  115. Matthew Turvey <mcturvey@gmail.com>
  116. Dale Hudjik <dale.hudjik@gmail.com>
  117. James Cassell <w3c@cyberpear.com>
  118. Joseph D'Andrea <jdandrea@gmail.com>
  119. Pietro Russo <p.russo@webprofession.com>
  120. Moto Ishizawa <summerwind.jp+w3c@gmail.com>
  121. Chris Adams <chris@tuesdaybegins.com>
  122. Eric Carlson <eric.carlson@apple.com>
  123. Michael Turnwall <w3c@turnwall.net>
  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. John Foliot <john.foliot@deque.com>
  134. Shefik Macauley <allknightaccess@gmail.com>
  135. Joe Steele <steele@adobe.com>
  136. John Vernaleo <john@netpurgatory.com>
  137. Jeremy Keith <jeremy@adactio.com>
  138. Jedi Lin <JediLin@Gmail.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. Eliot Graff <eliotgra@microsoft.com>
  169. Frank Olivier <frank.olivier@microsoft.com>
  170. Jonathan Griffin <jgriffin@mozilla.com>
  171. Kris Krueger <krisk@microsoft.com>
  172. Erik Isaksen <erik_isaksen@hotmail.com>
  173. Daniel Davis <ddavis@w3.org>
  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@w3.org>
  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. Jeremy LaCivita <jeremy.lacivita@theplatform.com>
  223. Denis Ah-Kang <denis@w3.org>
  224. Alvar Laigna <laigna@gmail.com>
  225. Kunio Ito <kunio.ito@mail.rakuten.com>
  226. David Mays <david_mays@comcast.com>
  227. Michael Chen <michael_chen@cable.comcast.com>
  228. jongyoul Park <jongyoul@etri.re.kr>
  229. Adrian Roselli <roselli@algonquinstudios.com>
  230. Colin Ihrig <cjihrig@gmail.com>
  231. Kilroy Hughes <kilroy.hughes@microsoft.com>
  232. Reinaldo Ferraz <reinaldo@nic.br>
  233. Bill Mandel <bill.mandel@nbcuni.com>
  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. Xingrong Guo <guoxingrong@baidu.com>
  241. Jet Villegas <w3c@junglecode.net>
  242. Alexander Surkov <surkov.alexander@gmail.com>
  243. Hasan Savran <hsavran@kent.edu>
  244. Ben Dalton <bendalton@gmail.com>
  245. Marco Kotrotsos <Marco@mlabs.nl>
  246. Brian Blakely <anewpage.media@gmail.com>
  247. Eric VonColln <eric.voncolln@navy.mil>
  248. Jason Boyd <jason@pixelboxdesign.co.uk>
  249. Jungkee Song <jungkee.song@samsung.com>
  250. Huan Ren <renhuan@360.cn>
  251. Xitong Huang <stonehuang@tencent.com>
  252. Rayi Lei <leiyi@baidu.com>
  253. Daniel Austin <daniel.austin@grintech.net>
  254. David Dorwin <ddorwin@google.com>
  255. jiexuan gao <gaojiexuan@baidu.com>
  256. Mathew Marquis <mat@matmarquis.com>
  257. Xiaoqing Yang <yangxiaoqing@baidu.com>
  258. Aaron Colwell <acolwell@google.com>
  259. Alex Giladi <alex.giladi@huawei.com>
  260. Motomasa Futagami <Motomasa.Futagami@jp.sony.com>
  261. Kevin Streeter <kstreete@adobe.com>
  262. Christian Kaiser <kaiserc@google.com>
  263. François REMY <francois.remy.dev@outlook.com>
  264. Xuejian Li <lixuejian@baidu.com>
  265. Zuncheng Yang <yangzuncheng@baidu.com>
  266. Qianglong Zheng <zhengqianglong@baidu.com>
  267. Zhou Shen <shenzhou@baidu.com>
  268. Duoyi Wu <wuduoyi@baidu.com>
  269. Zheng Jia <jiazheng@baidu.com>
  270. Weifeng Feng <fengweifeng@baidu.com>
  271. Damin Hu <hudamin@baidu.com>
  272. Yang Liu <liuyang12@baidu.com>
  273. Zhixing Lei <leizhixing@baidu.com>
  274. Honggang Tang <tanghonggang@baidu.com>
  275. Kefeng Li <buaadallas@gmail.com>
  276. Xu Ma <maxu@baidu.com>
  277. Junzhong Liu <liujunzhong@baidu.com>
  278. Yusuke Maehama <maehama@tomo-digi.co.jp>
  279. Stefan Kaiser <stefan.kaiser@fokus.fraunhofer.de>
  280. Sheau Ng <Sheau.ng@nbcuni.com>
  281. Stefan Pham <stefan.pham@fokus.fraunhofer.de>
  282. Ami Fischman <fischman@google.com>
  283. Arnaud Braud <arnaud.braud@orange.com>
  284. Futomi Hatano <futomi.hatano@newphoria.co.jp>
  285. Bram Tullemans <tullemans@ebu.ch>
  286. Petr Peterka <ppeterka@verimatrix.com>
  287. lei wang <wanglei03@baidu.com>
  288. Milan Patel <Milan.Patel@huawei.com>
  289. Yiling Gu <guyiling@baidu.com>
  290. Yehuda Katz <wycats@gmail.com>
  291. Xueqing Huang <huangxueqing@baidu.com>
  292. Zefa Xiong <xiongzefa@baidu.com>
  293. shanglin chen <chenshanglin@baidu.com>
  294. Yaso Córdova <yaso@nic.br>
  295. Dongsheng Zhang <zhangdongsheng@baidu.com>
  296. Ping Wu <wuping02@baidu.com>
  297. Yao Tong <tongyao@baidu.com>
  298. Bin Chen <chenbin01@baidu.com>
  299. Youichi Takashima <takashima.youichi@lab.ntt.co.jp>
  300. Patrick Ladd <Pat_Ladd2@cable.comcast.com>
  301. Norifumi Kikkawa <norifumi.kikkawa@jp.sony.com>
  302. Billy Gregory <bgregory@paciellogroup.com>
  303. Hanrui Gao <gaohanrui@360.cn>
  304. Hao Jing <jh.jinghao@huawei.com>
  305. Glenn Deen <glenn.deen@nbcuni.com>
  306. Lei Wang <wanglei@baidu.com>
  307. Tom Handal <thandal@verimatrix.com>
  308. Tsutomu Ogasawara <tsutomu.ogasawara@mail.rakuten.com>
  309. Jose Segura <jose.segura@mail.rakuten.com>
  310. Pengcheng Guo <guopengcheng@baidu.com>
  311. Erika Doyle Navara <erika.doyle@microsoft.com>
  312. Tom Wiltzius <wiltzius@google.com>
  313. Pierre-Anthony Lemieux <pal@sandflow.com>
  314. Xie Jianhui <xiejianhui@baidu.com>
  315. Yujie Jiang <jiangyujie@baidu.com>
  316. Leslie Sikos <sikos@sikoswebconsulting.com.au>
  317. Mark Sadecki <mark.sadecki+w3c@gmail.com>
  318. Kazuhiko Takabayashi <kazuhiko.takabayashi@jp.sony.com>
  319. Brady Eidson <beidson@apple.com>
  320. Jerry Smith <jdsmith@microsoft.com>
  321. Michael Thornburgh <mthornbu@adobe.com>
  322. Cyril Rickelton-Abdi <cyril.rickelton-abdi@turner.com>
  323. Andrew Davis <andrew@diff.mx>
  324. Mick Hakobyan <mhakobyan@netflix.com>
  325. Mallory van Achterberg <stommepoes@stommepoes.nl>
  326. Vladimir Sinelnikov <sinelnikov@gmail.com>
  327. Chris Wong <huanghoujin@baidu.com>
  328. Yiliang LIU <liuyiliang@baidu.com>
  329. Hernan Beati <hernanbeati@gmail.com>
  330. mingqiang zhang <imcnan@gmail.com>
  331. yubo zhou <zhouyubo@360.cn>
  332. Ben Barber <barberboy@gmail.com>
  333. Matt Rakow <marakow@microsoft.com>
  334. Suzanne Taylor <Suzanne.Taylor@pearson.com>
  335. Grzegorz Babula <gbabula@gmail.com>
  336. Brian Kardell <hitchjs@gmail.com>
  337. xueliang fan <fanxueliang@baidu.com>
  338. Niels Thorwirth <nthorwirth@verimatrix.com>
  339. David Evans <david.evans@rd.bbc.co.uk>
  340. Danny O'Brien <danny@eff.org>
  341. Joseph Karr O'Connor <josephoconnor@mac.com>
  342. Seth Schoen <schoen@eff.org>
  343. Jamil Ellis <jamil.ellis@hbo.com>
  344. Jim Walsh <jim@jwalshcreative.com>
  345. Greg Davis <greg.davis@pearson.com>
  346. Gabino Alonso <gabinovincent@gmail.com>
  347. Sam Langdon <sam.langdon@hachette.co.uk>
  348. Michael Kelly <mkelly@mozilla.com>
  349. Xiaoqian Wu <xiaoqian@w3.org>
  350. Yue Min <minyue@baidu.com>
  351. Min Li <limin04@baidu.com>
  352. A.S. Krishnakumar <ask@avaya.com>
  353. Shijun Sun <shijuns@microsoft.com>
  354. Jonathan Neal <jonathantneal@gmail.com>
  355. Joanmarie Diggs <jdiggs@igalia.com>
  356. Pedro Xavier Jorge <pedro.xavierjorge@gmail.com>
  357. Akira Torii <Torii.Akira@bp.MitsubishiElectric.co.jp>
  358. So Vang <svang@nab.org>
  359. Nathalia Sautchuk Patrício <nathalia@nic.br>
  360. Deblyn prado <deblyn@nic.br>
  361. Vicente García Díaz <vicegd@live.com>
  362. Nolan Butcher <nolan.butcher@hbo.com>
  363. Shinya Maruyama <Shinya.Maruyama@jp.sony.com>
  364. RAVI CHANDRA RAVULAPATI <ravichandra480@gmail.com>
  365. John Riviello <john_riviello@comcast.com>
  366. yaolong wang <wangyaolong@baidu.com>
  367. Shun-ichi Sekiguchi <Sekiguchi.Shunichi@eb.MitsubishiElectric.co.jp>
  368. Tao Liang <liangtao01@baidu.com>
  369. Glenn Eguchi <geguchi@adobe.com>
  370. Hirofumi Nishikawa <Nishikawa.Hirofumi@cs.MitsubishiElectric.co.jp>
  371. Hiroyuki Yamada <Yamada.Hiroyuki@dn.MitsubishiElectric.co.jp>
  372. Chockalingam Muthian <chockam@gmail.com>
  373. Lukáš Čihák <lukas.cihak@mensa.cz>
  374. WOOGLAE KIM <wlkim@inswave.com>
  375. Min Ren <minren@tencent.com>
  376. Rustam Khashimkhodjaev <Rustam_Khashimkhodjaev@cable.comcast.com>
  377. Brian Evans <Brian.Evans@microsoft.com>
  378. Jason White <jjwhite@ets.org>
  379. Hyejin Lee <hjlee@html5forum.or.kr>
  380. Richard Grzeczkowski <richard_grzeczkowski@cable.comcast.com>
  381. Pascal Perrot <pascal.perrot@orange.com>
  382. Dongseong Hwang <dongseong.hwang@intel.com>
  383. Dapeng Liu <max.ldp@alibaba-inc.com>
  384. Matthew Wolenetz <wolenetz@google.com>
  385. Cory Heslip <cory_heslip@cable.comcast.com>
  386. Shaohang Yang <shaohang.ysh@alibaba-inc.com>
  387. Nirankush Panchbhai <npanch@microsoft.com>
  388. Pramod Patlolla <pramod.patlolla@turner.com>
  389. Cooper Pope <cooper.pope@turner.com>
  390. Grisha Lyukshin <glyuk@microsoft.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


Maintained by Laurent Carcone, from a development by Dominique Hazaël-Massieux (dom@w3.org) on an original design by Michael Sperberg-McQueen $Id: showv.php3,v 1.129 2015/07/01 16:13:23 kahan Exp $. Please send bug reports and request for enhancements to lcarcone@w3.org with w3t-sys@w3.org copied (if your mail client supports it, send mail directly to the right persons)