W3C WBS Home

Results of Questionnaire Release "HTML 5 differences from HTML 4" as a W3C Working Draft?

The results of this questionnaire are available to anybody.

This questionnaire was open from 2007-06-26 to 2007-07-03.

86 answers have been received.

Jump to results for question:

  1. Release "HTML 5 differences from HTML 4" as a W3C Working Draft?

1. Release "HTML 5 differences from HTML 4" as a W3C Working Draft?

Shall we release HTML 5 differences from HTML 4 as a W3C Working Draft? Specifically, version 1.25 2007/06/25 14:50:30 plus any publication-related changes (e.g. status section, typos, broken links) agreed by Anne van Kesteren and Dan Connolly.

If you're not familiar with the process of Working Draft publication, see the list of W3C working drafts, section 7.4.1 First Public Working Draft of the Process document, and the heartbeat requirement.

Section 3.3 Consensus in the W3C process defines consensus as a "substantial number" in support of a proposal and no formal objections. In this survey, you may indicate disagreement without formally objecting. An individual who registers a Formal Objection should cite technical arguments and propose changes that would remove the Formal Objection. Please put your arguments (or a pointer to your arguments) in the rationale field.


ChoiceAll responders
Yes, agree 65
Abstain 11
No, disagree 3
Formally Object 5

(2 responses didn't contain an answer to this question)


Responder Release "HTML 5 differences from HTML 4" as a W3C Working Draft?RationaleComments
W3C/MIT (Dan Connolly <dckc@madmode.com>) Yes, agree
Opera Software AS (Anne van Kesteren <annevk@annevk.nl>) Yes, agree I think we should try getting the main specification out soon too.
Apple, Inc. (Maciej Stachowiak <mjs@apple.com>) Yes, agree This seems like the best way to satisfy the heartbeat requirement.
Google, Inc. (Ian Hickson <ian@hixie.ch>) Yes, agree
Queensland University of Technology (Michael Lawley <Michael.Lawley@csiro.au>) Yes, agree Paragraph 1 of section 2 should contain a reference to the cited example esoteric feature, eg http://www.w3.org/TR/html4/appendix/notes.html#h-B.3.7
International Webmasters Association (IWA) (Diego La Monica <d.lamonica@webprofession.com>) Yes, agree
Mozilla Foundation (Gervase Markham <gerv@mozilla.org>) Yes, agree
W3C Invited Experts
Orange (Stéphane Deschamps <stephane.deschamps@orange.com>) Yes, agree I'm late in joining the group but still will want to advocate for maintaining the table@summary attribute - and may have a few more remarks. Yet, as Lachlan Hunt says, it does reflect HTML 5 in its current state of work: not final.
mTLD Top Level Domain Limited (Stephen Stewart <sstewart@mtld.mobi>) Yes, agree Fulfils the "Heartbeat" requirement.Publishing "HTML 5 differences from HTML 4" is the best way for anyone familiar with HTML 4 to see the current status of the work of this group.
Invited Experts without Member Access
Patrick Garies (Patrick Garies <w3c-5@patrick.dark.name>) Abstain I agree with Laura Carlson et al that there should be stated rationale for breaks from HTML4, particularly for dropped accessibility attributes and the redefinition of existing semantics.

Section 2.2 should have errors fixed. “DOCTYPEs from earlier versions of HTML were longer because the HTML language was SGML based and therefore required a reference to a DTD.” should have the word “needed” after “longer” and there should be a hyphen between “SGML” and “based”.
Thomas Broyer (Thomas Broyer <t.broyer@ltgt.net>) Yes, agree
Dylan Smith (Dylan Smith <qstage@cox.net>) No, disagree I don't the the doc has been reviewed enough by the WG to 'publish' as such, yet.
Sec 7.4.1 says: "The publication of the First Public Working Draft is a signal to the community to begin reviewing the document." If we're not anywhere near finishing a first review of this doc, why publish it?
It may well be a good starting point for discussion, but there seem to be a number of contentious issues that should be resolved, or at the very least documented prior to publication.
Sander van Lambalgen (Sander van Lambalgen <w3c@have-skill.com>) Yes, agree
James Cassell (James Cassell <w3c@cyberpear.com>) Abstain There are some good arguments as to why we should not release this as a working draft, namely, that the design principles document hasn't been released yet.
Dannii Willis (Dannii Willis <curiousdannii@gmail.com>) Yes, agree
Geoff Richards (Geoff Richards <geoff@laxan.com>) Yes, agree
M. Jackson Wilkinson (M. Jackson Wilkinson <jackw-w3c@jounce.net>) Yes, agree
Serdar Kiliç (Serdar Kiliç <serdar@kilic.net>) Yes, agree
Jeff Schiller (Jeff Schiller <codedread@gmail.com>) Yes, agree I agree on the condition that http://dev.w3.org/cvsweb/~checkout~/html5/html4-differences/Overview.html#ref-html5 be cleaned up two only specify one set of HTML5 and WebForms documents.
Joshua Sled (Joshua Sled <jsled@asynchronous.org>) Yes, agree The draft is a useful, concise overview, which should inform future review and discussion.
Michael Puls II (Michael Puls II <shadow2531@gmail.com>) Yes, agree
Arne Johannessen (Arne Johannessen <arne@thaw.de>) Yes, agree While a risk of creating a wrong impression about HTML 5 exists, this document is sufficiently clear about its status that the advantages of publishing it outweigh this risk by far.
Terry Morris (Terry Morris <MorrisW3C@gmail.com>) Abstain The document contains rationale for dropping presentational elements and attributes. I believe that it is also necessary to provide rationale for dropping the accessibility-related attributes.
Alejandro Fernandez (Alejandro Fernandez <alejandro@mediadvanced.com>) Yes, agree
Theresa O'Connor (Theresa O'Connor <eoconnor@apple.com>) Yes, agree
Daniel Schattenkirchner (Daniel Schattenkirchner <schattenkirchner.daniel@gmx.de>) Yes, agree
Doug Wright (Doug Wright <douglas.wright@pre-school.org.uk>) Yes, agree
Robert Burns (Robert Burns <rob@robburns.com>) Formally Object I do not understand why we would start with this document for fulfill the heartbeat rule rather than the "Design Principles". Publishing a document that lays out the differences between HTML4 and HTML5 implies that this WG done some work on HTML5. That work has only just begun and reviews are scheduled for completion throughout this month. I certainly could imagine a differences document or even a first working draft itself ready for the next heartbeat in three months.The hearbeat rule aside (which would be satisfied more easily, more quickly and less painfully with the principles document), making the differences document available to the public as a draft of this WG would be understood by our audience as reflecting the work of this WG. It does not because that work is only now just beginning.

