W3C WBS Home

Results of Questionnaire HTML WG tasks

The results of this questionnaire are available to anybody.

This questionnaire was open from 2007-04-24 to 2009-12-31.

132 answers have been received.

Jump to results for question:

  1. What background experience and expertise do you bring to the group?
  2. What tasks are you here to help with?
  3. Which section(s) are you planning to review in detail in the coming weeks?
  4. When do you plan to complete your detailed review of the above section(s)?

1. What background experience and expertise do you bring to the group?

Please say a few words about any relevant background experience that you bring to the HTML WG.

Details

Responder What background experience and expertise do you bring to the group?
Chasen Le Hara I am very, very familiar with the HTML 4 spec (and the XTML 1 "spec," but that's not saying much). I write XHTML every day, CSS every other day, and JS at least once a week.
Dylan Smith Daily user of a blithering array of tag-soup: html 4 (strict and trans), xhtml, xml, newsml, nitf. It'd be nice if something made the pieces fit together better.... ; )
Murray Maloney I am a technical writer.
My W3C experience is extensive.
I have been a member of every HTML WG,
including the earliest one in the IETF.
I was product manager for HTML editing and viewing tools,
including accessibility tools.

I have also been quite effective in a QA role.
Kornel Lesinski Senior-level experience in web development, including DOM scripting, OOP design patterns.
Technical writer. Involved in "open the web" initiative.
David Dailey Didn't we already fill this out when we signed up? That's fine -- I think my earlier version may have been more complete though.

PhD quantitative psychology, faculty appointments in depts of math, computer science and psychology. Publications in mathematics, linguistics, computer science, psychology. Single artist gallery exhibit last year, including over 50 works in HTML, SVG, pen and ink, Adobe Photoshop. Research in graph theory and some relations to statistics. Recent manuscript submitted for publication on SVG (under review Addison Wesley). Ten years in academic administration including development of instructional software and university web policy and administration. Development of some 2000 web pages for use in instruction on interface design and javascript. Several of these are ranked in the top ten for the query by Google. I am "spec-challenged."
Chris Veenboer Software/web development.
Mihai Sucan Extensive experience with HTML, XHTML, CSS, DOM, and JavaScript - all started 8-9 years ago.

A good knowledge of Voice Interactivity technologies, like VoiceXML, Speech Grammar, Semantic Interpretation, and related.

Recent experience with SVG development.

On a daily basis, I do a lot of JavaScript+DOM+PHP work (and assorted HTML+CSS work).

I also have experience with Atom and RSS.

I do lots of web browser testing, especially Opera and Firefox. Submitted various bug reports, ranging from UI bugs to errors in implementations of specifications (SVG, CSS, Voice, etc).

Since 2006 I started to be interested of contributing to web standards, and related discussions on the WHATWG and W3C mailing lists. Since then I have contributed reviews and suggestions to Web Forms 2, HTML 5 and XBL 2. All of this work is done in spare time.

My site has more details and lists most of my work: robodesign.ro/mihai.
Asbjørn Ulsberg I've worked as a professional web developer for 7 years and had it as a hobby for 10. I've invested large amounts of time in working groups, mailing lists and similar over the years to keep up to date on the current state of affairs and I feel that I am on the technical forefront of web development in Norway.
Brad Fults My relevant expertise lies in HTML implementation and interoperability, spec editing, ECMAScript expertise in specifications, design, implementation and performance. I have previous experience contributing to groups including the WHATWG, Mozilla and W3-Style. I regularly write about technology for the novice. I hold two academic degrees, one in Mathematics-Computer Science and one in Philosophy.
Roger Johansson Several years' experience from writing tutorials and articles related to Web standards and best practices in Web development.
David Baron I work on the layout engine in Mozilla/Firefox (since 1998, full time since 2003) and have been involved in the CSS community for about the same amount of time (and on the CSS Working Group since 2000). I've also been a bit involved with the WHATWG, I was on the CDF working group for about a year, and I'm Mozilla's representative to the W3C Advisory Committee.
John-Mark Bell I've been using web technologies for 8 or so years. For about the last 4 years, I've been heavily involved in implementing support fo HTML and CSS (amongst other things) in the engine of a lightweight web browser (http://www.netsurf-browser.org)
Tim McMahon I am a full time web designer with the American Mathematical Society and own my own design firm Eleven Limited, LLC.
M. Jackson Wilkinson Experience developing parsers, microformats, and other standardized blocks of semantic markup. Experience in education and design that may be useful in developing reference materials.
Maciej Stachowiak
Andrew Neitsch Software development experience, technical aptitude, lots of free time.
Bhasker V Kode I have been tracking developments in human-computer interaction ,which started with my college project titled ajacss where i developed low resolution css based displays and animation built entirely from css, apart from a SALT compliant speech recognition implementation for kiosks .

I am currently working with TutorVista -the online tutoring startup ,in developing its rich and interactive applications using XML and SVG as the standards for communication. Apart from authoring the javascript library and client-side frameworks at work, ive has also worked on human-computer proof-of-concepts and other garage hacks since my college days .I have also been featured on Ajaxian previously for my prototypes on speech recognition with ajax ,and accessable css prototypes . These days I spends my free time spear-heading the Returnable Project - the web delivery mashup framework , authoring the Reusable javascript library , part of the team at TechEnclave.com , and other things client-side . My blog that has been active since 2003 , is over at http://bosky101.blogspot.com where i talk about javascript , scripting and technology .
Magnus Kristiansen Some years of experience with web applications and the related technologies. Testing and writing test cases.
Alfonso Martínez de Lizarrondo Web development for 7 years.
Szymon Pilkowski Front-end developer - big experience with xhtml 1.0/1.1 + CSS, as well as html 4.01 and browser-compatibility issues.
Josef Spillner I'm a researcher in the area of forms generation and thus particularly interested in WF2 adoption and evaluation of its merits. Such work will probably not always be carried out by me personally, depending on the need students might register for the WG as well, but the general idea is that I'll take care of WG-related issues for them.
Beside that I'm firmly rooted in the free software community and will
watch out for issues such as free codecs and KDE-related topics (KHTML renderer, Quanta+ editor) in the HTML5 specification process.
Henrik Lied Worked with HTML for several years, been a participant to the WHATWG Mailing list.
Stephen Stewart Web designer working with HTML for several years.
Matthew Ratzloff Close to a decade of web development experience.
Dominik Tomaszuk Extensive experience with HTML, CSS, JavaScript, XHTML, XML, XSLT, RDF etc.
Thomas Higginbotham I would consider myself proficient in HTML/XHTML, CSS, JavaScript, and ASP.Net. I spend much of my spare time reading about web standards, accessibility, and best practices.
David Hyatt
Nicolas Le Gall I'm not so experienced in HTML, I practice web standards every day since only 2 years. I'm currently a 23 years old student and love to share my knowledge. I think I can bring a "fresh vision" of HTML, just like new HTML users (or future users).
Serdar Kiliç Web developer since 1998.
John Boyer Currently chair of Forms working group and editor of XForms. Previously involved heavily in authoring and editing the family of specs related to XML Signatures, including XML canonicalization, exclusive canonicalization, XML signatures, and XPath filter 2.
Isac Lagerblad I've worked as a professional web developer for 4 years and had it as a hobby for 9. I've spent allot of time in following mailinglists and some webstandartisas bloggers.
Rene Saarsoo
Patrick Taylor Web developer for over 10 years. Intimately familiar with HTML 4.01 spec and the implementation issues among browsers. I've followed WHAT WG spec development for last year, I'm currently educating myself in the fine details of HTML5 as defined by WHAT WG to be better able to contribute to W3 HTML WG.
Jonas Sicking Been working with web development since 1996 and implementing various web standards in the gecko engine since 2000. I've also been doing some W3C spec work.
Roman Kitainik I had been introduced to HTML in 1999. Since then, the front-end web development is my profession.
Addam Wassel Web developer/designer with several years experience creating standards-compliant HTML, XHTML, and CSS.
James VanDyke
Matthew Wilcox Three years practical experience designing and coding standards compliant and accessible websites using HTML4, XHTML (all flavours, including 1.1 sent as xml), and CSS. I have designed and coded numerous sites, large and small, working with organisations of varying sizes, especially as part of my full time job of the last two years as Designer and now Senior Designer at karova.com

Example sites I have coded/designed include:

http://shop.wwf.org.uk/ [WWF World Wide Fund for Nature]
http://www.dedicatetrees.com/ [Woodland Trust]
http://www.wt-store.com/ [Woodland Trust]
http://stdavidshospice.org.uk/ [Small hospice charity]

I have also worked on other non-web HTML based applications for business.

I am familiar with creating bi-lingual websites.
I have good experience of real-world usage of accessible HTML/CSS and their role/importance as exists currently in the charity and business sector.
Anne van Kesteren I'm quite comfortable with the WHATWG proposals having contributed to them since their inception. Some more information can be found here: http://annevankesteren.nl/about
Craig Saila Web standards advocate for nearly 6 years, contributor to CSS 2.1
Darren West 3 years web development experience using web standards, and 10 years other IT experience.
Michael Turnwall Worked as Team Lead for all front-end code for Gateway.com bringing their site closer to web standards. Was the key proponent for web standards at my current job to the point that it became a selling point to help bring in new clients.
James Graham Participant in WHATWG mailing list since 2004. (Co)developer of a few HTML-related tools including html5lib parser.
Gregory Rosmaita i have been an invited expert to the Web Accessibility Initiative (WAI) since 1997. i have served on the Protocols and Formats WG (since before it had a name); the Authoring Tool Accessibility WG; the Evaluation & Repair WG; the User Agent Accessibility Guidelines WG; the Education and Outreach WG; and i served as the Interest-Group Member-at-Large of the WAI Coordination group.

i played a role in drafting:

* Authoring Tool Accessibility Guidelines, 1.0 (ATAG)
* User Agent Accessibility Guidelines, 1.0 (UAAG)
* Web Content Accessibility Guidelines, 1.0 (WCAG)
* XML Authoring Guidelines (XAG)

in addition, i am a member of the Acessibility Working Group (A11Y) at freestandards.org with a concentration on Compound Document Formats (CDF), Scaleable Vector Graphics (SVG), and Web APIs.
Benjamin Hedrington 7 years deep web experience, been messing around with the web more than 10. I am particularly interested the new web technologies and standards that I see emerging further every day through W3C and outside work (Mobile, Future HTML, RDFa, Semantic Web, etc.)
Karl Dubost QA, HTML through all the specifications since the start of the Web.
Yannick Croissant Three years practical experience coding standards compliant. Front-end developer since one year.
Marco Battilana 10 years personal and 7 years professional experience in a web-related role. HTML, CSS, Layout design, Graphic design, Identity design, UI design, User-centered design, Information Architecture, Usability.
Andrew Smith 8 years experience as a professional web designer / developer
Jens Meiert Almost 10 years of document markup expertise with special focus on large-scale, multi-client platforms and portals (based on web standards). Familiar with affiliated topics, especially usability (applies to document authors, too, sure). W3C-close generalist.

http://meiert.com/en/
Eric Eggert Student of media informatics. Web design since 2002 with a focus on document structure and semantics.
Stephen Axthelm software development experience, front end web development experience, documentation experience, front and back end scripting experience
Account Deleted I'm web developer for over 4 years. From 2003 to 2005 web development is my hobby, since 2005 I work as a professional web developer.
I'm a student of National Aviation University of Ukraine.
Andrei Polushin Commercial software development, esp. document viewers. Familiar with various Web technologies from the implementation point.
Chris Adams I am currently a student studying web development with a strong focus on usability and accessibility.
Jirka Kosek I have been involved with markup and Web technologies since 1995. I have written several books about Web technologies (HTML, CSS, PHP, XML) and I teach all those technologies on university.

I'm member of other standardization bodies OASIS (DocBook and RELAX NG TC) and ISO JTC1/SC34. My primary expertise is in XML based publishing systems and validation technologies (RELAX NG, Schematron, NVDL).
Marco Neumann XML, OWL, RDF, Spatial Data
Ian Hickson
Henri Sivonen I've been involved in the WHATWG work since 2004. I'm developing an HTML5 conformance checker and wrote my master's thesis about it. Previously, I've been involved in the Atom working group (feed format—not protocol) at the IETF. I've been involved in the Mozilla project in varying and fluctuating ways since 1999.
Lee Kowalkowski 10 years web development. 5 years development lead for UK government web applications. Specialist in client-tier technologies (JS/CSS/HTML/HTTP) which I practise, study and mentor almost every day.
Robert Burns Currently developing an HTML/XML/CSS authoring tool. Detailed familiarity with several standards including XML, XML namespaces, Unicode, MathML, CSS2, CSS3, HTML 4.01, and XHTML.
Henrik Dvergsdal MSc Computer Science, teaching experience, developer experience. Speciality: universally accessible web applications.
Ariel Pérez I'm a web designer and developer since 2001. I would like to contribute with my modest knowledge about HTML. Deeply interested in standards
David Håsäther Several years of experience with HTML, XML and related technologies. Been following the WHATWG since the start (although not super closely).
Laurens Holst Through personal interest, my work at Backbase (XBL, XForms and Web Forms 2.0-like languages) and study projects, I have gained experience with declarative web apps and various browser and W3C technologies such as Javascript, HTML, CSS, XSLT, XBL, DOM, XML Events, XML Schema, RDF, etc. I also have used XHTML2 as a document markup language for an internal publishing system.
Joshue O Connor Years as a web developer with particular experience working directly with people with disabilities, accessibility auditing, consultancy, usability and user testing.
Mark Martin HTML/CSS authoring full-time for 5 years. JS/DOM for 3 years.
John Bradley I bring a strong and growing knowledge of how the semantic web can work for higher education, and how standards-based web design/development can be taught at the 2-to-4-year college level.
Sean Fraser Eleven years in aerospace Quality Assurance writing process documents and performing data analysis; numerous years constructing web sites; and, several years advocating Web Standards.
Benoit Piette I have +10 years of experience in web development.
I am the president of a local Web development user group (W3Québec) that promotes good web development practices and web standards in the province of Québec Canada
Denis Boudreau Extensive experience with (x)HTML, CSS and WCAG. Experience in standardization with the Quebec governement and ISO (participating in working groups related to human interfaces and accessibility).
Carol King Several years of standards-based Web development experience: HTML, XHTML, and XML.
Balakumar Muthu Fell in love with Web since 1996 and involved in Designing, Development and User Experience technologies. Has a Tech Blog @ http://i5bala.com
Gonzalo Rubio I'm working on the web since 1999 and i've been the leader of the user-experience design department at a regional company for almost a year.
Alejandro Fernandez Web designer and developer for 5 years.
Interested in standards developing and usability.
Stéphane Deschamps I have made web sites for ten years and have advocated for standards for several years, either through helping translation projects (<http://www.pompage.net/>) or by co-organising a cycle of conferences devoted to best practices (<http://www.paris-web.fr/>).
Marek Pawlowski BSc Automatics. Active webdeveloper also involved in some intranet webapps. Major experience in HTML, CSS, JS, PHP, Object Pascal. Minor: C++, Java. Recent experience: SVG, Atom/RSS, Microformats. Experience in beta testing.
Masataka Yakura
Thomas Bradley Several years education and experience in front-end and back-end development and design.
Jon Barnett intimate familiarity with HTML, XML, CSS, Javascript, DOM, XSLT, XPath, and PHP.
Debi Orton I've been coding web sites since 1996, and have spent MANY hours wandering through the HTML/XHTML/CSS documentation learning how to make it work. I have also been involved in the New York State (U. S.) accessibility initiative since 1999. Since 2003, I have been the co-chair of the NYS Forum's IT Accessibility Committee, which provides support and resources to state agency web developers, and it is in that role that I joined this group. Although New York's policy and standards diverged from the WCAG when the threat of 2.0 seemed close (2004), we have urged using web standards, such as HTML, XHTML, CSS, XML to achieve accessibility. I write supporting documentation on a regular basis. Most recently, our Governor signed an executive order decreeing that all public meetings were to made available to the public via video webcasts -- an entirely new concept to State web developers -- and I have been working with our committee to provide information and resources on implementing the executive order in an accessible way. I have been following the ARIA group, since AJAX is becoming somewhat of a problem for people using screen readers, and saw the call to join this working group.
Marcin Hanclik parsers, compilers, browser internals, browser development, multimedia standards
Jason White From 1993-96 I was an observer in the International Committee for Accessible
Document Design, which developed an SGML DTD for use by publishers to enable
books to be made more accessible to people with print disabilities. In 1997, I
joined the first W3C Web Accessibility Initiative working group, and
participated in discussions surrounding the accessibility of what was then
known as HTML Cougar, which later became HTML 4, and CSS 2.0. In 1998-99 I
participated in the Web Content Accessibility Guidelines working group, which
took WCAG 1.0 to Recommendation status. From 2000-2004 I was privileged to
serve, with Gregg Vanderheiden, as co-Chair of the WCAG working group. I have
also been involved in the WAI Protocols and Formats working group, discussing
accessibility issues related to a number of W3C technologies. Other relevant
activities include participation in technical committees of the Daisy
Consortium, and involvement, as an invited expert, in the W3C's Device
Independence working group. I use both braille and speech output systems to
access the Web and have an abiding interest in research related to non-visual
user interfaces and document processing applications.
Sander van Lambalgen Professional web application developer since 2000-2003 (depending on where you draw the line of professionalism; see http://have-skill.com/ for specific skills). Active participant in the WHATWG during 2004 and early 2005; only lurking since, although I try to at least keep up with changes to the draft.
Charles McCathie Nevile Worked on the accessibility implementations of Opera and Amaya, and a number of authoring tools. Worked on various accessibility specs and teaching people to produce accessible web content.
David McClure MS Computer Science, developer experience
Eric Daspet Expertise from the authoring point of view (xml, sgml, html, accessibility)
Experience in writing and reviewing spec
Ben Boyle Web developer (10 years); interested in seeing HTML5 provide richer semantics.
Dimitri Glazkov Web developer since 1995, write server-side software that produces, consumes, and processes markup on an organization scale (CMS), as well as client-side (JS) part of the software.
Kai Hendry http://hendry.iki.fi/cv - my resume

I'm generally interested with the Web in the mobile/handheld device context. I wrote my Master thesis about it: http://hendry.iki.fi/msc.pdf
Matthew Raymond Web developer with several years of programming experience outside Web development. Previously worked on Web sites and various Web standards as a hobby. Degree in Computer Systems Engineering from Boston University.
Adam Roben Have worked on Safari/WebKit since July 2006. Sporadic web development experience since 1998.
Ryan King
Shawn Medero I've been involved web development since 1996 (starting professionally in 1997). I've coded (and still do) HTML pages by hand but also with WYSIWYG editors for academic institutions, large corporations, small business, and personal use. I've constructed web sites that used Arabic, Bengali, Chinese, English, French, German, and many others. Additionally, I am well versed in the server-side scripting languages and content management systems that are often used to generate HTML pages. Finally, I have wore other hats like system administrator (setting up Apache or IIS), project manager and my current role as an interface designer. Currently I work at a non-profit research institution that creates large-scale linguistic data for research purposes (biomedical study, text mining, machine translation, social-linguistic study...) that are often sourced from web-based content.
Weston Ruter I've been web developing since late 90's, and I did my undergrad in Computer Science. I have been developing a cross-browser implementation of Web Forms 2.0 (http://code.google.com/p/webforms2/) so I am pretty familiar with that spec.
Mikko Honkala Prototype browser implementation (XHTML, CSS, SVG, XForms), XForms standardization
Mark Baker Former HTML WG member (1999-2000), where I was a co-editor of XHTML Basic. Expertise as a former mobile browser developer (three different browsers). Also very knowledgeable about HTTP, URIs, Web history, Web & Internet architecture, REST, etc..
Marghanita da Cruz Authoring and publishing webpages in HTML since 1997.
Apache Webserver (user), Linux and MSWindows Desktops
Programmer to sales roles in ICT since 1982.

Assisted in Drafting AS8015-2005 Australian Standard for Corporate Governance of ICT
<http://www.ramin.com.au/itgovernance/as8015.html>

Presentations on Video Editing and Publishing content on the Web using Ogg Theora/Vorbis

Open Source Video Editing and Publication Sydney, 27th July 2006
<http://www.ramin.com.au/linux/acs-os-sig.html>

Capture and Editing in Linux using Kino, Sydney 31 August 2007
<http://www.ramin.com.au/linux/video-capture-editing-using-kino.shtml>
Joseph D'Andrea Conceived/lead AT&T Labs' Web Standards Initiative, cultivating "environmentally responsible" site development techniques benefiting content managers, developers, and designers.

Developed AT&T-internal, enhanced version of GeraldO's Kinder, Gentler Validator (before it moved to the W3C and before source was available).

Contributed testing/feedback to DaveR's HTML Tidy in it's early stages.

Rewrote Google Enterprise's XSLT with standards compliance and accessibility in mind. (Also supports [X]HTML5.)

Over fifteen years experience in IA, software engineering, key web technologies and mentoring others on their use.

AT&T project info: http://www.joesapt.net/article/weeklystandards/
Google project info: http://code.google.com/p/gsa-xhtml-stylesheet/
LinkedIn Profile: http://www.linkedin.com/in/jdandrea
Geoffrey Sneddon Been part of the standards movement since 2003, familiar with HTML 4.01 spec (and, as I always end up saying, <i> is NOT deprecated), decent knowledge of XML 1.0 and XHTML 1.0 specs, as well as knowledge of parts of CSS 2.1 (but what parts I do know, I know well). I'm an implementer of Atom and RSS, with plans to implement HTML5.
Scott Vesey web browser deployment in large intranet
issues for large corporate environments
legacy user agent dependancies
Justin Thorp I've done plenty of education and outreach work concerning web standards and web accessibility, including being on WAI's EOWG for the last 4+ years.

I have also worked on many teams where we have authored standards-compliant large scale Web sites for all types of people and organization.
Doug Jones spec, standard procedure authoring; instruction to users.
Ivan Enderlin I'm developing on web since 1999, and I've always read W3C's recommandations. I try — in each of my development — to make the best work as possible. I hear by best work, a work that correctly written for everyone (including accessible). The accessibility (and a fortiori well-formed HTML, CSS, Javascript and co.) is my first reason to join and contribute to this working group. The second reason is that I think Internet has a great future ahead of him. Internet could be very powerfull, and my little (but strong) experience should be usefull.
Wesley Upchurch 7 years of web design and development experience.
Preston Bannister Of immediate relevance is the exercise of the past few years, in replacing a desktop application with a web-based equivalent. The task called for pushing (hard!) on the limits of HTML/CSS/Javascript in current browsers, so I have a pretty good grasp of that domain.

Played with HTML a bit since 1992, but stayed away from trying to do anything complex until the playing field was less of a mess (when we saw NN4 fading, IE6 dominant, and Mozilla/Firefox rising).

As a single common thread, pretty much everything I've worked on in the past 25 years has had a network in the middle - all commercial software of various sorts, mostly for intranets. Worked on GUI applications (on and off) starting in the early 1980's.

Played the role of security "expert" (not a title I'd claim) for most of the projects I've been involved with - mainly as I'd read up on security/encryption/authentication for a task in 1985, figured out what needed to be done, and got an unexpected visit from the NSA.

An interest in artificial intelligence (AI) was what originally brought me to software. Sent a good amount of time using Lisp, after signing up for a couple AI-related projects.
Sierk Bornemann Senior-level experience in document markup and CSS, grown since 1997. Familiar with affiliated topics, especially contributing (code, ideas) to W3C QA Tools (W3C Markup Validator) and promoting them (openSUSE Linux). W3C-close generalist.

<http://sierkbornemann.de/>
Sam Kuper I've been working with HTML since 1998. Wrote help files using HTML and JavaScript for Nortel Networks in 1999 and became a freelance HTML/JavaScript/Flash debugger and author in 2000.
Samuel Santos I work mainly as a J2EE Web Developer.
I am very confident with both the HTML/XHTML and CSS specifications and strict following of web standards has always been a goal.
I am a strong advocate of usability and accessibility standards, after all the web is for everyone.
Raphael Champeimont I have written HTML documents for 5 years...
Karl Groves I have been designing & developing websites since 1996 and have done so professionally since 2001. I have a background in psychology and philosophy and have worked as a usability & accessibility consultant for the past 4 years. During that time, I've had a lot of experiences which have lead to a broad view of how sites are being produced - by everything from small companies to Fortune 200 companies.
aurélien levy co-writing of the french accessibility guidelines
David Singer I am a multimedia standards person, focused on the new media tags.
David Randall Working on the web for 9 years with extensive knowledge with xhtml/css, web standards, semantic markup and accessiblity.
Bill Mason Eight years mostly in front-end web development: (X)HTML, CSS, Javascript, accessibility.
Kelly Gifford Professional Web Developer/Software Engineer since 2001 (experienced in both front and back-end technologies). Started coding HTML way back in 1995.
Sam Johnston Extensive web application development since 1996 across many environments. Technical and policy writing experience. CISSP.
Dean Edridge
Cynthia Shelly I'm a member of the new Accessiblity Labs team at Microsoft, and am responsible for strategy and incubation around Web Accessibility. I've worked at Microsoft since 1996, mostly on projects that touched the web in one way or another. Among other roles, I was a development lead on the www.msn.com home page, a program manager on Office Graphics, and drove accessiblity for Windows Live.

I have a lot of experience with making complex, dynamic web applications accessible, while still making them compelling in a highly competetive market. I have a strong interest in semantics of documents, graphics, and especially of user interface controls and their behavior.

I've been a member of the WCAG 2.0 working group since 2000, and have recently joined PF.
Dionysios Synodinos * Web Engineer,
* Technical Editor for online publications and magazines &
* Freelance consultant

Focusing on:
* Rich Internet Applications
* Web Application Security
* Multi-channel access and Web Services

Going back and forth between server side programming and UI design for more than a decade, been involved in diverse software projects and contributed to different publications. Strong research background on the area of Mobile WWW.
Simon Pieters I am participating in the WHATWG since 2005. I'm doing QA and spec work for Opera since 2007.
Terry Morris I am an associate professor of Computer Information Systems at William Rainey Harper College in Palatine, IL, USA. I've been teaching web development since 1999. My background also include over a decade as an information technology professional doing software development, systems analysis, and web development. Please seem http://terrymorris.net for more information.
Ben Millard * Professional frontend developer (HTML, CSS, accessibility) working on UK commercial and public sector websites at different scales:
<http://www.sdesign1.com/ben.htm>
* Moderator and active participant at Accessify Forum:
<http://www.accessifyforum.com/profile.php?mode=viewprofile&u=2202>
* Website markup collection and analysis leading to development of HTML5 accessibility features. Most recent work funded by Mozilla Foundation (1st September 2008 to 1st December 2008):
<http://projectcerbera.com/web/study/>
* Reads about accessibility, usability, standards and web technology generally.
Dan Connolly been involved with development/standardization of HTML, HTTP, URIs, XML, RDF, OWL, etc. Some commercial software development too.
http://www.w3.org/People/Connolly/
Julian Reschke - some product experience automatically extracting metadata from HTML (DC in meta elements, XPath based extractors)

- support of RFC2629 engine in XSLT (IETF XML format for spec writing), generating (X)HTML with microformats
Channy Yun Web standards evangelist involved in WaSP ilg group member since 2007, joining WHATWG mailing list since 2004. Mozilla l10n Korean owner from 2002.
Larry Masinter I've been working on standards development since the early 1980s (25 years) including development of Internet and Web standards since the early 1990s. I've been deeply involved (as working group chair and document editor) in numerous efforts -- see my web site http://larry.masinter.net for a sample.
Laura Carlson Web Designer for over a dozen years. Experience in in web standards design and development, HTML, accessibility, CSS, training, learning technologies, instructional design, and technology documentation. Education includes a Bachelors and Masters degree. For more information visit "Ten questions for Laura Carlson" Web Standards Group Interview:
http://webstandardsgroup.org/features/laura-carlson.cfm
Martin McEvoy I have been involved with HTML markup languages since 1997.
I have Designed and Implemented new microformats using the microformats process.
I have also built many GRDDL profiles using XSLT
I also have Built a RDFa plugin for Dreamweaver
Ryan Mitchell User of HTML for 14+ years, open source web developer with in emphasis on UX.
John Stewart - Work in a government lab that promotes creation of international standards;
- have open-source implementation of X3D;
- participant in X3D design and evolution process.
Jace Voracek I have extensive experience with web development primarily with open source coding and HTML. I also am a motion graphics designer, and look forward to the enhancement of multimedia content with HTML 5. As an iPhone developer, I am also interested in the growth of mobile web content.

2. What tasks are you here to help with?

summary | by responder | by choice

Choose one or more tasks that you're particularly interested to work on. Some options have questions; if you check one of those, please answer the question in a comment.

Bonus points for providing pointers to relevant work that you have already done and/or dates by which you plan to have something for the WG to look at.

If you're willing to lead in certain areas, please note that in a comment too.

See also HtmlTaskBrainstorm, invitation 11 Apr.

Summary

ChoiceAll responders
Results
drafting spec text (which features/sections?) 28
detailed review of substantial sections of spec (which features/sections?) 48
test case development (which kind?) 32
manual test result (which browser? authoring tools?) 29
test suite organization/editing 12
tutorial development, quick reference, course materials, ... 56
formalization (schemas, formal rules, ...) 12
a periodic survey of top web sites 25
usability testing 38
design principles, goals requirements (drafting, review, liaison) 35
orientation: documenting group norms, helping people learn them 14
web browser maintenance (esp. fixing bugs around spec compliance) 14
web browser enhancements 16
authoring tool development 15
prototyping new features using scripting 20
validation/checking service development 15
validation/checking service operations 8
issue tracking, summarization, and clustering 22
security review, risk analysis 11
forms taskforce 17
translation to languages other than English 7
serve as scribe for teleconferences 3

Skip to view by choice.

View by responder

Details

Responder What tasks are you here to help with?Comments
Chasen Le Hara
  • test case development (which kind?)
  • manual test result (which browser? authoring tools?)
  • test suite organization/editing
  • tutorial development, quick reference, course materials, ...
  • usability testing
  • authoring tool development
  • prototyping new features using scripting
  • validation/checking service development
  • validation/checking service operations
  • issue tracking, summarization, and clustering
  • security review, risk analysis
I'm willing to work with or build any test cases. I can check tests in Safari, Firefox, and Opera (any version of those browsers).

I like making tutorials and would be happy to make some for HTML 5.
Dylan Smith
  • tutorial development, quick reference, course materials, ...
  • usability testing
Murray Maloney
  • drafting spec text (which features/sections?)
  • detailed review of substantial sections of spec (which features/sections?)
  • design principles, goals requirements (drafting, review, liaison)
I am not able to commit myself sufficiently to offer my services as an editor (due to ongoing health issues). However, I would like to have a significant role in the development of the HTML specification, as an occasional writer and/or as a critical reviewer.
Kornel Lesinski
  • tutorial development, quick reference, course materials, ...
  • design principles, goals requirements (drafting, review, liaison)
  • prototyping new features using scripting
  • validation/checking service development
  • security review, risk analysis
I'm going to write tutorials for new features, in Polish, and gather feedback.

I'm testing Web Forms on some of my websites, usually writing JS implementations.

I have prototype of non-schema based conformance checker + tidy tool for HTML4 and XHTML, which (if time permits) I plan to update for HTML5.
David Dailey
  • tutorial development, quick reference, course materials, ...
  • usability testing
  • design principles, goals requirements (drafting, review, liaison)
  • orientation: documenting group norms, helping people learn them
  • issue tracking, summarization, and clustering
I could help as needed (and as appropriate to my expertise) with any of the checked areas, but certainly not with all. Sign me up for slots where I can be useful and where there seems to be an undersupply of volunteers, or where my expertise (whatever that is) may prove valuable. Concerning tutorials and other training materials, I my expertise is currently limited to proofreading. After some preliminary guides are developed I might be able to help with course materials or even test suites.

In the area of design principles, I could work on non-normative principles.
Chris Veenboer
  • web browser maintenance (esp. fixing bugs around spec compliance)
  • prototyping new features using scripting
Mihai Sucan
  • test case development (which kind?)
  • tutorial development, quick reference, course materials, ...
  • authoring tool development
  • prototyping new features using scripting
(when time allows)

I review any section of the spec, and provide my suggestions.

I can do test case development: from parsing to interoperability tests, JavaScript, DOM, HTML, XML and anything needed. I have experience making test cases for bug reports (most of them for Opera).

I can do complete, in-depth reviews/surveys of top web sites, when needed. I can precisely pin-point errors made, provide tips for fixing/improving the sites, provide links to resources for learning and related work. However, given my current schedule I cannot do it periodically.

Tutorial development experience: I wrote a tutorial about Voice Interactivity for Opera (see dev.opera.com). I plan to write more tutorials going over new teritory (not only Voice Interactivity).

Regarding authoring tool development: I am working on my own WYSIWYG editor, which includes a page cleaner - both projects are not yet public.

I plan to contribute more to this working group over the summer.
Asbjørn Ulsberg
  • detailed review of substantial sections of spec (which features/sections?)
  • test case development (which kind?)
  • tutorial development, quick reference, course materials, ...
  • prototyping new features using scripting
I'd like to point out that my level of involvement in the HTML WG is higly dependent on the time I have available for it. I participate in the WG on my private time which is often quite pressed already. I would love to participate in the WG in my working hours, but unfortunately my employer does not acknowledge or support my choice in joining this WG, so I have to do it outside of work.

Given this, the checked items above does only reflect what I would like to contribute with, not what I will necessarily do. E.g., I can't really commit to anything with my current work situation. If my employer embraces my membership, I will be able to commit more strongly to given tasks, but at the moment, I'm just trying to contribute the best I can with discussing issues on the lists and doing as much work as possible off-list.
Brad Fults
  • tutorial development, quick reference, course materials, ...
  • design principles, goals requirements (drafting, review, liaison)
Roger Johansson
  • tutorial development, quick reference, course materials, ...
David Baron
  • test case development (which kind?)
  • design principles, goals requirements (drafting, review, liaison)
  • web browser maintenance (esp. fixing bugs around spec compliance)
  • web browser enhancements
John-Mark Bell
  • detailed review of substantial sections of spec (which features/sections?)
  • test case development (which kind?)
  • web browser maintenance (esp. fixing bugs around spec compliance)
  • web browser enhancements
I'm likely to be implementing the parsing section of the WHATWG spec in the relatively near future. As part of that process, I'll be reviewing that section (at least) in some detail.

Being involved in UA development, more testcases are always beneficial. I'd be happy to contribute in this area as much as time allows. I probably don't have sufficient time to help with editing any testsuite, however.
Tim McMahon
  • usability testing
  • design principles, goals requirements (drafting, review, liaison)
  • authoring tool development
M. Jackson Wilkinson
  • tutorial development, quick reference, course materials, ...
  • a periodic survey of top web sites
  • usability testing
willing to lead insofar as educational materials are concerned
Maciej Stachowiak
  • detailed review of substantial sections of spec (which features/sections?)
  • test case development (which kind?)
  • manual test result (which browser? authoring tools?)
  • design principles, goals requirements (drafting, review, liaison)
  • web browser maintenance (esp. fixing bugs around spec compliance)
  • web browser enhancements
  • security review, risk analysis
  • forms taskforce
detailed review: mainly DOM APIs and scripting issues
test case development: mainly scripting & media features
manual test result: happy to test on Safari (latest shipping and WebKit trunk) as needed
design principles: willing to continue editing if needed and desired
web browser maintenance, web browser enhancements: it's my job! at least for Safari/WebKit


Andrew Neitsch
  • detailed review of substantial sections of spec (which features/sections?)
  • usability testing
Bhasker V Kode
  • tutorial development, quick reference, course materials, ...
  • design principles, goals requirements (drafting, review, liaison)
  • web browser enhancements
  • prototyping new features using scripting
I am a quick learner and a proficient speaker and writer. With guidance,I am willing to work on new enhancements,understand w3c writing guidelines and help in editing,and extending documents - both with my expertise as well as those who work in collaboration.
Magnus Kristiansen
  • test case development (which kind?)
  • prototyping new features using scripting
No particular reservations on test case types (yet).
Alfonso Martínez de Lizarrondo
  • authoring tool development
Now I'm colaborating in the development of FCKeditor, so I can try to help adding there new features or fix existing problems.
Szymon Pilkowski
  • manual test result (which browser? authoring tools?)
  • web browser maintenance (esp. fixing bugs around spec compliance)
Browser: I mostly use Opera for surfing and Firefox for development.
I test my pages in: Firefox 1.5, Firefox 2.0, Opera 9, IE 6.0, IE 5.5, eventually IE 5.0.
Josef Spillner
  • formalization (schemas, formal rules, ...)
  • authoring tool development
  • validation/checking service development
  • forms taskforce
A student thesis will be written to compare XF/XF-Transitional/WF2 and to find out about declarative vs. imperative forms needs (cf discussion on public-html).
Henrik Lied
  • test case development (which kind?)
  • tutorial development, quick reference, course materials, ...
  • usability testing
Stephen Stewart
  • tutorial development, quick reference, course materials, ...
Matthew Ratzloff
  • test suite organization/editing
  • tutorial development, quick reference, course materials, ...
Time permitting, I'm interested in helping to edit a document targeted at content authors, created from the final recommendation but pared down considerably. This would contain no implementation information.

I would also like to create a document for content authors detailing differences from HTML 4.
Dominik Tomaszuk
  • drafting spec text (which features/sections?)
  • test suite organization/editing
  • tutorial development, quick reference, course materials, ...
  • formalization (schemas, formal rules, ...)
  • usability testing
  • validation/checking service development
  • validation/checking service operations
  • forms taskforce
Thomas Higginbotham
  • detailed review of substantial sections of spec (which features/sections?)
  • test case development (which kind?)
David Hyatt
  • drafting spec text (which features/sections?)
  • detailed review of substantial sections of spec (which features/sections?)
  • test case development (which kind?)
  • web browser maintenance (esp. fixing bugs around spec compliance)
  • web browser enhancements
Nicolas Le Gall
  • tutorial development, quick reference, course materials, ...
  • orientation: documenting group norms, helping people learn them
Serdar Kiliç
  • detailed review of substantial sections of spec (which features/sections?)
  • manual test result (which browser? authoring tools?)
  • a periodic survey of top web sites
  • prototyping new features using scripting
John Boyer
  • forms taskforce
I am interested in working out a forms language for HTML that meets as well as possible the requirements that inspired both XForms and WF2. I am especially interested in an architecture that allows relatively seamless scale up from html4 tag soup forms to xforms, where I view aspects of WF2 as being somewhere in the middle with possibly some pieces not being able to morph, without adjustment, to something more like xforms (which I see ultimately manifesting itself in the lifecycle of forms that grow sufficiently complex over time).
Isac Lagerblad
  • detailed review of substantial sections of spec (which features/sections?)
  • tutorial development, quick reference, course materials, ...
  • usability testing
Rene Saarsoo
  • a periodic survey of top web sites
I have done some previous work on analyzing/validating the markup on a number of pages [1]. Also some periodic surveys on Estonian websites [2].

Both of these studies should be repeated, or some other selection of sites could be tested, but I don't have enough resources at the moment to survey more than 100,000 sites.

[1] http://triin.net/2006/06/12/Coding_practices_of_web_pages
[2] http://triin.net/2005/04/27/Web_Standards_in_Estonia
Patrick Taylor
  • detailed review of substantial sections of spec (which features/sections?)
  • manual test result (which browser? authoring tools?)
  • tutorial development, quick reference, course materials, ...
  • a periodic survey of top web sites
  • usability testing
  • authoring tool development
Detailed review of sections of spec - which features/sections - as much as is needed
Manual test result - which browser? - Safari, Opera, Firefox, legacy browsers on both Mac and Windows
Tutorials, course materials - happy to assist in writing or review any tutorials or course materials
Authoring tool development - will work or help on HTML5 bundle for Textmate
Jonas Sicking
  • drafting spec text (which features/sections?)
  • detailed review of substantial sections of spec (which features/sections?)
  • manual test result (which browser? authoring tools?)
  • design principles, goals requirements (drafting, review, liaison)
  • web browser maintenance (esp. fixing bugs around spec compliance)
  • web browser enhancements
  • security review, risk analysis
Drafting for and reviewing the full HTML spec.
Tests for the 4 major browsers though mostly for firefox.
Browser maintenance and development for firefox.
Roman Kitainik
  • drafting spec text (which features/sections?)
  • detailed review of substantial sections of spec (which features/sections?)
  • test case development (which kind?)
  • manual test result (which browser? authoring tools?)
  • test suite organization/editing
  • tutorial development, quick reference, course materials, ...
  • a periodic survey of top web sites
  • usability testing
  • design principles, goals requirements (drafting, review, liaison)
  • orientation: documenting group norms, helping people learn them
  • web browser maintenance (esp. fixing bugs around spec compliance)
  • web browser enhancements
  • authoring tool development
  • issue tracking, summarization, and clustering
It would be rewarding to see the skills and expertise I was lucky to accumulate put to good use. Any kind of good use.
Addam Wassel
  • tutorial development, quick reference, course materials, ...
  • usability testing
James VanDyke
  • tutorial development, quick reference, course materials, ...
  • a periodic survey of top web sites
  • usability testing
Matthew Wilcox
  • drafting spec text (which features/sections?)
  • detailed review of substantial sections of spec (which features/sections?)
  • design principles, goals requirements (drafting, review, liaison)
I am interested in any elements of the HTML5 specification that will potentially differ from those set out in existing HTML/XHTML specification. Main concerns are accessibility features and semantics in the language. I would like to review any such potential modifications, with the intent to question why such changes may be being proposed, how those changes may effect existing sites, ramifications of any changes, and whether such modifications or additions enhance and clarify the accessibility and semantics of the language.
Anne van Kesteren
  • detailed review of substantial sections of spec (which features/sections?)
  • test case development (which kind?)
  • design principles, goals requirements (drafting, review, liaison)
  • forms taskforce
I have worked on tests for Web Forms 2, <canvas>, the HTML5 parsing algorithm and several smaller features. I'm planning to continue that work whenever time lets me. I might be willing to help out with test suite organization, but I'm not sure if I have enough time to fully help with getting it to work.
Craig Saila
  • detailed review of substantial sections of spec (which features/sections?)
  • manual test result (which browser? authoring tools?)
  • tutorial development, quick reference, course materials, ...
  • a periodic survey of top web sites
  • design principles, goals requirements (drafting, review, liaison)
Re: review, I can tackle any section that's needed.

Re: testing results in IE6, IE7, WebKit, Gecko, Opera 9 and TextMate authoring tool.
Darren West
  • detailed review of substantial sections of spec (which features/sections?)
  • prototyping new features using scripting
  • forms taskforce
Interested in forms and accessibility and would like to help out where ever I can. I'm very interested in maintaining and expanding HTML's semantics while also creating purposeful? UI elements.
Michael Turnwall
  • drafting spec text (which features/sections?)
  • a periodic survey of top web sites
  • usability testing
I'm open to any section. Just let me know what is expected.
James Graham
  • test case development (which kind?)
  • validation/checking service development
  • issue tracking, summarization, and clustering
Test cases for parsing in particular
Gregory Rosmaita
  • drafting spec text (which features/sections?)
  • test case development (which kind?)
  • manual test result (which browser? authoring tools?)
  • test suite organization/editing
  • formalization (schemas, formal rules, ...)
  • usability testing
  • design principles, goals requirements (drafting, review, liaison)
  • web browser maintenance (esp. fixing bugs around spec compliance)
  • authoring tool development
  • validation/checking service development
  • forms taskforce
i have contributed to and built test suites; i have contributed to the drafting of guidelines; i have extensive experience in usability testing; i serve as my own authoring tool; and am interested in furthering the accessibility advances of HTML 4.01
Benjamin Hedrington
  • tutorial development, quick reference, course materials, ...
  • a periodic survey of top web sites
  • design principles, goals requirements (drafting, review, liaison)
  • prototyping new features using scripting
  • issue tracking, summarization, and clustering
I'd be willing to help efforts in any of these areas, I hesitate so say I could lead as I do not know if there are prescribed processes or procedures the W3C expects. I clicked through in response to Dan's call for more help with "issue tracking, summarization, and clustering" I don't know exactly what that entails (e.g. monitoring the Email list, convening small groups to discuss issues via phone or email, etc.) I have been told I have a way of summarizing and crystallizing an issue or discussion so other can better understand it which may be an asset here and I am willing to help.

Thanks,
-Ben
Karl Dubost
  • drafting spec text (which features/sections?)
  • detailed review of substantial sections of spec (which features/sections?)
  • test case development (which kind?)
  • tutorial development, quick reference, course materials, ...
  • a periodic survey of top web sites
  • validation/checking service development
  • validation/checking service operations
  • issue tracking, summarization, and clustering
Yannick Croissant
  • tutorial development, quick reference, course materials, ...
  • orientation: documenting group norms, helping people learn them
Marco Battilana
  • test case development (which kind?)
  • manual test result (which browser? authoring tools?)
  • a periodic survey of top web sites
  • usability testing
  • design principles, goals requirements (drafting, review, liaison)
  • orientation: documenting group norms, helping people learn them
Andrew Smith
  • manual test result (which browser? authoring tools?)
  • formalization (schemas, formal rules, ...)
  • a periodic survey of top web sites
  • usability testing
  • design principles, goals requirements (drafting, review, liaison)
Jens Meiert
  • detailed review of substantial sections of spec (which features/sections?)
  • tutorial development, quick reference, course materials, ...
  • usability testing
  • design principles, goals requirements (drafting, review, liaison)
  • issue tracking, summarization, and clustering
Eric Eggert
  • a periodic survey of top web sites
  • design principles, goals requirements (drafting, review, liaison)
Stephen Axthelm
  • manual test result (which browser? authoring tools?)
  • orientation: documenting group norms, helping people learn them
  • validation/checking service operations
  • issue tracking, summarization, and clustering
My reasons for joining the WG were in part to help make the new specifications more approachable to the average developer. I'll gladly pitch in where ever help is needed but I'd be keenly interested in helping with any tasks that where I can help improve the developer/spec interface.
Account Deleted
  • manual test result (which browser? authoring tools?)
  • usability testing
  • forms taskforce
manual test result: I use Opera for development and for surfing.
I test my web-projects in such browsers: Opera 9, Firefox 2.0, IE 6.0
Andrei Polushin
  • web browser maintenance (esp. fixing bugs around spec compliance)
  • web browser enhancements
Chris Adams
  • manual test result (which browser? authoring tools?)
  • tutorial development, quick reference, course materials, ...
  • web browser enhancements
  • prototyping new features using scripting
  • issue tracking, summarization, and clustering
Jirka Kosek
  • formalization (schemas, formal rules, ...)
  • validation/checking service development
Marco Neumann
  • prototyping new features using scripting
Ian Hickson
  • drafting spec text (which features/sections?)
  • detailed review of substantial sections of spec (which features/sections?)
  • design principles, goals requirements (drafting, review, liaison)
  • issue tracking, summarization, and clustering
  • security review, risk analysis
  • forms taskforce
As editor I'll have to interact with all of the groups, of course, but the ones I've checked are the ones I imagine I'll spend the most time dealing with.
Henri Sivonen
  • detailed review of substantial sections of spec (which features/sections?)
  • formalization (schemas, formal rules, ...)
  • design principles, goals requirements (drafting, review, liaison)
  • validation/checking service development
  • validation/checking service operations
A conformance checking service and a schema are already well under way:
http://hsivonen.iki.fi/validator/html5/
http://syntax.whattf.org/
As a side effect, I have to do substantial review of the sections concerning parsing and non-script-related document conformance.
Already participated in the drafting of the design principles.
Lee Kowalkowski
  • detailed review of substantial sections of spec (which features/sections?)
  • tutorial development, quick reference, course materials, ...
Sections to review are detailed in answer to next question.
Robert Burns
  • detailed review of substantial sections of spec (which features/sections?)
  • web browser enhancements
  • authoring tool development
Henrik Dvergsdal
  • detailed review of substantial sections of spec (which features/sections?)
  • tutorial development, quick reference, course materials, ...
  • formalization (schemas, formal rules, ...)
  • usability testing
  • validation/checking service development
I can provide quick references in various formats (print, html, widgets etc.) and develop different types of formal grammars. I can also assist in accessibility reviewing.
Ariel Pérez
  • drafting spec text (which features/sections?)
  • detailed review of substantial sections of spec (which features/sections?)
  • manual test result (which browser? authoring tools?)
  • tutorial development, quick reference, course materials, ...
  • usability testing
Interested in participate in the definition of the spec, test it in available browsers and eventually elaborate some documentation in Spanish - my mother tongue- about HTML 5
David Håsäther
  • detailed review of substantial sections of spec (which features/sections?)
  • test case development (which kind?)
  • manual test result (which browser? authoring tools?)
  • test suite organization/editing
I've done some test cases, and I expect to do more.
Laurens Holst
  • detailed review of substantial sections of spec (which features/sections?)
  • formalization (schemas, formal rules, ...)
  • prototyping new features using scripting
  • forms taskforce
Review of sections related to my experience and interests.
Joshue O Connor
  • usability testing
We have a full user testing facility in our head office where we can video users (using Morae) and conduct extensive user tests.
Mark Martin
  • a periodic survey of top web sites
  • usability testing
  • prototyping new features using scripting
  • validation/checking service operations
John Bradley
  • tutorial development, quick reference, course materials, ...
  • usability testing
  • security review, risk analysis
Sean Fraser
  • a periodic survey of top web sites
I removed my participation in "tutorial development, quick reference, course materials,..." due to schedule conflicts. However, I will be available with to offer assistance with any member who wants it.
Benoit Piette
  • tutorial development, quick reference, course materials, ...
  • prototyping new features using scripting
I am still figuring out how I can help. I don't have much time, so I can't be in charge of anything big or time consuming. I should also add evangelization of the spec in our local user group. Translation of specs / tutorials in french is also something I could work on.
Denis Boudreau
  • usability testing
  • design principles, goals requirements (drafting, review, liaison)
Carol King
  • detailed review of substantial sections of spec (which features/sections?)
Balakumar Muthu
  • tutorial development, quick reference, course materials, ...
  • a periodic survey of top web sites
  • usability testing
  • validation/checking service development
Gonzalo Rubio
  • drafting spec text (which features/sections?)
  • translation to languages other than English
Alejandro Fernandez
  • usability testing
  • translation to languages other than English
If can do the translation of the documents to spanish.
Stéphane Deschamps
  • tutorial development, quick reference, course materials, ...
  • translation to languages other than English
I'd like to contribute translations to French with an educational approach.
Marek Pawlowski
  • manual test result (which browser? authoring tools?)
  • tutorial development, quick reference, course materials, ...
Few weeks ago I started moving some of my site to HTML5 to check its backward compatibility. I always use most recent versions of IE, Opera, Firefox and Safari.
Being betatester and minor contributor of Polish leading HTML editor I can track issues connected with authoring tools.
Masataka Yakura
  • translation to languages other than English
I could do some translation work (Japanese)
Thomas Bradley
  • tutorial development, quick reference, course materials, ...
  • a periodic survey of top web sites
  • prototyping new features using scripting
Concentration on semantics, structure and accessibility.
Jon Barnett
  • test case development (which kind?)
  • manual test result (which browser? authoring tools?)
  • test suite organization/editing
  • tutorial development, quick reference, course materials, ...
  • authoring tool development
Debi Orton
  • drafting spec text (which features/sections?)
  • detailed review of substantial sections of spec (which features/sections?)
  • tutorial development, quick reference, course materials, ...
  • usability testing
  • issue tracking, summarization, and clustering
I can help with issue tracking, etc, if you use the "breadth-first" approach...I'm a little hesitant to volunteer if you use the "depth-first" approach
Marcin Hanclik
  • detailed review of substantial sections of spec (which features/sections?)
3.14.x
Jason White
  • detailed review of substantial sections of spec (which features/sections?)
  • usability testing
  • design principles, goals requirements (drafting, review, liaison)
  • orientation: documenting group norms, helping people learn them
I am interested in reviewing sections of the spec that have significant
accessibility-related impact, including media elements and the forthcoming
draft of the Forms section. From recent discussions it appears that most of
the relevant issues have already been raised, but I will nevertheless review
the draft and report any further comments. I plan to participate in working
group discussions, particularly, but not exclusively, related to accessibility
and hope to play a constructive role in clarifying issues, discussing
proposals and facilitating the emergence of well designed and practical
solutions.
Sander van Lambalgen
  • detailed review of substantial sections of spec (which features/sections?)
  • tutorial development, quick reference, course materials, ...
  • forms taskforce
(time permitting)

Specifically for sections 3/4 of the current WHATWG web-apps draft, and sections 2/3 of the current WHATWG web-forms draft.
Charles McCathie Nevile
  • detailed review of substantial sections of spec (which features/sections?)
Accessibility features

- what were they in HTML 4 and if they worked did they get into the draft yet?
- what are the new accessibility improvements in the HTML 5 draft.
David McClure
  • drafting spec text (which features/sections?)
  • test case development (which kind?)
  • manual test result (which browser? authoring tools?)
  • test suite organization/editing
  • tutorial development, quick reference, course materials, ...
  • usability testing
  • orientation: documenting group norms, helping people learn them
  • authoring tool development
  • issue tracking, summarization, and clustering
  • forms taskforce
Other tasks as needed.

drafting spec text: any features/sections needed
test case development: any needed
manual test result: Safari/Mac, Firefox/Win are primary, but can download others




Eric Daspet
  • detailed review of substantial sections of spec (which features/sections?)
  • issue tracking, summarization, and clustering
  • translation to languages other than English
- translation of the wg publications in french
Ben Boyle
  • detailed review of substantial sections of spec (which features/sections?)
  • tutorial development, quick reference, course materials, ...
Particular interest in forms. Also in the new document semantics (sections, articles, etc) and newly specificied behaviour of elements (e.g. DFN).
Dimitri Glazkov
  • drafting spec text (which features/sections?)
  • detailed review of substantial sections of spec (which features/sections?)
  • authoring tool development
  • prototyping new features using scripting
Kai Hendry
  • test case development (which kind?)
  • test suite organization/editing
  • tutorial development, quick reference, course materials, ...
  • usability testing
Testing mobile UAs
Matthew Raymond
  • tutorial development, quick reference, course materials, ...
  • web browser maintenance (esp. fixing bugs around spec compliance)
  • web browser enhancements
  • authoring tool development
  • forms taskforce
Adam Roben
  • manual test result (which browser? authoring tools?)
  • web browser maintenance (esp. fixing bugs around spec compliance)
  • web browser enhancements
Happy to provide testing on Safari/WebKit
Ryan King
  • detailed review of substantial sections of spec (which features/sections?)
  • test case development (which kind?)
  • orientation: documenting group norms, helping people learn them
Shawn Medero
  • test case development (which kind?)
  • manual test result (which browser? authoring tools?)
  • a periodic survey of top web sites
  • usability testing
  • issue tracking, summarization, and clustering
Happy to help run a usability session with either lo-fi (paper) or hi-fi (working demo) prototypes in the Philadelphia area. Likewise, I can test prototypes and report back my findings. I usually have access to Linux, Mac OS X, and Windows workstations.
Weston Ruter
  • test case development (which kind?)
  • test suite organization/editing
  • prototyping new features using scripting
I've been developing a WF2 cross-browser implementation (a prototype of the new features using scripting); I will be continuing to prototype new features in the implementation. I've also been developing a WF2 test suite (http://webforms2.googlecode.com/svn/trunk/testsuite/index.html) to test this implementation, and I can head up the development of more tests.
Mikko Honkala
  • drafting spec text (which features/sections?)
  • detailed review of substantial sections of spec (which features/sections?)
  • forms taskforce
My PhD thesis at should be relevant info:
http://lib.tkk.fi/Diss/2007/isbn9789512285662/
Mark Baker
  • drafting spec text (which features/sections?)
  • detailed review of substantial sections of spec (which features/sections?)
  • design principles, goals requirements (drafting, review, liaison)
mostly interested in parts of spec that touch on other aspects of the Web, e.g. HTTP-related, URI-related, media types, ...
Marghanita da Cruz
  • drafting spec text (which features/sections?)
  • test case development (which kind?)
  • design principles, goals requirements (drafting, review, liaison)
  • security review, risk analysis
<http://www.ramin.com.au/linux/review-of-html5.shtml>
Joseph D'Andrea
  • manual test result (which browser? authoring tools?)
  • tutorial development, quick reference, course materials, ...
  • validation/checking service development
  • validation/checking service operations
All MacOS X-based browsers available (and Windows XP via Parallels on MacOS). Happy to pitch in with Validation/Checking service dev/ops as needed.
Geoffrey Sneddon
  • detailed review of substantial sections of spec (which features/sections?)
  • tutorial development, quick reference, course materials, ...
  • issue tracking, summarization, and clustering
Detailed review of any sections that involve the parsing of any HTML documents (through reading them with a fine tooth-comb while implementing them).

I'm willing to help with the tutorial/whatever writing (as general writing of things like that is far far better than my writing of specs), depending on what the decision is of what sort of document(s) to write.

I'm also willing to help move data into the issue tracker, from external sources, though how much I do that will inevitably be very time dependant (as I'd rather do the two above before I did such a thing).
Scott Vesey
  • manual test result (which browser? authoring tools?)
  • tutorial development, quick reference, course materials, ...
exploring release of internal test framework to public domain.
Justin Thorp
  • detailed review of substantial sections of spec (which features/sections?)
  • test case development (which kind?)
  • manual test result (which browser? authoring tools?)
  • tutorial development, quick reference, course materials, ...
  • a periodic survey of top web sites
  • orientation: documenting group norms, helping people learn them
Doug Jones
  • tutorial development, quick reference, course materials, ...
Ivan Enderlin
  • drafting spec text (which features/sections?)
  • tutorial development, quick reference, course materials, ...
  • orientation: documenting group norms, helping people learn them
I'm particulary interesting by making turorial development and helping people to learn.
Wesley Upchurch
  • tutorial development, quick reference, course materials, ...
Preston Bannister
  • tutorial development, quick reference, course materials, ...
  • design principles, goals requirements (drafting, review, liaison)
  • orientation: documenting group norms, helping people learn them
  • prototyping new features using scripting
  • security review, risk analysis
Sierk Bornemann
  • detailed review of substantial sections of spec (which features/sections?)
  • design principles, goals requirements (drafting, review, liaison)
  • validation/checking service development
  • validation/checking service operations
I would participate or lead (with help of experts) in working out a solution to enrich (X)HTML 5 with appropriate markup elements and attributes for an effective anti-SPAM protection mechanism against harvesting email addresses and chat messenger IDs, as http://www.w3.org/TR/xmldsig-core/ and, more concrete, http://xmlns.com/foaf/spec/#term_mbox_sha1sum provide and recommend for their purposes.
Sam Kuper
  • formalization (schemas, formal rules, ...)
Samuel Santos
  • drafting spec text (which features/sections?)
  • a periodic survey of top web sites
  • usability testing
  • design principles, goals requirements (drafting, review, liaison)
  • issue tracking, summarization, and clustering
  • forms taskforce
Drafting for and reviewing mainly the "Semantics and structure of HTML elements" section.
Since I'm a developer, my main concern is to help producing a specification that is the best it can be for web applications.
Raphael Champeimont
Karl Groves
  • detailed review of substantial sections of spec (which features/sections?)
  • tutorial development, quick reference, course materials, ...
  • a periodic survey of top web sites
  • usability testing
I would be deeply interested in assisting wherever I am capable, but primarily in areas cited above as my areas of interest. As I get my feet wet within the WG, I may be interested in expanding my involvement.

Specifically regarding my answer to which sections of the spec I'd be willing to review, I would say on a broad view it would be "Semantics and structure of HTML elements" and more specifically, Section 3.3, "3.3 Documents and document fragments" as well as the discussions of forms and tables.
aurélien levy
  • test case development (which kind?)
  • manual test result (which browser? authoring tools?)
  • usability testing
accessibility features of html
David Singer
  • drafting spec text (which features/sections?)
David Randall
  • tutorial development, quick reference, course materials, ...
  • a periodic survey of top web sites
  • usability testing
  • web browser enhancements
Bill Mason
Kelly Gifford
  • tutorial development, quick reference, course materials, ...
  • usability testing
  • orientation: documenting group norms, helping people learn them
Sam Johnston
  • drafting spec text (which features/sections?)
  • detailed review of substantial sections of spec (which features/sections?)
  • design principles, goals requirements (drafting, review, liaison)
  • security review, risk analysis
Primarily interested in items relevant to web application development.
Dean Edridge
Cynthia Shelly
  • drafting spec text (which features/sections?)
  • detailed review of substantial sections of spec (which features/sections?)
  • issue tracking, summarization, and clustering
  • forms taskforce
My primary goal in this group is around driving practical technical solutions for tricky accessibiltiy problems, in a way that can meet the needs of both accessibility consumers and mainstream web authors. I'm happy to do whatever is needed to further that goal.

Areas where I think I can have the most impact are forms, reviewing existing spec text, and issue tracking. I'd be glad to write spec text or test cases where needed, and I've done both for WCAG.
Dionysios Synodinos
  • drafting spec text (which features/sections?)
  • detailed review of substantial sections of spec (which features/sections?)
  • design principles, goals requirements (drafting, review, liaison)
  • security review, risk analysis
  • forms taskforce
Simon Pieters
  • detailed review of substantial sections of spec (which features/sections?)
  • test case development (which kind?)
  • manual test result (which browser? authoring tools?)
  • test suite organization/editing
  • web browser maintenance (esp. fixing bugs around spec compliance)
Terry Morris
  • a periodic survey of top web sites
  • design principles, goals requirements (drafting, review, liaison)
Ben Millard
  • drafting spec text (which features/sections?)
  • manual test result (which browser? authoring tools?)
  • a periodic survey of top web sites
  • issue tracking, summarization, and clustering
* Research into accessible table markup:
<http://projectcerbera.com/web/study/2007/tables/>
* Newest round of research, with broader scope:
<http://projectcerbera.com/web/study/2008/collection/>
* Some ability to summarise differing views on controversial issues.
* Trends, changes and practices in the web industry.
* Tidying markup examples in discussions and examples.
* Accessibility impact of proposals.
Dan Connolly
  • test case development (which kind?)
  • formalization (schemas, formal rules, ...)
  • validation/checking service development
  • issue tracking, summarization, and clustering
  • serve as scribe for teleconferences
I'm particularly interested in testing the tree construction stuff in a validator-like online service.
Julian Reschke
  • formalization (schemas, formal rules, ...)
  • design principles, goals requirements (drafting, review, liaison)
  • issue tracking, summarization, and clustering
  • serve as scribe for teleconferences
Channy Yun
  • test case development (which kind?)
  • tutorial development, quick reference, course materials, ...
  • translation to languages other than English
Larry Masinter
  • drafting spec text (which features/sections?)
  • detailed review of substantial sections of spec (which features/sections?)
  • test case development (which kind?)
  • manual test result (which browser? authoring tools?)
  • test suite organization/editing
  • tutorial development, quick reference, course materials, ...
  • formalization (schemas, formal rules, ...)
  • design principles, goals requirements (drafting, review, liaison)
  • orientation: documenting group norms, helping people learn them
  • authoring tool development
  • prototyping new features using scripting
  • issue tracking, summarization, and clustering
  • security review, risk analysis
  • serve as scribe for teleconferences
Laura Carlson
  • drafting spec text (which features/sections?)
  • design principles, goals requirements (drafting, review, liaison)
  • issue tracking, summarization, and clustering
TEXT ALTERNATIVES ISSUE (@alt):

- Working on ISSUE 31 with SteveF, Joshue O Connor and others
http://www.w3.org/html/wg/tracker/issues/31

- Created Wiki page on the "Omitting Text Alternatives for Critical Content" issue.
http://esw.w3.org/topic/HTML/IssueAltAttribute

- Requested PFWG WAI to review Omitting alt Attribute for Critical Content and provide advice on the potential accessibility impact.
http://lists.w3.org/Archives/Public/wai-xtech/2007Oct/0044.html

- Worked on ACTION 54 with SteveF, Joshue O Connor and others to draft text for HTML 5 spec to require producers/authors to include @alt on img elements.
http://www.w3.org/html/wg/tracker/actions/54

- Created Wiki page "Action 54: First Draft"
http://esw.w3.org/topic/HTML/Action54AltAttribute

- Created Discussion Page for "Action 54: First Draft"
http://esw.w3.org/topic/HTML/Action54AltAttributeDiscussion

- Created Wiki page "Action 54: Second Draft"
http://esw.w3.org/topic/HTML/Action54AltAttributeSecondDraft

- Created Wiki page "Action 54: Third Draft"
http://esw.w3.org/topic/HTML/Action54AltAttributeThirdDraft

- Participated in WAI CG Task Force which produced Consensus Resolutions on Text alternatives in HTML 5
http://www.w3.org/2009/06/Text-Alternatives-in-HTML5

- Worked with SteveF Cynthia Shelly, Matt May and others on ACTION 131 to draft ALT spec
http://www.w3.org/html/wg/tracker/actions/131

- Action 131 Deliverable
http://www.w3.org/2009/06/Text-Alternatives-in-HTML5


@SUMMARY ISSUE:

- Working on ISSUE-32 with SteveF, Joshue O Connor and others on table summary
http://www.w3.org/html/wg/tracker/issues/32

- Worked on "Mechanism to Summarize a Table" Wiki page
http://esw.w3.org/topic/HTML/SummaryForTABLE

- Worked on ACTION-66 with SteveF, Joshue O Connor and others to collate information
http://www.w3.org/html/wg/tracker/actions/66

- Worked on ACTION-111 to move issue 32 toward resolution by asking PFWG for comments on several items:
http://lists.w3.org/Archives/Public/public-html/2009May/0033.html
http://www.w3.org/html/wg/tracker/actions/111


CANVAS ELEMENT

- Working on ISSUE-74 Canvas accessibility
http://www.w3.org/html/wg/tracker/issues/74

- Created Wiki page "New canvas Element Accessibility Issues"
http://esw.w3.org/topic/HTML/AddedElementCanvas


MULTIMEDIA <Audio> <Video>

- Created Wiki page "Multimedia Accessibility (<Audio> <Video>)"
http://esw.w3.org/topic/HTML/MultimediaAccessibilty

- Requested PFWG WAI to review multimedia accessibility requirements <audio> <video>
http://lists.w3.org/Archives/Public/public-html/2008Sep/0421.html


DESIGN PRINCIPLES

- Collaborated with other working group members to author:
"Request to Strengthen the HTML5 Accessibility Design Principle"
http://esw.w3.org/topic/HTML/AccessibilityDesignPrinciple
http://lists.w3.org/Archives/Public/public-html/2009Jun/0661.html
http://lists.w3.org/Archives/Public/public-html/2009Jul/0249.html

- Helped with Design Principles Wiki page. e.g. helped identify and document disputed principles.
http://esw.w3.org/topic/HTML/ProposedDesignPrinciples?action=recall&rev=78#head-f6eb28b3b561a144b2d4a9af50467f4692b8bffc


ACCESSIBILITY ISSUES PROCEDURE

- Collaborated with other working group members to author:
"Procedure to Promote Progress With Accessibility Issues in HTML5" Proposal
http://esw.w3.org/topic/HTML/AccessibilityIssueProcedure

- Created Discussion Page for Accessibility Issues Procedure:
http://esw.w3.org/topic/HTML/AccessibilityIssueProcedure/Discussion


@HEADERS ISSUE:

- Requested PFWG WAI to review headers/id attribute and provide advice on the on the potential accessibility impact.
http://lists.w3.org/Archives/Public/wai-xtech/2007May/0049.html

- Created Wiki page "headers attribute Issue"
http://esw.w3.org/topic/HTML/IssueTableHeaders

- Worked on ISSUES-57/20 with SteveF, Joshue O Connor and others on @headers
http://www.w3.org/html/wg/tracker/issues/57
http://www.w3.org/html/wg/tracker/issues/20

- Worked on ACTION-72 with SteveF, Joshue O Connor and others to draft text for the HTML 5 spec
http://www.w3.org/html/wg/tracker/actions/72

- Created Wiki page "ACTION 72: @headers rewrite" deliverable:
http://esw.w3.org/topic/HTML/Action72Headers

- Created Wiki page "headers/id Testing (Bug 5822)"
http://esw.w3.org/topic/HTML/TableHeadersTestingBug5822

- Created Wiki page "Cyclic Header Chains"
http://esw.w3.org/topic/HTML/CyclicHeaderChains


- FURTHER WG WORK

- Helped with HTML Working Group Issue and Action Definitions
http://esw.w3.org/topic/HTML

- Created Wiki page "HTML WG Meeting Minutes"
http://esw.w3.org/topic/HTML/Minutes

- Created Wiki page "HTML WG Surveys"
http://esw.w3.org/topic/HTML/Surveys

- Created Wiki page "HTML WG Email Lists"
http://esw.w3.org/topic/HTML/EmailLists

- Created Wiki page "HTML WG Teleconferences"
http://esw.w3.org/topic/HTML/Teleconferences

- Created Wiki page "HTMLWG Requests and PFWG Responses"
http://esw.w3.org/topic/HTML/HTMLRequestsPFresponse

- Participating in PFWG Caucus on HTML5 Issues
http://esw.w3.org/topic/PF/XTech/HTML5/Caucus

- Started justification Wiki pages for dropped/added/changed elements and attributes.
Martin McEvoy
  • design principles, goals requirements (drafting, review, liaison)
  • web browser enhancements
  • authoring tool development
Ryan Mitchell
John Stewart
  • drafting spec text (which features/sections?)
  • detailed review of substantial sections of spec (which features/sections?)
  • test case development (which kind?)
  • web browser enhancements
X3D integration related tasks.
Jace Voracek
  • test case development (which kind?)
  • manual test result (which browser? authoring tools?)
  • tutorial development, quick reference, course materials, ...
  • a periodic survey of top web sites
  • usability testing
  • web browser maintenance (esp. fixing bugs around spec compliance)
  • web browser enhancements
  • validation/checking service development
  • translation to languages other than English
Due to my occupied work schedule, my time availability affects the work of what I am able to do time-based. Because of this, my interest of what I am able to do may shift depending on my schedule. Overall, I am generally willing to assist in tasks that are in current demand.

Regarding testing, I primarily use Apple Safari. I am also willing to test on the iPhone's Mobile Safari.

View by choice

ChoiceResponders
drafting spec text (which features/sections?)
  • Murray Maloney
  • Dominik Tomaszuk
  • David Hyatt
  • Jonas Sicking
  • Roman Kitainik
  • Matthew Wilcox
  • Michael Turnwall
  • Gregory Rosmaita
  • Karl Dubost
  • Ian Hickson
  • Ariel Pérez
  • Gonzalo Rubio
  • Debi Orton
  • David McClure
  • Dimitri Glazkov
  • Mikko Honkala
  • Mark Baker
  • Marghanita da Cruz
  • Ivan Enderlin
  • Samuel Santos
  • David Singer
  • Sam Johnston
  • Cynthia Shelly
  • Dionysios Synodinos
  • Ben Millard
  • Larry Masinter
  • Laura Carlson
  • John Stewart
detailed review of substantial sections of spec (which features/sections?)
  • Murray Maloney
  • Asbjørn Ulsberg
  • John-Mark Bell
  • Maciej Stachowiak
  • Andrew Neitsch
  • Thomas Higginbotham
  • David Hyatt
  • Serdar Kiliç
  • Isac Lagerblad
  • Patrick Taylor
  • Jonas Sicking
  • Roman Kitainik
  • Matthew Wilcox
  • Anne van Kesteren
  • Craig Saila
  • Darren West
  • Karl Dubost
  • Jens Meiert
  • Ian Hickson
  • Henri Sivonen
  • Lee Kowalkowski
  • Robert Burns
  • Henrik Dvergsdal
  • Ariel Pérez
  • David Håsäther
  • Laurens Holst
  • Carol King
  • Debi Orton
  • Marcin Hanclik
  • Jason White
  • Sander van Lambalgen
  • Charles McCathie Nevile
  • Eric Daspet
  • Ben Boyle
  • Dimitri Glazkov
  • Ryan King
  • Mikko Honkala
  • Mark Baker
  • Geoffrey Sneddon
  • Justin Thorp
  • Sierk Bornemann
  • Karl Groves
  • Sam Johnston
  • Cynthia Shelly
  • Dionysios Synodinos
  • Simon Pieters
  • Larry Masinter
  • John Stewart
test case development (which kind?)
  • Chasen Le Hara
  • Mihai Sucan
  • Asbjørn Ulsberg
  • David Baron
  • John-Mark Bell
  • Maciej Stachowiak
  • Magnus Kristiansen
  • Henrik Lied
  • Thomas Higginbotham
  • David Hyatt
  • Roman Kitainik
  • Anne van Kesteren
  • James Graham
  • Gregory Rosmaita
  • Karl Dubost
  • Marco Battilana
  • David Håsäther
  • Jon Barnett
  • David McClure
  • Kai Hendry
  • Ryan King
  • Shawn Medero
  • Weston Ruter
  • Marghanita da Cruz
  • Justin Thorp
  • aurélien levy
  • Simon Pieters
  • Dan Connolly
  • Channy Yun
  • Larry Masinter
  • John Stewart
  • Jace Voracek
manual test result (which browser? authoring tools?)
  • Chasen Le Hara
  • Maciej Stachowiak
  • Szymon Pilkowski
  • Serdar Kiliç
  • Patrick Taylor
  • Jonas Sicking
  • Roman Kitainik
  • Craig Saila
  • Gregory Rosmaita
  • Marco Battilana
  • Andrew Smith
  • Stephen Axthelm
  • Account Deleted
  • Chris Adams
  • Ariel Pérez
  • David Håsäther
  • Marek Pawlowski
  • Jon Barnett
  • David McClure
  • Adam Roben
  • Shawn Medero
  • Joseph D'Andrea
  • Scott Vesey
  • Justin Thorp
  • aurélien levy
  • Simon Pieters
  • Ben Millard
  • Larry Masinter
  • Jace Voracek
test suite organization/editing
  • Chasen Le Hara
  • Matthew Ratzloff
  • Dominik Tomaszuk
  • Roman Kitainik
  • Gregory Rosmaita
  • David Håsäther
  • Jon Barnett
  • David McClure
  • Kai Hendry
  • Weston Ruter
  • Simon Pieters
  • Larry Masinter
tutorial development, quick reference, course materials, ...
  • Chasen Le Hara
  • Dylan Smith
  • Kornel Lesinski
  • David Dailey
  • Mihai Sucan
  • Asbjørn Ulsberg
  • Brad Fults
  • Roger Johansson
  • M. Jackson Wilkinson
  • Bhasker V Kode
  • Henrik Lied
  • Stephen Stewart
  • Matthew Ratzloff
  • Dominik Tomaszuk
  • Nicolas Le Gall
  • Isac Lagerblad
  • Patrick Taylor
  • Roman Kitainik
  • Addam Wassel
  • James VanDyke
  • Craig Saila
  • Benjamin Hedrington
  • Karl Dubost
  • Yannick Croissant
  • Jens Meiert
  • Chris Adams
  • Lee Kowalkowski
  • Henrik Dvergsdal
  • Ariel Pérez
  • John Bradley
  • Benoit Piette
  • Balakumar Muthu
  • Stéphane Deschamps
  • Marek Pawlowski
  • Thomas Bradley
  • Jon Barnett
  • Debi Orton
  • Sander van Lambalgen
  • David McClure
  • Ben Boyle
  • Kai Hendry
  • Matthew Raymond
  • Joseph D'Andrea
  • Geoffrey Sneddon
  • Scott Vesey
  • Justin Thorp
  • Doug Jones
  • Ivan Enderlin
  • Wesley Upchurch
  • Preston Bannister
  • Karl Groves
  • David Randall
  • Kelly Gifford
  • Channy Yun
  • Larry Masinter
  • Jace Voracek
formalization (schemas, formal rules, ...)
  • Josef Spillner
  • Dominik Tomaszuk
  • Gregory Rosmaita
  • Andrew Smith
  • Jirka Kosek
  • Henri Sivonen
  • Henrik Dvergsdal
  • Laurens Holst
  • Sam Kuper
  • Dan Connolly
  • Julian Reschke
  • Larry Masinter
a periodic survey of top web sites
  • M. Jackson Wilkinson
  • Serdar Kiliç
  • Rene Saarsoo
  • Patrick Taylor
  • Roman Kitainik
  • James VanDyke
  • Craig Saila
  • Michael Turnwall
  • Benjamin Hedrington
  • Karl Dubost
  • Marco Battilana
  • Andrew Smith
  • Eric Eggert
  • Mark Martin
  • Sean Fraser
  • Balakumar Muthu
  • Thomas Bradley
  • Shawn Medero
  • Justin Thorp
  • Samuel Santos
  • Karl Groves
  • David Randall
  • Terry Morris
  • Ben Millard
  • Jace Voracek
usability testing
  • Chasen Le Hara
  • Dylan Smith
  • David Dailey
  • Tim McMahon
  • M. Jackson Wilkinson
  • Andrew Neitsch
  • Henrik Lied
  • Dominik Tomaszuk
  • Isac Lagerblad
  • Patrick Taylor
  • Roman Kitainik
  • Addam Wassel
  • James VanDyke
  • Michael Turnwall
  • Gregory Rosmaita
  • Marco Battilana
  • Andrew Smith
  • Jens Meiert
  • Account Deleted
  • Henrik Dvergsdal
  • Ariel Pérez
  • Joshue O Connor
  • Mark Martin
  • John Bradley
  • Denis Boudreau
  • Balakumar Muthu
  • Alejandro Fernandez
  • Debi Orton
  • Jason White
  • David McClure
  • Kai Hendry
  • Shawn Medero
  • Samuel Santos
  • Karl Groves
  • aurélien levy
  • David Randall
  • Kelly Gifford
  • Jace Voracek
design principles, goals requirements (drafting, review, liaison)
  • Murray Maloney
  • Kornel Lesinski
  • David Dailey
  • Brad Fults
  • David Baron
  • Tim McMahon
  • Maciej Stachowiak
  • Bhasker V Kode
  • Jonas Sicking
  • Roman Kitainik
  • Matthew Wilcox
  • Anne van Kesteren
  • Craig Saila
  • Gregory Rosmaita
  • Benjamin Hedrington
  • Marco Battilana
  • Andrew Smith
  • Jens Meiert
  • Eric Eggert
  • Ian Hickson
  • Henri Sivonen
  • Denis Boudreau
  • Jason White
  • Mark Baker
  • Marghanita da Cruz
  • Preston Bannister
  • Sierk Bornemann
  • Samuel Santos
  • Sam Johnston
  • Dionysios Synodinos
  • Terry Morris
  • Julian Reschke
  • Larry Masinter
  • Laura Carlson
  • Martin McEvoy
orientation: documenting group norms, helping people learn them
  • David Dailey
  • Nicolas Le Gall
  • Roman Kitainik
  • Yannick Croissant
  • Marco Battilana
  • Stephen Axthelm
  • Jason White
  • David McClure
  • Ryan King
  • Justin Thorp
  • Ivan Enderlin
  • Preston Bannister
  • Kelly Gifford
  • Larry Masinter
web browser maintenance (esp. fixing bugs around spec compliance)
  • Chris Veenboer
  • David Baron
  • John-Mark Bell
  • Maciej Stachowiak
  • Szymon Pilkowski
  • David Hyatt
  • Jonas Sicking
  • Roman Kitainik
  • Gregory Rosmaita
  • Andrei Polushin
  • Matthew Raymond
  • Adam Roben
  • Simon Pieters
  • Jace Voracek
web browser enhancements
  • David Baron
  • John-Mark Bell
  • Maciej Stachowiak
  • Bhasker V Kode
  • David Hyatt
  • Jonas Sicking
  • Roman Kitainik
  • Andrei Polushin
  • Chris Adams
  • Robert Burns
  • Matthew Raymond
  • Adam Roben
  • David Randall
  • Martin McEvoy
  • John Stewart
  • Jace Voracek
authoring tool development
  • Chasen Le Hara
  • Mihai Sucan
  • Tim McMahon
  • Alfonso Martínez de Lizarrondo
  • Josef Spillner
  • Patrick Taylor
  • Roman Kitainik
  • Gregory Rosmaita
  • Robert Burns
  • Jon Barnett
  • David McClure
  • Dimitri Glazkov
  • Matthew Raymond
  • Larry Masinter
  • Martin McEvoy
prototyping new features using scripting
  • Chasen Le Hara
  • Kornel Lesinski
  • Chris Veenboer
  • Mihai Sucan
  • Asbjørn Ulsberg
  • Bhasker V Kode
  • Magnus Kristiansen
  • Serdar Kiliç
  • Darren West
  • Benjamin Hedrington
  • Chris Adams
  • Marco Neumann
  • Laurens Holst
  • Mark Martin
  • Benoit Piette
  • Thomas Bradley
  • Dimitri Glazkov
  • Weston Ruter
  • Preston Bannister
  • Larry Masinter
validation/checking service development
  • Chasen Le Hara
  • Kornel Lesinski
  • Josef Spillner
  • Dominik Tomaszuk
  • James Graham
  • Gregory Rosmaita
  • Karl Dubost
  • Jirka Kosek
  • Henri Sivonen
  • Henrik Dvergsdal
  • Balakumar Muthu
  • Joseph D'Andrea
  • Sierk Bornemann
  • Dan Connolly
  • Jace Voracek
validation/checking service operations
  • Chasen Le Hara
  • Dominik Tomaszuk
  • Karl Dubost
  • Stephen Axthelm
  • Henri Sivonen
  • Mark Martin
  • Joseph D'Andrea
  • Sierk Bornemann
issue tracking, summarization, and clustering
  • Chasen Le Hara
  • David Dailey
  • Roman Kitainik
  • James Graham
  • Benjamin Hedrington
  • Karl Dubost
  • Jens Meiert
  • Stephen Axthelm
  • Chris Adams
  • Ian Hickson
  • Debi Orton
  • David McClure
  • Eric Daspet
  • Shawn Medero
  • Geoffrey Sneddon
  • Samuel Santos
  • Cynthia Shelly
  • Ben Millard
  • Dan Connolly
  • Julian Reschke
  • Larry Masinter
  • Laura Carlson
security review, risk analysis
  • Chasen Le Hara
  • Kornel Lesinski
  • Maciej Stachowiak
  • Jonas Sicking
  • Ian Hickson
  • John Bradley
  • Marghanita da Cruz
  • Preston Bannister
  • Sam Johnston
  • Dionysios Synodinos
  • Larry Masinter
forms taskforce
  • Maciej Stachowiak
  • Josef Spillner
  • Dominik Tomaszuk
  • John Boyer
  • Anne van Kesteren
  • Darren West
  • Gregory Rosmaita
  • Account Deleted
  • Ian Hickson
  • Laurens Holst
  • Sander van Lambalgen
  • David McClure
  • Matthew Raymond
  • Mikko Honkala
  • Samuel Santos
  • Cynthia Shelly
  • Dionysios Synodinos
translation to languages other than English
  • Gonzalo Rubio
  • Alejandro Fernandez
  • Stéphane Deschamps
  • Masataka Yakura
  • Eric Daspet
  • Channy Yun
  • Jace Voracek
serve as scribe for teleconferences
  • Dan Connolly
  • Julian Reschke
  • Larry Masinter

3. Which section(s) are you planning to review in detail in the coming weeks?

summary | by responder | by choice

Please choose one or a few sections that you plan to review in detail in the coming weeks.

Suggestions on sending comments for review:

Consider summarizing the discussion of the issues you raised in the wiki issues list. Keep in mind an obligation to summarize points of view even when you disagree with them.

This list of sections to review is based on v1.78 of Thu Jun 7 00:53:39 2007 UTC of the editor's draft of the HTML 5 spec , with some arbitrary choices about which subsections to lump together.

Summary

ChoiceAll responders
Results
1. Introduction 6
2. The Document Object Model 6
3.1. Introduction (Semantics and structure of HTML elements) 12
3.2. Common microsyntaxes 5
3.3. Documents and document fragments 8
3.4. Global attributes 8
3.5. Interaction 4
3.6. The root element 4
3.7. Document metadata 8
3.8. Sections 10
3.9. Prose 8
3.10. Preformatted text 6
3.11. Lists 7
3.12. Phrase elements 7
3.13. Edits 6
3.14. Embedded content (subsection 1-4, figure to embed) 7
3.14.5. The object element (and o 3.14.6. The param element) 3
3.14.7. The video element 10
3.14.8. The audio element 8
3.14.9. Media elements 8
3.14.10. The source element 4
3.14.11. The canvas element 4
3.14.12. The map element thru 3.14.14. Image maps 4
3.15. Tabular data 6
3.16. Forms 14
3.17. Scripting 6
3.18. Interactive elements (inc. datagrid) 7
3.19. Miscellaneous elements (legend, div) 6
4. Web browsers (4.1 browsing context to 4.3 Session history) 3
4.4. Links 4
4.5. Interfaces for URI manipulation 3
4.6 Navigating across documents 2
4.7. Determining the type of a new resource in a browsing context 6
4.8. User prompts 3
4.9. Scripting 3
4.10. Browser state 3
4.11. Client-side session and persistent storage of name/value pairs 6
4.12. Client-side database storage 4
5. Editing 5
6. Communication 2
7. Repetition templates 4
8. The HTML syntax: * 8.1. Writing HTML documents 6
8.2. Parsing HTML documents 6
8.3. Namespaces 4
8.4. Entities 2
9. WYSIWYG editors 6
10. Rendering 1
11. Things that you can't do with this 3

Skip to view by choice.

View by responder

Details

Responder Which section(s) are you planning to review in detail in the coming weeks?Comments
Chasen Le Hara
Dylan Smith
Murray Maloney
Kornel Lesinski
David Dailey
Chris Veenboer
Mihai Sucan
Asbjørn Ulsberg
Brad Fults
Roger Johansson
David Baron
John-Mark Bell
Tim McMahon
M. Jackson Wilkinson
Maciej Stachowiak
Andrew Neitsch
Bhasker V Kode
Magnus Kristiansen
Alfonso Martínez de Lizarrondo
Szymon Pilkowski
Josef Spillner
Henrik Lied
Stephen Stewart
Matthew Ratzloff
Dominik Tomaszuk
Thomas Higginbotham
David Hyatt
Nicolas Le Gall
Serdar Kiliç
John Boyer
Isac Lagerblad
Rene Saarsoo
Patrick Taylor
Jonas Sicking
Roman Kitainik
Addam Wassel
James VanDyke
Matthew Wilcox
Anne van Kesteren
Craig Saila
Darren West
Michael Turnwall
James Graham
Gregory Rosmaita
Benjamin Hedrington
Karl Dubost
Yannick Croissant
Marco Battilana
Andrew Smith
Jens Meiert
Eric Eggert
Stephen Axthelm
Account Deleted
Andrei Polushin
Chris Adams
Jirka Kosek
  • 8.3. Namespaces
  • 8.4. Entities
Marco Neumann
  • 3.7. Document metadata
  • 3.14.12. The map element thru 3.14.14. Image maps
  • 8.2. Parsing HTML documents
Ian Hickson
Henri Sivonen
  • 8.2. Parsing HTML documents
  • 8.3. Namespaces
Lee Kowalkowski
  • 1. Introduction
  • 2. The Document Object Model
  • 4. Web browsers (4.1 browsing context to 4.3 Session history)
  • 4.4. Links
  • 4.5. Interfaces for URI manipulation
  • 4.6 Navigating across documents
  • 4.7. Determining the type of a new resource in a browsing context
  • 4.8. User prompts
  • 4.9. Scripting
  • 4.10. Browser state
  • 4.11. Client-side session and persistent storage of name/value pairs
  • 4.12. Client-side database storage
I might review other sections if I have the time.
Robert Burns
  • 3.8. Sections
  • 3.9. Prose
  • 3.15. Tabular data
  • 9. WYSIWYG editors
Henrik Dvergsdal
  • 5. Editing
Ariel Pérez
  • 3.8. Sections
  • 9. WYSIWYG editors
David Håsäther This will depend on the amount of time I can commit.
Laurens Holst
Joshue O Connor I am particularly interested in HTML 5 and accessibility/usability.
Mark Martin
John Bradley
  • 2. The Document Object Model
  • 3.1. Introduction (Semantics and structure of HTML elements)
  • 3.2. Common microsyntaxes
  • 3.3. Documents and document fragments
Sean Fraser
Benoit Piette
  • 3.14.7. The video element
Denis Boudreau
  • 8. The HTML syntax: * 8.1. Writing HTML documents
Carol King
  • 3.1. Introduction (Semantics and structure of HTML elements)
Balakumar Muthu
  • 3.5. Interaction
  • 3.11. Lists
  • 3.16. Forms
  • 9. WYSIWYG editors
Gonzalo Rubio
  • 3.4. Global attributes
  • 3.8. Sections
Alejandro Fernandez
Stéphane Deschamps
Marek Pawlowski I'm not sure I'd have time for detailed review but I'll try do some brief review.
Masataka Yakura
Thomas Bradley
Jon Barnett
  • 5. Editing
If the spec details the DOM of designMode, I'll happily review it.
Debi Orton
  • 3.1. Introduction (Semantics and structure of HTML elements)
  • 3.11. Lists
  • 3.15. Tabular data
  • 3.16. Forms
  • 3.19. Miscellaneous elements (legend, div)
Marcin Hanclik
  • 3.14.7. The video element
  • 3.14.8. The audio element
  • 3.14.9. Media elements
Jason White
Sander van Lambalgen
  • 2. The Document Object Model
  • 3.1. Introduction (Semantics and structure of HTML elements)
  • 3.3. Documents and document fragments
  • 3.4. Global attributes
  • 3.5. Interaction
  • 3.6. The root element
  • 3.7. Document metadata
  • 3.8. Sections
  • 3.9. Prose
  • 3.10. Preformatted text
  • 3.11. Lists
  • 3.12. Phrase elements
  • 3.13. Edits
  • 3.14. Embedded content (subsection 1-4, figure to embed)
  • 3.14.11. The canvas element
  • 3.16. Forms
  • 3.17. Scripting
  • 3.18. Interactive elements (inc. datagrid)
  • 3.19. Miscellaneous elements (legend, div)
  • 7. Repetition templates
This initial selection is what I plan to look at; as it's a lot of text, I'll probably narrow down that selection after a first pass, based on what I feel I'm actually qualified to say anything on.
Charles McCathie Nevile Starting from http://www.w3.org/WAI/References/HTML4-access and HTML 4, and then chug through the differences document to find the things that seem to need reading
David McClure
Eric Daspet
  • 3.16. Forms
Ben Boyle
  • 3.1. Introduction (Semantics and structure of HTML elements)
  • 3.2. Common microsyntaxes
  • 3.3. Documents and document fragments
  • 3.4. Global attributes
  • 3.6. The root element
  • 3.7. Document metadata
  • 3.8. Sections
  • 3.9. Prose
  • 3.10. Preformatted text
  • 3.11. Lists
  • 3.12. Phrase elements
  • 3.13. Edits
  • 3.14. Embedded content (subsection 1-4, figure to embed)
  • 3.14.7. The video element
  • 3.14.8. The audio element
  • 3.14.9. Media elements
  • 3.14.10. The source element
  • 3.14.11. The canvas element
  • 3.14.12. The map element thru 3.14.14. Image maps
  • 3.15. Tabular data
  • 3.16. Forms
  • 3.17. Scripting
  • 3.18. Interactive elements (inc. datagrid)
  • 3.19. Miscellaneous elements (legend, div)
  • 4.4. Links
  • 4.5. Interfaces for URI manipulation
  • 5. Editing
  • 8. The HTML syntax: * 8.1. Writing HTML documents
  • 8.3. Namespaces
  • 9. WYSIWYG editors
  • 11. Things that you can't do with this
Dimitri Glazkov
  • 4.10. Browser state
  • 4.11. Client-side session and persistent storage of name/value pairs
  • 4.12. Client-side database storage
  • 7. Repetition templates
Kai Hendry
Matthew Raymond
  • 3.2. Common microsyntaxes
  • 3.7. Document metadata
  • 3.14.7. The video element
  • 3.14.9. Media elements
  • 3.16. Forms
  • 3.18. Interactive elements (inc. datagrid)
  • 7. Repetition templates
May review limited portions of sections not checked above.
Adam Roben
Ryan King
  • 4.7. Determining the type of a new resource in a browsing context
  • 8.2. Parsing HTML documents
Shawn Medero
Weston Ruter
  • 3.16. Forms
Mikko Honkala
  • 3.16. Forms
  • 4.11. Client-side session and persistent storage of name/value pairs
  • 4.12. Client-side database storage
Mark Baker
  • 4.7. Determining the type of a new resource in a browsing context
  • 4.11. Client-side session and persistent storage of name/value pairs
  • 5. Editing
  • 6. Communication
Marghanita da Cruz
  • 1. Introduction
  • 2. The Document Object Model
  • 3.1. Introduction (Semantics and structure of HTML elements)
  • 3.14. Embedded content (subsection 1-4, figure to embed)
  • 3.14.5. The object element (and o 3.14.6. The param element)
  • 3.14.7. The video element
  • 3.14.8. The audio element
  • 3.14.9. Media elements
  • 4. Web browsers (4.1 browsing context to 4.3 Session history)
  • 4.8. User prompts
  • 8. The HTML syntax: * 8.1. Writing HTML documents
<http://www.ramin.com.au/linux/review-of-html5.shtml#current-reviews>
Joseph D'Andrea
Geoffrey Sneddon
  • 3.2. Common microsyntaxes
  • 3.3. Documents and document fragments
  • 3.4. Global attributes
  • 3.6. The root element
  • 3.7. Document metadata
  • 3.8. Sections
  • 3.9. Prose
  • 3.10. Preformatted text
  • 3.11. Lists
  • 3.12. Phrase elements
  • 3.13. Edits
  • 3.19. Miscellaneous elements (legend, div)
  • 4.4. Links
  • 4.7. Determining the type of a new resource in a browsing context
  • 8. The HTML syntax: * 8.1. Writing HTML documents
  • 8.2. Parsing HTML documents
Scott Vesey
Justin Thorp
  • 1. Introduction
  • 3.1. Introduction (Semantics and structure of HTML elements)
  • 3.3. Documents and document fragments
  • 3.4. Global attributes
  • 3.5. Interaction
  • 3.8. Sections
  • 3.9. Prose
  • 3.10. Preformatted text
  • 3.12. Phrase elements
  • 3.13. Edits
  • 3.14.7. The video element
  • 3.14.8. The audio element
  • 3.15. Tabular data
  • 3.16. Forms
Doug Jones
  • 3.1. Introduction (Semantics and structure of HTML elements)
  • 3.3. Documents and document fragments
  • 3.4. Global attributes
  • 3.8. Sections
  • 3.9. Prose
  • 8. The HTML syntax: * 8.1. Writing HTML documents
Ivan Enderlin
Wesley Upchurch
  • 3.1. Introduction (Semantics and structure of HTML elements)
  • 3.14. Embedded content (subsection 1-4, figure to embed)
  • 3.18. Interactive elements (inc. datagrid)
  • 3.19. Miscellaneous elements (legend, div)
Preston Bannister
Sierk Bornemann
Sam Kuper
  • 2. The Document Object Model
Samuel Santos
  • 1. Introduction
  • 3.1. Introduction (Semantics and structure of HTML elements)
  • 3.7. Document metadata
  • 3.16. Forms
  • 3.17. Scripting
Raphael Champeimont
Karl Groves I will defer answering this question until I can get a grasp on what is needed and/ or what I feel has yet to be said that I feel strongly about
aurélien levy
David Singer
  • 3.14.7. The video element
  • 3.14.8. The audio element
  • 3.14.9. Media elements
  • 3.14.10. The source element
focus on the media elements, and their usage and accessibility
David Randall
  • 3.1. Introduction (Semantics and structure of HTML elements)
  • 3.16. Forms
Bill Mason
Kelly Gifford
Sam Johnston
  • 3.12. Phrase elements
  • 3.14. Embedded content (subsection 1-4, figure to embed)
  • 3.15. Tabular data
  • 3.16. Forms
  • 3.17. Scripting
  • 3.18. Interactive elements (inc. datagrid)
  • 4.7. Determining the type of a new resource in a browsing context
Primarily interested in items relevant to web application development.
Dean Edridge
Cynthia Shelly On the July 9, 2008 Editors draft
2.5 Common DOM interfaces
3.7 Dynamic Content Insertion
4.7 Embedded Content
4.9 Forms
4.11 Interactive Elements
10 Rendering and User Agent Behavior
6. User Interaction
Dionysios Synodinos
  • 3.3. Documents and document fragments
  • 3.14. Embedded content (subsection 1-4, figure to embed)
  • 3.14.5. The object element (and o 3.14.6. The param element)
  • 3.14.7. The video element
  • 3.14.8. The audio element
  • 3.14.9. Media elements
  • 3.14.10. The source element
  • 3.14.11. The canvas element
  • 3.14.12. The map element thru 3.14.14. Image maps
  • 3.16. Forms
  • 3.17. Scripting
  • 3.18. Interactive elements (inc. datagrid)
  • 4.9. Scripting
  • 4.11. Client-side session and persistent storage of name/value pairs
Simon Pieters I review most of the spec as it's being edited, and more throughly when we implement or write tests for something.
Terry Morris
Ben Millard
Dan Connolly
  • 1. Introduction
looks like the intro has most of the references to other work, i.e. cross-WG stuff, so the chair should look it over.
Julian Reschke
  • 3.7. Document metadata
  • 3.8. Sections
  • 3.9. Prose
  • 3.10. Preformatted text
  • 3.11. Lists
  • 3.12. Phrase elements
  • 3.13. Edits
Channy Yun
Larry Masinter
  • 1. Introduction
  • 2. The Document Object Model
  • 3.1. Introduction (Semantics and structure of HTML elements)
  • 3.2. Common microsyntaxes
  • 3.3. Documents and document fragments
  • 3.4. Global attributes
  • 3.5. Interaction
  • 3.6. The root element
  • 3.7. Document metadata
  • 3.8. Sections
  • 3.9. Prose
  • 3.10. Preformatted text
  • 3.11. Lists
  • 3.12. Phrase elements
  • 3.13. Edits
  • 3.14. Embedded content (subsection 1-4, figure to embed)
  • 3.14.5. The object element (and o 3.14.6. The param element)
  • 3.14.7. The video element
  • 3.14.8. The audio element
  • 3.14.9. Media elements
  • 3.14.10. The source element
  • 3.14.11. The canvas element
  • 3.14.12. The map element thru 3.14.14. Image maps
  • 3.15. Tabular data
  • 3.16. Forms
  • 3.17. Scripting
  • 3.18. Interactive elements (inc. datagrid)
  • 3.19. Miscellaneous elements (legend, div)
  • 4. Web browsers (4.1 browsing context to 4.3 Session history)
  • 4.4. Links
  • 4.5. Interfaces for URI manipulation
  • 4.6 Navigating across documents
  • 4.7. Determining the type of a new resource in a browsing context
  • 4.8. User prompts
  • 4.9. Scripting
  • 4.10. Browser state
  • 4.11. Client-side session and persistent storage of name/value pairs
  • 4.12. Client-side database storage
  • 5. Editing
  • 6. Communication
  • 7. Repetition templates
  • 8. The HTML syntax: * 8.1. Writing HTML documents
  • 8.2. Parsing HTML documents
  • 8.3. Namespaces
  • 8.4. Entities
  • 9. WYSIWYG editors
  • 10. Rendering
  • 11. Things that you can't do with this
This survey presumes something that I think no longer holds -- that there is a single document. I'm most interested in trying to help deal with the "generic" complaints (accessibility, methodology, nature of the specification, testability etc) and how to resolve them, as those are the issues which seem to be the show-stoppers for reaching consensus.
Laura Carlson
Martin McEvoy
  • 3.4. Global attributes
  • 3.14.7. The video element
  • 3.14.8. The audio element
  • 3.14.9. Media elements
  • 8.2. Parsing HTML documents
  • 9. WYSIWYG editors
And Microdata
Ryan Mitchell
John Stewart
  • 11. Things that you can't do with this
X3D integration.
Jace Voracek I currently am unable to make an absolute commitment due to my schedule. I can review current/recent items that I feel strongly about.

View by choice

ChoiceResponders
1. Introduction
  • Lee Kowalkowski
  • Marghanita da Cruz
  • Justin Thorp
  • Samuel Santos
  • Dan Connolly
  • Larry Masinter
2. The Document Object Model
  • Lee Kowalkowski
  • John Bradley
  • Sander van Lambalgen
  • Marghanita da Cruz
  • Sam Kuper
  • Larry Masinter
3.1. Introduction (Semantics and structure of HTML elements)
  • John Bradley
  • Carol King
  • Debi Orton
  • Sander van Lambalgen
  • Ben Boyle
  • Marghanita da Cruz
  • Justin Thorp
  • Doug Jones
  • Wesley Upchurch
  • Samuel Santos
  • David Randall
  • Larry Masinter
3.2. Common microsyntaxes
  • John Bradley
  • Ben Boyle
  • Matthew Raymond
  • Geoffrey Sneddon
  • Larry Masinter
3.3. Documents and document fragments
  • John Bradley
  • Sander van Lambalgen
  • Ben Boyle
  • Geoffrey Sneddon
  • Justin Thorp
  • Doug Jones
  • Dionysios Synodinos
  • Larry Masinter
3.4. Global attributes
  • Gonzalo Rubio
  • Sander van Lambalgen
  • Ben Boyle
  • Geoffrey Sneddon
  • Justin Thorp
  • Doug Jones
  • Larry Masinter
  • Martin McEvoy
3.5. Interaction
  • Balakumar Muthu
  • Sander van Lambalgen
  • Justin Thorp
  • Larry Masinter
3.6. The root element
  • Sander van Lambalgen
  • Ben Boyle
  • Geoffrey Sneddon
  • Larry Masinter
3.7. Document metadata
  • Marco Neumann
  • Sander van Lambalgen
  • Ben Boyle
  • Matthew Raymond
  • Geoffrey Sneddon
  • Samuel Santos
  • Julian Reschke
  • Larry Masinter
3.8. Sections
  • Robert Burns
  • Ariel Pérez
  • Gonzalo Rubio
  • Sander van Lambalgen
  • Ben Boyle
  • Geoffrey Sneddon
  • Justin Thorp
  • Doug Jones
  • Julian Reschke
  • Larry Masinter
3.9. Prose
  • Robert Burns
  • Sander van Lambalgen
  • Ben Boyle
  • Geoffrey Sneddon
  • Justin Thorp
  • Doug Jones
  • Julian Reschke
  • Larry Masinter
3.10. Preformatted text
  • Sander van Lambalgen
  • Ben Boyle
  • Geoffrey Sneddon
  • Justin Thorp
  • Julian Reschke
  • Larry Masinter
3.11. Lists
  • Balakumar Muthu
  • Debi Orton
  • Sander van Lambalgen
  • Ben Boyle
  • Geoffrey Sneddon
  • Julian Reschke
  • Larry Masinter
3.12. Phrase elements
  • Sander van Lambalgen
  • Ben Boyle
  • Geoffrey Sneddon
  • Justin Thorp
  • Sam Johnston
  • Julian Reschke
  • Larry Masinter
3.13. Edits
  • Sander van Lambalgen
  • Ben Boyle
  • Geoffrey Sneddon
  • Justin Thorp
  • Julian Reschke
  • Larry Masinter
3.14. Embedded content (subsection 1-4, figure to embed)
  • Sander van Lambalgen
  • Ben Boyle
  • Marghanita da Cruz
  • Wesley Upchurch
  • Sam Johnston
  • Dionysios Synodinos
  • Larry Masinter
3.14.5. The object element (and o 3.14.6. The param element)
  • Marghanita da Cruz
  • Dionysios Synodinos
  • Larry Masinter
3.14.7. The video element
  • Benoit Piette
  • Marcin Hanclik
  • Ben Boyle
  • Matthew Raymond
  • Marghanita da Cruz
  • Justin Thorp
  • David Singer
  • Dionysios Synodinos
  • Larry Masinter
  • Martin McEvoy
3.14.8. The audio element
  • Marcin Hanclik
  • Ben Boyle
  • Marghanita da Cruz
  • Justin Thorp
  • David Singer
  • Dionysios Synodinos
  • Larry Masinter
  • Martin McEvoy
3.14.9. Media elements
  • Marcin Hanclik
  • Ben Boyle
  • Matthew Raymond
  • Marghanita da Cruz
  • David Singer
  • Dionysios Synodinos
  • Larry Masinter
  • Martin McEvoy
3.14.10. The source element
  • Ben Boyle
  • David Singer
  • Dionysios Synodinos
  • Larry Masinter
3.14.11. The canvas element
  • Sander van Lambalgen
  • Ben Boyle
  • Dionysios Synodinos
  • Larry Masinter
3.14.12. The map element thru 3.14.14. Image maps
  • Marco Neumann
  • Ben Boyle
  • Dionysios Synodinos
  • Larry Masinter
3.15. Tabular data
  • Robert Burns
  • Debi Orton
  • Ben Boyle
  • Justin Thorp
  • Sam Johnston
  • Larry Masinter
3.16. Forms
  • Balakumar Muthu
  • Debi Orton
  • Sander van Lambalgen
  • Eric Daspet
  • Ben Boyle
  • Matthew Raymond
  • Weston Ruter
  • Mikko Honkala
  • Justin Thorp
  • Samuel Santos
  • David Randall
  • Sam Johnston
  • Dionysios Synodinos
  • Larry Masinter
3.17. Scripting
  • Sander van Lambalgen
  • Ben Boyle
  • Samuel Santos
  • Sam Johnston
  • Dionysios Synodinos
  • Larry Masinter
3.18. Interactive elements (inc. datagrid)
  • Sander van Lambalgen
  • Ben Boyle
  • Matthew Raymond
  • Wesley Upchurch
  • Sam Johnston
  • Dionysios Synodinos
  • Larry Masinter
3.19. Miscellaneous elements (legend, div)
  • Debi Orton
  • Sander van Lambalgen
  • Ben Boyle
  • Geoffrey Sneddon
  • Wesley Upchurch
  • Larry Masinter
4. Web browsers (4.1 browsing context to 4.3 Session history)
  • Lee Kowalkowski
  • Marghanita da Cruz
  • Larry Masinter
4.4. Links
  • Lee Kowalkowski
  • Ben Boyle
  • Geoffrey Sneddon
  • Larry Masinter
4.5. Interfaces for URI manipulation
  • Lee Kowalkowski
  • Ben Boyle
  • Larry Masinter
4.6 Navigating across documents
  • Lee Kowalkowski
  • Larry Masinter
4.7. Determining the type of a new resource in a browsing context
  • Lee Kowalkowski
  • Ryan King
  • Mark Baker
  • Geoffrey Sneddon
  • Sam Johnston
  • Larry Masinter
4.8. User prompts
  • Lee Kowalkowski
  • Marghanita da Cruz
  • Larry Masinter
4.9. Scripting
  • Lee Kowalkowski
  • Dionysios Synodinos
  • Larry Masinter
4.10. Browser state
  • Lee Kowalkowski
  • Dimitri Glazkov
  • Larry Masinter
4.11. Client-side session and persistent storage of name/value pairs
  • Lee Kowalkowski
  • Dimitri Glazkov
  • Mikko Honkala
  • Mark Baker
  • Dionysios Synodinos
  • Larry Masinter
4.12. Client-side database storage
  • Lee Kowalkowski
  • Dimitri Glazkov
  • Mikko Honkala
  • Larry Masinter
5. Editing
  • Henrik Dvergsdal
  • Jon Barnett
  • Ben Boyle
  • Mark Baker
  • Larry Masinter
6. Communication
  • Mark Baker
  • Larry Masinter
7. Repetition templates
  • Sander van Lambalgen
  • Dimitri Glazkov
  • Matthew Raymond
  • Larry Masinter
8. The HTML syntax: * 8.1. Writing HTML documents
  • Denis Boudreau
  • Ben Boyle
  • Marghanita da Cruz
  • Geoffrey Sneddon
  • Doug Jones
  • Larry Masinter
8.2. Parsing HTML documents
  • Marco Neumann
  • Henri Sivonen
  • Ryan King
  • Geoffrey Sneddon
  • Larry Masinter
  • Martin McEvoy
8.3. Namespaces
  • Jirka Kosek
  • Henri Sivonen
  • Ben Boyle
  • Larry Masinter
8.4. Entities
  • Jirka Kosek
  • Larry Masinter
9. WYSIWYG editors
  • Robert Burns
  • Ariel Pérez
  • Balakumar Muthu
  • Ben Boyle
  • Larry Masinter
  • Martin McEvoy
10. Rendering
  • Larry Masinter
11. Things that you can't do with this
  • Ben Boyle
  • Larry Masinter
  • John Stewart

4. When do you plan to complete your detailed review of the above section(s)?

Make your best guess. Feel free to update it later.

Summary

ChoiceAll responders
Results
2007-06-15 2
2007-06-30 4
2007-07-15 3
2007-07-31 6
2007-08-15 3
2007-08-30 26

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

Details

Responder When do you plan to complete your detailed review of the above section(s)?
Chasen Le Hara
Dylan Smith
Murray Maloney
Kornel Lesinski
David Dailey
Chris Veenboer
Mihai Sucan
Asbjørn Ulsberg
Brad Fults
Roger Johansson
David Baron
John-Mark Bell
Tim McMahon
M. Jackson Wilkinson
Maciej Stachowiak
Andrew Neitsch
Bhasker V Kode
Magnus Kristiansen
Alfonso Martínez de Lizarrondo
Szymon Pilkowski
Josef Spillner
Henrik Lied
Stephen Stewart
Matthew Ratzloff
Dominik Tomaszuk
Thomas Higginbotham
David Hyatt
Nicolas Le Gall
Serdar Kiliç
John Boyer
Isac Lagerblad
Rene Saarsoo
Patrick Taylor
Jonas Sicking
Roman Kitainik
Addam Wassel
James VanDyke
Matthew Wilcox
Anne van Kesteren
Craig Saila
Darren West
Michael Turnwall
James Graham
Gregory Rosmaita
Benjamin Hedrington
Karl Dubost
Yannick Croissant
Marco Battilana
Andrew Smith
Jens Meiert
Eric Eggert
Stephen Axthelm
Account Deleted
Andrei Polushin
Chris Adams
Jirka Kosek 2007-07-31
Marco Neumann 2007-06-30
Ian Hickson
Henri Sivonen 2007-08-30
Lee Kowalkowski 2007-07-31
Robert Burns 2007-06-30
Henrik Dvergsdal 2007-06-30
Ariel Pérez 2007-07-15
David Håsäther 2007-08-30
Laurens Holst 2007-07-15
Joshue O Connor
Mark Martin
John Bradley 2007-07-31
Sean Fraser
Benoit Piette 2007-08-30
Denis Boudreau 2007-08-30
Carol King 2007-08-30
Balakumar Muthu 2007-08-30
Gonzalo Rubio 2007-08-15
Alejandro Fernandez 2007-07-15
Stéphane Deschamps
Marek Pawlowski
Masataka Yakura
Thomas Bradley 2007-07-31
Jon Barnett 2007-08-30 possibly later as spec evolves.
Debi Orton 2007-07-31
Marcin Hanclik 2007-08-15
Jason White 2007-08-30
Sander van Lambalgen 2007-08-30
Charles McCathie Nevile 2007-08-30 I don't really believe this guess :( But I will make an effort at it...
David McClure
Eric Daspet 2007-08-30
Ben Boyle 2007-08-30 (working my way through it)
Dimitri Glazkov 2007-08-30
Kai Hendry
Matthew Raymond 2007-08-30
Adam Roben
Ryan King 2007-08-30
Shawn Medero 2007-08-30
Weston Ruter 2007-08-30 I've been abroad for the past few months so have not had reliable Internet access. I am returning home now so will be more available to take on WG tasks. Probably September is more likely when I'll be able to finish reviewing.
Mikko Honkala
Mark Baker 2007-08-30
Marghanita da Cruz 2007-08-30 New Target 31st October 2007

Joseph D'Andrea
Geoffrey Sneddon 2007-08-30 <del>I'll try to get 3.1–13, as well as 3.19 and 4.4, done by mid July (as I'm off on the 19th). 4.7 after that (probably early August), then however long the parsing takes.</del>

I hope to have everything bar the parsing section done by the end of August. Parsing will be done when I have time afterwards.
Scott Vesey
Justin Thorp The end of the year.
Doug Jones 2007-06-15 2008-03-31
Ivan Enderlin
Wesley Upchurch 2007-08-30
Preston Bannister
Sierk Bornemann 2007-08-30 to be done
Sam Kuper 2007-06-30
Samuel Santos 2007-08-30 2008-02-10
Raphael Champeimont
Karl Groves All options above are in the past. ;-)
aurélien levy
David Singer 2007-08-30
David Randall
Bill Mason
Kelly Gifford
Sam Johnston
Dean Edridge
Cynthia Shelly August 15, 2008
Dionysios Synodinos 2007-10-20
Simon Pieters 2007-07-31
Terry Morris
Ben Millard
Dan Connolly 2007-08-15 I said 30 June previously, but I haven't finished a couple other tasks in time, so I'm pushing back my estimate by a couple weeks. And again. :-/
Julian Reschke 2007-08-30
Channy Yun 2007-08-30
Larry Masinter "complete" seems ambitious. I intend to do a detailed review of sections chosen at random in an attempt to get more depth to the shallow comments given so far.
Laura Carlson
Martin McEvoy
Ryan Mitchell
John Stewart 2007-06-15
Jace Voracek

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