The document is already available for public revirew at <http://wiki.whatwg.org/wiki/Differences_from_HTML4>, so we do not provide any more information by publishing than is already available. I would have no objection to adding a link to the WhatWG publication from our front page along with a link to the WhatWG HTML5 draft as long as it was made clear that those documents are where the HTML WG is beginning its preparation of a draft.

In summary my formal objection to publishing this document are due to: 1) publishing this document to fulfill the heartbeat rule is unnecessary since we have the "Design Principles" document to publish. 2) The public will misunderstand the meaning of us re-publishing the "differences" document, thinking that it reflects the work and endorsement of the HTML WG. 3) The document is already available for public information through the WhatWG. 4) The work of the HTML WG has not yet been completed to a sufficient degree to even determine what differences there will be between HTML4 and HTML5 (even for a draft). 5) We are having problems communicating the issues conveyed in the "differences" document within the WG itself. Publishing that to a general audience with all of its ambiguity will only exhibit the same issue, compounded tremendously.

I would remove this formal objection once: 1) We have published our design principles (at least in draft form) 2) the WG member reviews have been filed and the WG editors have had time to digest and incorporate changes (as they deem necessary) into the draft 3) The ambiguities in the document are dealt with. In particular there are ambiguities about what it means to drop/omit/deprecate a facility of the language. Many of those omitted facilities are lumped together whether they were actually actively omitted or have not yet been considered. Ambiguities over the rationale for omitting (particularly semantic) facilities have not yet been added to the document.
Philip TAYLOR (Philip TAYLOR <P.Taylor@Rhul.Ac.Uk>) Formally Object 1) Approximately five times as many respondents favoured publishing the design principles first as favoured publishing "HTML 5 differences from HTML 4"; given the W3C's position on consensus, it is clear that the first document to be agreed and published should be one outlining the design principles on which HTML 5 is to be based.

2) It will not be possible to publish anything on "HTML 5 differences from HTML 4" until a specification for HTML 5 has been agreed. At the moment, the specification represents the beliefs of, and consensus amongst, the WHAT WG rather than this group.
No further comment needed, I believe.
Craig Francis (Craig Francis <craig@synergycms.com>) Yes, agree Web developers need to know what it happening... if they know this is a draft, and things can change, they can also start making suggestions.
Egor Kloos (Egor Kloos <studio@dutchcelt.nl>) Yes, agree This documents state is mature enough to be released in to the wild. Some of the language needs a little polish, which I trust will be taken care of for the working draft release.
Raphael Champeimont (Raphael Champeimont <almacha@almacha.org>) Yes, agree
Eric Eggert (Eric Eggert <ee@w3.org>) Yes, agree
Scott Lewis (Scott Lewis <scotfl@gmail.com>) Yes, agree
Leif Halvard Silli (Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>) Formally Object (1) To publish «differences» before «design principles», would to me seem like ignoring the previous questionaire about which doc to publish first. This again could lead participants to ignore partaking in these questionaires, since their outcome are ignored anyway. Therefore, I formally object.

(2) This working draft currently fails to list accessibility as a field where HTML5 (as delivered from the WHATwg) differs (whether for the better or the worse) substantially from HTML4. To not mention this, may give the impression that one are trying to play down the issue.
(1) This document, which (could) act as a overview of what HTML5 is supposed to be, is long overdue appearance from the brains behind HTML5 - the WHATwg group. But to change its status from editor's draft to working draft now, seems out of order when we have voted to publish design principles first. Also: Without the «real» design principleses document, this could soon become a defacto «design principles» document, as what it really does is to give a short overview over the ideas behind HTML5 - as delivered by the WHATwg. (It is notable that the document reflects very little - if any - of the issues that have been debated the heaviest in the HTMLwg - not only when it comes to the accessibility attributes of TABLE, but also on a such issue as the proposed DOCTYPE.)

(2) But even without agreed upon design principles at hand, I think the working draft fails miserably when it does not mention accessibility as a field where it differs greatly (currently - and perhaps at any rate) from HTML4. HTML4 mentioned Accessisibility as a fields where it differed (positively) from previous HTML standards. See http://www.w3.org/TR/html401/intro/intro.html#h-2.3.2, were many things which WHATwg want to delete, are mentioned (ACRONYM, non-visual rendering of TABLES amongst them.)

Btw, it also feels as if the document speaks with a double tongue, when it speaks about author versus UA requirements. Is this differentiation meant to comfort those authors that do not find their favourite elements/attributes in HTML5 (for instance the HEADERS attribute)?
Adam Nash (Adam Nash <adamn@wirespring.com>) Yes, agree It's an informative summary of the proposed changes, and I think publishing useful working drafts is a measurable way to move forward. My only reservation is that I imagine some people who aren't familiar with the w3c working draft process (most people) will skip all the intro text and get the impression that these changes are finalized, then start blogging in outrage about it or something. I don't know what more can be done about that though; some people are just dumb on the internet.http://lists.w3.org/Archives/Public/public-html/2007Jun/1004.html
Johannes Lichtenberger (Johannes Lichtenberger <jl@nabooisland.com>) Yes, agree It covers the current state of HTML 5 very well.
David Choi (David Choi <daaave@gmail.com>) Yes, agree Seems ready for community review.
Brendan Cullen (Brendan Cullen <brendan@brendancullen.com>) Abstain
Joshue O Connor (Joshue O Connor <josh@interaccess.ie>) No, disagree This is difficult - as I have just joined the group - but in truth I am also not convinced - as it stands - that the document explains clearly the rational for dropping important attributes (summary, headers and longdesc) that have had such a proven and positive impact on enhancing accessibility. I really don't think it's enough to state that they have been dropped and not explain why.When this document is presented to the world and others who are not expert developers or accessibility people read it, it needs to be clear as to why important (accessibility) features are being changed, why this is happening and appear confident in how the specification will evolve. I don't get that sense at the moment and think many will be confused reading it - especially if they come to the document cold.

For the record, I am not against the draft (in principle) but while these issues are being debated and resolved I think it would be best to wait until a clearer outcome is reached. This is also to help developers not in the group to understand some of the very important changes being suggested and contribute to the discussion in a constructive and informed manner.
Thomas Bradley (Thomas Bradley <thomasjbradley@gmail.com>) Yes, agree
Stephen Axthelm (Stephen Axthelm <steveax@pobox.com>) Yes, agree
Ben Boyle (Ben Boyle <benjamins.boyle@gmail.com>) Yes, agree We need to publish, it's a useful document, it's a draft (i.e. people shouldn't assume it represents anything "final" - it represents the current state of the WG).
Robert Marshall (Robert Marshall <rdm@rdmsoft.com>) Yes, agree
Michaeljohn Clement (Michaeljohn Clement <mj@mjclement.com>) Yes, agree
Andrew Ramsden (Andrew Ramsden <andrew@irama.org>) Yes, agree The feedback (positive and negative) it receives should be very useful in guiding the next steps.
Eric Daspet (Eric Daspet <eric.daspet@survol.fr>) Abstain
Olivier Gendrin (Olivier Gendrin <olivier.gendrin@gmail.com>) Yes, agree
Channy Yun (Channy Yun <channy@gmail.com>) Yes, agree General people can understand complicated specification hard to read through this document.
Geoffrey Sneddon ( <>) Yes, agree
Darren West (Darren West <darren.west@gmail.com>) Yes, agree
Shawn Medero (Shawn Medero <smedero@uw.edu>) Yes, agree There seems to be confusion concerning the purpose of this document. A couple of objections state that the document doesn't not adequately justify dropping/adding/changing certain elements but I don't believe this document makes any attempt (nor should it) to justify anything. It clearly explains the differences between HTML 4 and where we are with HTML 5 at this point in time. It has been very productive at doing so - a number of concerns have been raised about the proposed HTML 5 spec within the working group based on the differences pointed out in this document. With that in mind it should be published to a wider audience so we can get their feedback as well. Approving this document and the changes described will not act as a "rubber stamp" for the entire HTML 5 spec.
Lachlan Hunt (Lachlan Hunt <lachlan.hunt@lachy.id.au>) Yes, agree There is no reason not to publish as a working draft. Although it's clearly incomplete and there are many open issues, it closely reflects the current state of HTML5, which is good enough for a WD.Responses that ask for detailed rationale for every dropped, added and changed element and attribute is unrealistic, since the HTML5 spec isn't finished, and not all issues have been decided yet. It's also questionable as to whether giving detailed rationale for decisions is in the scope of this document, which I believe should be an objective summary of the differences only.

By comparison, the following appendices in HTML4 and XHTML1.1 which list changes from previous versions don't give rationale, and the comparison of SGML and XML doesn't either.

Arthur Jennings (Arthur Jennings <arthur.jennings@gmail.com>) Yes, agree
Benjamin Meadowcroft (Benjamin Meadowcroft <ben@benmeadowcroft.com>) Yes, agree Publishing this will open up the work to a wider range of people who can then feedback on the work without trawling through the mailing lists to find out where we are up to as a working group.
Matthew Ratzloff (Matthew Ratzloff <matt@builtfromsource.com>) Abstain
Ryan King (Ryan King <ryan@theryanking.com>) Yes, agree The
James Graham (James Graham <james@hoppipolla.co.uk>) Yes, agree Whilst the concept of "publishing" makes little sense applied to a publicly available document that has already been widely circulated on the internet, this document is, in my opinion, second only to the draft spec itself in it's usefulness in communicating the current state of play for HTML 5. It is also a helpful precis for those unfamiliar with the HTML 5 draft and has caused focused discussion on some technical matters. Since there appear to be some unresolved issues with publishing a draft of the spec itself, I believe this is the second best option.
Kornel Lesinski (Kornel Lesinski <kornel@geekhood.net>) Abstain I'd like it to contain rationale for dropping accessibility-related attributes.
Other than that, it's OK.
Jirka Kosek (Jirka Kosek <jirka@kosek.cz>) Yes, agree http://lists.w3.org/Archives/Public/public-html/2007Jun/0853.html
Cameron McCormack (Cameron McCormack <cam@mcc.id.au>) Yes, agree
Julian Reschke (Julian Reschke <julian.reschke@gmx.de>) Abstain
Jens Meiert (Jens Meiert <jens@meiert.com>) Yes, agree
Steve Faulkner (Steve Faulkner <faulkner.steve@gmail.com>) Formally Object The "HTML 5 differences from HTML 4" Editor's draft 25 June 2007 does not provide a rationale for the dropping of the summary, headers and longdesc attributes and does not provide any information regarding changed or new elements and attributes that will provide the same or similar accessibility features to the attributes being dropped. The arguments for and against the dropping of these attributes are currently being debated by and have been detailed by members of the working group[1] Also it does not adequately document the dropping of these attributes as being open issues within section "1.1. Open Issues"

As per the Formal Objection Guidelines[2]I propose that the "HTML 5 differences from HTML 4" document be modified to clearly indicate the rationales for dropping the attributes in question and their status as being open issues, both in "1.1. Open Issues" and in "3.6. Dropped Attributes" section.


Sander Tekelenburg (Sander Tekelenburg <st@isoc.nl>) Yes, agree
Sean Fraser (Sean Fraser <wileyluxe@gmail.com>) Yes, agree A very important document for continued public education.
Masataka Yakura (Masataka Yakura <masataka.yakura@gmail.com>) Yes, agree
Balakumar Muthu (Balakumar Muthu <balakumar.muthu@gmail.com>) Yes, agree
Brad Fults (Brad Fults <bfults@gmail.com>) Yes, agree This document is the first step in making the work of this working group more approachable and intelligible to both content authors and spec consumers. As such, it should be published and commented on early and often.
Nicolas Le Gall (Nicolas Le Gall <me@neovov.com>) Yes, agree
John-Mark Bell (John-Mark Bell <jmb@netsurf-browser.org>) Abstain
Weston Ruter (Weston Ruter <westonruter@gmail.com>) Yes, agree
David Andersson (David Andersson <liorean@gmail.com>) Yes, agree
Tim McMahon (Tim McMahon <tmcmahon@elevenlimited.com>) Yes, agree
Andrei Polushin (Andrei Polushin <polushin@gmail.com>) Yes, agree
Roger Johansson (Roger Johansson <roger@456bereastreet.com>) Abstain Rationale for each removed/changed/added element and attribute is needed. At the very least the document should state that rationale for all changes will be included in a future update.
Ben Millard (Ben Millard <cerbera@projectcerbera.com>) Yes, agree * Fulfills the heartbeat requirement.
* Merely documents facts and is accurate enough in doing so.
* Introduces how the HTML5 proposal differs technically from current widespread standards, making it suitable as a first publication.
* Is not binding and does not lock us into the current feature set. As the HTML5 proposal changes, so will this document.
Alfonso Martínez de Lizarrondo (Alfonso Martínez de Lizarrondo <amla70@gmail.com>) Abstain
Laura Carlson (Laura Carlson <laura.lee.carlson@gmail.com>) No, disagree Rationale based on design principles, for each and every dropped/added/changed element and attribute should be supplied. Plus a link to the issues page in the the wiki should be added.

The design principles received the most support [34] in the "What should the HTML WG publish first?" survey.
Only seven people supported publishing a "What's new in HTML 5".

Results were:

- Design principles, requirements = 34
- HTML 5 specification = 25
tutorial = 0
- a "What's new in HTML 5" document, enumerating differences from HTML 4, and perhaps discussing their status = 7
- a testing plan/proposal = 1

So I'm not sure why the differences document is being pushed for publication first, unless it is to solely to fulfill the heartbeat requirement.

In order to apply consistent decision making throughout the specification, it is critical to come to consensus on the design principles. No principles or disputed principles can very well lead to inconsistent, contradictory, and discriminating decision making. Principles can be a critical guide.

Consensus of guiding principles, definition of terms, and a common set of reviewing questions for features would:

1. Aid in communication and understanding.
2. Help avoid needless arguments and churning of issues.
3. Promote consistent and fair decision making.
5. Encourage outcomes that reflect what is important to the working group.
6. Benefit working group progress.

Publishing the differences document before coming to consensus on the
design principles is backward.

No agreed upon principles, at best results in decisions (e.g. dropping/adding/changing elements and attributes) without foundation.

At worse it results in arbitrary, inconsistent, unjust, partial, wrong-headed, and discriminating decisions.
At the very least, the document should have a disclaimer stating something like:

"This document is a draft. It is not a set of decisions. It is not based on agreed upon principles. All rationale for proposed differences is pending and will be forthcoming. This document is merely a discussion starter for the group. It does not constitute endorsement of the differences specified, nor does it indicate that the Working Group feels that the document in its present state should be incorporated into HTML 5 as a W3C Recommendation or even a W3C Working Draft."
Paul Haine (Paul Haine <paul@joeblade.com>) Yes, agree
Bill Mason (Bill Mason <billm@accessibleinter.net>) Yes, agree
Andrew Sidwell (Andrew Sidwell <andi@takkaria.org>) Yes, agree It is written and it is useful. Not publishing it seems a waste of effort.
Sandy Smith (Sandy Smith <ssmith@forumone.com>) Yes, agree
Gregory Rosmaita (Gregory Rosmaita <gregory.rosmaita@gmail.com>) Formally Object it is unconscionable that the HTML WG should release a vastly different draft in toto without first outlining and cementing our design principles.i still hold to the opinion that our development path should start with HTML 4.01, its corrections and errata, and THEN introduce each issue from the HTML5 draft as INDIVIDUAL issues. i am EXTREMELY uncomfortable in being forced to choose a draft, in toto, as our bsic working draft slash foundational document, because too many of HTML4x's babies are being flushed down the drain with the bathwater of those issues which need to be addressed more fully, such as the integration of XForms work into HTML markup, and fixing that which is actually broken, by examining each piece individually; comparing and contrasting HTML4x against HTML5 is a good, constructive effort, but to adopt HTML5 and then be told that specific items for specific use cases and re-use cases which have been stripped from HTML4x need to be justified in order to be retained or restored to the proposed HTML5 working draft is a slap in the face of those who worked extremely hard to ensure that HTML4x addressed accessibility issues, and an even harder blow to the guts of the users who actually benefit from them... clearly identified needs don't need to be justified, they need to be addressed. this isn't rhetoric, it's reality.

More details on responses


The following W3C Members and Invited Experts have not answered the questionnaire:

  1. Microsoft Corp.: Paul Cotton <Paul.Cotton@microsoft.com>,Travis Leithead <Travis.Leithead@microsoft.com>,Adrian Bateman <adrianba@microsoft.com>,Jatinder Mann <jmann@microsoft.com>,John Simmons <johnsim@microsoft.com>,Jerry Smith <jdsmith@microsoft.com>
  2. IBM Corporation: Sam Ruby <rubys@intertwingly.net>,Masatomo Kobayashi <mstm@jp.ibm.com>
  3. Avaya Communications: Dan Romascanu <dromasca@avaya.com>,A.S. Krishnakumar <ask@avaya.com>
  4. Comcast Corporation: Mark Vickers <mark_vickers@comcast.com>,Sree Kotay <Sree_Kotay@comcast.com>,Jeremy LaCivita <jeremy.lacivita@comcast.com>,David Mays <david_mays@comcast.com>,Michael Chen <michael_chen@comcast.com>,Bill Mandel <bill.mandel@nbcuni.com>,Patrick Ladd <Pat_Ladd2@comcast.com>,Glenn Deen <glenn.deen@nbcuni.com>,John Riviello <john_riviello@comcast.com>,Rustam Khashimkhodjaev <Rustam_Khashimkhodjaev@comcast.com>,Richard Grzeczkowski <richard_grzeczkowski@comcast.com>,Cory Heslip <cory_heslip@comcast.com>
  5. Huawei: Wu Chou <wu.chou@huawei.com>,GANG LIANG <gang.liang@huawei.com>,Alex Giladi <alex.giladi@huawei.com>,Milan Patel <Milan.Patel@huawei.com>,Hao Jing <jh.jinghao@huawei.com>
  6. SAP SE: Mark Crawford <mark.crawford@sap.com>,Stefan Schnabel <stefan.schnabel@sap.com>
  7. European Broadcasting Union (EBU-UER): Jean-Pierre EVAIN <evain@ebu.ch>,Bram Tullemans <tullemans@ebu.ch>
  8. Pearson plc: Suzanne Taylor <Suzanne.Taylor@pearson.com>,Greg Davis <greg.davis@pearson.com>
  9. Electronics and Telecommunications Research Institute (ETRI): Kangchan Lee <chan@w3.org>,Jonathan Jeon <hollobit@etri.re.kr>,WonSuk Lee <wonsuk.lee@etri.re.kr>,jongyoul Park <jongyoul@etri.re.kr>
  10. Deque Systems, Inc.: Preety Kumar <preety.kumar@deque.com>,John Foliot <john.foliot@deque.com>
  11. Rakuten,Inc.: Kunio Ito <kunio.ito@mail.rakuten.com>
  12. Inswave Systems Co., Ltd.: WOOGLAE KIM <wlkim@inswave.com>
  13. ERICSSON: Magnus Olsson <magnus.olsson@ericsson.com>,Per-Erik Brodin <per-erik.brodin@ericsson.com>
  14. NIC.br - Brazilian Network Information Center: Reinaldo Ferraz <reinaldo@nic.br>,Nathalia Sautchuk Patrício <nathalia@nic.br>
  15. JS Foundation: Brian Kardell <hitchjs@gmail.com>
  16. HTML5 Converged Technology Forum: Hyejin Lee <hjlee@html5forum.or.kr>
  17. Skynav, Inc.: Glenn Adams <glenn@skynav.com>
  18. Baidu, Inc.: Eva Lingyun Jing <jinglingyun@baidu.com>,Xingrong Guo <guoxingrong@baidu.com>,Rayi Lei <leiyi@baidu.com>,jiexuan gao <gaojiexuan@baidu.com>,Xiaoqing Yang <yangxiaoqing@baidu.com>,Xuejian Li <lixuejian@baidu.com>,Zuncheng Yang <yangzuncheng@baidu.com>,Qianglong Zheng <zhengqianglong@baidu.com>,Zhou Shen <shenzhou@baidu.com>,Duoyi Wu <wuduoyi@baidu.com>,Zheng Jia <jiazheng@baidu.com>,Weifeng Feng <fengweifeng@baidu.com>,Damin Hu <hudamin@baidu.com>,Yang Liu <liuyang12@baidu.com>,Zhixing Lei <leizhixing@baidu.com>,Honggang Tang <tanghonggang@baidu.com>,Kefeng Li <buaadallas@gmail.com>,Xu Ma <maxu@baidu.com>,Junzhong Liu <liujunzhong@baidu.com>,lei wang <wanglei03@baidu.com>,Yiling Gu <guyiling@baidu.com>,Zefa Xiong <xiongzefa@baidu.com>,shanglin chen <chenshanglin@baidu.com>,Ping Wu <wuping02@baidu.com>,Bin Chen <chenbin01@baidu.com>,Lei Wang <wanglei@baidu.com>,Pengcheng Guo <guopengcheng@baidu.com>,Xie Jianhui <xiejianhui@baidu.com>,Yujie Jiang <jiangyujie@baidu.com>,Chris Wong <huanghoujin@baidu.com>,Yiliang LIU <liuyiliang@baidu.com>,mingqiang zhang <imcnan@gmail.com>,xueliang fan <fanxueliang@baidu.com>,Yue Min <minyue@baidu.com>,Min Li <limin04@baidu.com>,yaolong wang <wangyaolong@baidu.com>,Tao Liang <liangtao01@baidu.com>
  19. British Broadcasting Corporation: David Evans <david.evans@rd.bbc.co.uk>
  20. Alibaba Group: Dapeng Liu <max.ldp@alibaba-inc.com>,Shaohang Yang <shaohang.ysh@alibaba-inc.com>
  21. Samsung Electronics Co., Ltd.: Youngsun Ryu <ysryu@samsung.com>,MING JIN <ming.jin.web@gmail.com>,Jungkee Song <jungkee.song@samsung.com>
  22. Department of Internal Affairs, New Zealand Government: Jason Kiss <jason@accessibleculture.org>
  23. Electronic Frontier Foundation: Danny O'Brien <danny@eff.org>,Seth Schoen <schoen@eff.org>
  24. W3C Staff:
  25. The Paciello Group, LLC: Steve Faulkner <faulkner.steve@gmail.com>,Patrick Lauke <redux@splintered.co.uk>
  26. Tencent: smallni ding <smallniding@tencent.com>,Min Ren <minren@tencent.com>,qigang huang <qiganghuang@tencent.com>
  27. MovieLabs: James Helman <jhelman@movielabs.com>,Pierre-Anthony Lemieux <pal@sandflow.com>
  28. Center for Mathematics and Computer Science (CWI): Jack Jansen <jack@cwi.nl>,Steven Pemberton <Steven.Pemberton@cwi.nl>
  29. Nippon Telegraph & Telephone Corp. (NTT): Kensaku KOMATSU <kensaku.komatsu@gmail.com>,Youichi Takashima <takashima.youichi@lab.ntt.co.jp>
  30. Defense Information Systems Agency (DISA): Eric VonColln <eric.voncolln@navy.mil>
  31. Mitsue-Links Co., Ltd.: Kazuhito Kidachi <k-kidachi@mitsue.co.jp>
  32. GRIN Technologies, Inc.: Daniel Austin <daniel.austin@grintech.net>
  33. Hachette Livre: Gabino Alonso <gabinovincent@gmail.com>,Sam Langdon <sam.langdon@hachette.co.uk>
  34. Educational Testing Service: Markku Hakkinen <mhakkinen@ets.org>,Jason White <jjwhite@ets.org>
  35. Fraunhofer Gesellschaft: Stefan Kaiser <stefan.kaiser@fokus.fraunhofer.de>,Stefan Pham <stefan.pham@fokus.fraunhofer.de>
  36. Yandex: Charles McCathie Nevile <chaals@yandex-team.ru>
  37. INSTITUT TELECOM: Cyril Concolato <cyril.concolato@telecom-paristech.fr>
  38. MITRE Corporation: Stanley Manoski <manoski@mitre.org>
  39. Newphoria Corporation: Futomi Hatano <futomi.hatano@newphoria.co.jp>
  40. Igalia: Joanmarie Diggs <jdiggs@igalia.com>
  41. Web3D Consortium: Don Brutzman <brutzman@nps.edu>
  42. Cable Television Laboratories Inc: Bob Lund <b.lund@cablelabs.com>,Clarke Stevens <c.stevens@cablelabs.com>
  43. Verimatrix, Inc.: Petr Peterka <ppeterka@verimatrix.com>,Tom Handal <thandal@verimatrix.com>,Niels Thorwirth <nthorwirth@verimatrix.com>
  44. Disruptive Innovations: Daniel Glazman <daniel.glazman@disruptive-innovations.com>
  45. Sony Corporation: Tatsuya Igarashi <Tatsuya.Igarashi@sony.com>,Motomasa Futagami <Motomasa.Futagami@jp.sony.com>,Norifumi Kikkawa <norifumi.kikkawa@jp.sony.com>,Kazuhiko Takabayashi <kazuhiko.takabayashi@jp.sony.com>,Shinya Maruyama <Shinya.Maruyama@jp.sony.com>
  46. Qihoo 360 Technology Co Ltd: Hanrui Gao <gaohanrui@360.cn>,yubo zhou <zhouyubo@360.cn>
  47. Mitsubishi Electric Corporation: Akira Torii <Torii.Akira@bp.MitsubishiElectric.co.jp>,Yusuke Yokosuka <Yokosuka.Yusuke@bx.MitsubishiElectric.co.jp>,Seiji Okumura <Okumura.Seiji@bc.MitsubishiElectric.co.jp>,Eiji Yamamoto <Yamamoto.Eiji@db.MitsubishiElectric.co.jp>
  48. Adobe Systems Inc.: Larry Masinter <masinter@adobe.com>,Roy Fielding <fielding@gbiv.com>,Joe Steele <steele@adobe.com>,Leonard Rosenthol <lrosenth@adobe.com>,Raul Hudea <rhudea@adobe.com>,Raghavan Gurumurthy <raghavan@adobe.com>,Mayank Kumar <mayankk@adobe.com>,Dragos Georgita <dgeorgit@adobe.com>,Christopher Bank <cbank@adobe.com>,Rik Cabanier <Cabanier@adobe.com>,Kevin Streeter <kstreete@adobe.com>,Michael Thornburgh <mthornbu@adobe.com>,Glenn Eguchi <geguchi@adobe.com>
  49. Royal National Institute of Blind People (RNIB): Sally Cain <sally.cain@rnib.org.uk>
  50. Netflix Inc.: Mark Watson <watsonm@netflix.com>,Mick Hakobyan <mhakobyan@netflix.com>
  51. National Association of Broadcasters: So Vang <svang@nab.org>
  52. Josh Lawton <w3c@joshlawton.com>
  53. Vladimir Sinelnikov <sinelnikov@gmail.com>
  54. Vicente García Díaz <vicegd@live.com>
  55. S Emerson <w3c@accretewebsolutions.ca>
  56. Joseph D'Andrea <jdandrea@gmail.com>
  57. Alvar Laigna <laigna@gmail.com>
  58. Lukáš Čihák <lukas.cihak@mensa.cz>
  59. Morten Tollefsen <morten@medialt.no>
  60. Don Kiely <donkiely@computer.org>
  61. Matt Lee <mattl@cnuk.org>
  62. Grzegorz Babula <gbabula@gmail.com>
  63. Deborah Dahl <dahl@conversational-technologies.com>
  64. David Child <dave@addedbytes.com>
  65. Justin Anthony Knapp <justinkoavf@gmail.com>
  66. Mark DuBois <Mark@webprofessionals.org>
  67. Martin McEvoy <martin@weborganics.co.uk>
  68. Patrick D F Ion <ion@ams.org>
  69. Robert Accettura <robert@accettura.com>
  70. Simon Myers <Smylers@stripey.com>
  71. David Bills <w3@dfbills.com>
  72. Anders Bondehagen <anders@bondehagen.com>
  73. Sierk Bornemann <sierkb@gmail.com>
  74. Nik Thierry <me@thisemail.ca>
  75. Ole Riesenberg <or@oleriesenberg.com>
  76. Gian Luca Marroni <gmarroni@libero.it>
  77. Joseph Karr O'Connor <josephoconnor@mac.com>
  78. Emmanuelle Gutiérrez y Restrepo <emmanuelle@sidar.org>
  79. Doug Jones <doug_b_jones@me.com>
  80. Robert Stern <rstern@gmail.com>
  81. Ian Devlin <ian@iandevlin.com>
  82. Yusuke Kagiwada <block.rxckin.beats@gmail.com>
  83. David Carlisle <davidc@nag.co.uk>
  84. David MacDonald <David100@sympatico.ca>
  85. Krijn Hoetmer <w3c@qontent.nl>
  86. Marc Drumm <mdrumm@wcupa.edu>
  87. Shefik Macauley <allknightaccess@gmail.com>
  88. Eihab Ibrahim <eihabibrahim@gmail.com>
  89. Hasan Savran <hsavran@kent.edu>
  90. Danny Liang <danny.glue@gmail.com>
  91. John Vernaleo <john@netpurgatory.com>
  92. Jim Walsh <jim@jwalshcreative.com>
  93. Jim Allan <jimallan@tsbvi.edu>
  94. Shane Thacker <shanethacker@gmail.com>
  95. Jeremy Keith <jeremy@adactio.com>
  96. Greg Johnson <greg.johnson@gmail.com>
  97. Vilem Malek <murphy@malek.cz>
  98. Ron Reisor <ron@udel.edu>
  99. Jedi Lin <JediLin@Gmail.com>
  100. Martijn Croonen <martijn@martijnc.be>
  101. Jonathan Neal <jonathantneal@gmail.com>
  102. Zhihong Mao <zhihong.mao@gmail.com>
  103. Marat Tanalin <mtanalin@yandex.ru>
  104. Jon Hughes <jon@phazm.com>
  105. Benoit Piette <benoit.piette@gmail.com>
  106. Andrew Norman <idonothaveacat@gmail.com>
  107. Samuel Santos <samaxes@gmail.com>
  108. Pedro Xavier Jorge <pedro.xavierjorge@gmail.com>
  109. Tomas Caspers <tomas@tomascaspers.de>
  110. Erik van Kempen <erikvankempen@gmail.com>
  111. Craig Buckler <craigbuckler@gmail.com>
  112. Han Xu <collin@w3china.org>
  113. Nick Fitzsimons <w3@nickfitz.co.uk>
  114. Dale Hudjik <dale.hudjik@gmail.com>
  115. Andrew Davis <andrew@diff.mx>

Send an email to all the non-responders.

Compact view of the results

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.132 2015/11/30 15:46:52 carcone 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)