W3C WBS Home

Results of Questionnaire HTML WG tasks

The results of this questionnaire are available to anybody.

This questionnaire is open from 2007-04-24 to 2008-12-31.

123 answers have been received.

Jump to results for question:

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?
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/
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.
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.
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.
Ryan King
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.
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."
Simon Pieters I am participating in the WHATWG since 2005. I have some experience with writing test cases<http://simon.html5.org/test/> and submitting bug reports to various browser vendors.
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
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.
Henrik Dvergsdal MSc Computer Science, teaching experience, developer experience. Speciality: universally accessible web applications.
Chris Veenboer Software/web development.
Alejandro Fernandez Web designer and developer for 5 years.
Interested in standards developing and usability.
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.
David McClure MS Computer Science, developer experience
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.
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.
Roger Johansson Several years' experience from writing tutorials and articles related to Web standards and best practices in Web development.
James Graham Participant in WHATWG mailing list since 2004. (Co)developer of a few HTML-related tools including html5lib parser.
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.
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).
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.
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.
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)
Darren West 3 years web development experience using web standards, and 10 years other IT experience.
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
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.
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.
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.
Ian Hickson
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.
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.
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.
Mikko Honkala Prototype browser implementation (XHTML, CSS, SVG, XForms), XForms standardization
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.
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.
Chris Adams I am currently a student studying web development with a strong focus on usability and accessibility.
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.
Craig Saila Web standards advocate for nearly 6 years, contributor to CSS 2.1
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
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.
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/
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.
Eric Eggert Student of media informatics. Web design since 2002 with a focus on document structure and semantics.
Bill Mason Eight years mostly in front-end web development: (X)HTML, CSS, Javascript, 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).
Ben Millard * Professional frontend developer (HTML, CSS, accessibility). <http://sdesign1.com/ben.htm>
* Provides standards- and browser-compliant solutions to markup problems raised on Accessify Forum. <http://www.accessifyforum.com/profile.php?mode=viewprofile&u=2202>
* Reads about accessibility, usability, standards and browser conformance.
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.
Thomas Bradley Several years education and experience in front-end and back-end development and design.
Marco Neumann XML, OWL, RDF, Spatial Data
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.
Eric Daspet Expertise from the authoring point of view (xml, sgml, html, accessibility)
Experience in writing and reviewing spec
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.
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
Ben Boyle Web developer (10 years); interested in seeing HTML5 provide richer semantics.
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.
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.
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.
Raphael Champeimont I have written HTML documents for 5 years...
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
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
Jon Barnett intimate familiarity with HTML, XML, CSS, Javascript, DOM, XSLT, XPath, and PHP.
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
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.
Charles McCathieNevile 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.
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
Adam Roben Have worked on Safari/WebKit since July 2006. Sporadic web development experience since 1998.
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.
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>
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..
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
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.
Dean Edridge I'm an experienced Web Developer with skills in HTML and XHTML and CSS. I am involved with the Usability Professionals Association (UPA) in Auckland New Zealand and am always looking for new ways to make the web more usable for everyone.
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.
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.
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.
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.
Kelly Gifford Professional Web Developer/Software Engineer since 2001 (experienced in both front and back-end technologies). Started coding HTML way back in 1995.

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?) 23
detailed review of substantial sections of spec (which features/sections?) 43
test case development (which kind?) 29
manual test result (which browser? authoring tools?) 27
test suite organization/editing 11
tutorial development, quick reference, course materials, ... 56
formalization (schemas, formal rules, ...) 11
a periodic survey of top web sites 24
usability testing 38
design principles, goals requirements (drafting, review, liaison) 31
orientation: documenting group norms, helping people learn them 14
web browser maintenance (esp. fixing bugs around spec compliance) 13
web browser enhancements 13
authoring tool development 14
prototyping new features using scripting 19
validation/checking service development 15
validation/checking service operations 9
issue tracking, summarization, and clustering 21
security review, risk analysis 8
forms taskforce 15
translation to languages other than English 5

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

Skip to view by choice.

View by responder

Details

Responder What tasks are you here to help with?Comments
Dan Connolly
  • test case development (which kind?)
  • formalization (schemas, formal rules, ...)
  • validation/checking service development
  • issue tracking, summarization, and clustering
I'm particularly interested in testing the tree construction stuff in a validator-like online service.
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.
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.
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.
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
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
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.
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
  • tutorial development, quick reference, course materials, ...
I will be working on a test suite for HTML5 for Opera this summer (week 25..31), probably focussing on already implemented features that currently lack tests. Reviewing the parts of the spec that I write tests against and running the tests that I write in various browsers goes without saying. Since I will be writing many test cases I will have to organize them somehow and so I could well help with organization of other tests too. I'm currently maintaining http://simon.html5.org/html5-elements. I might be interested in contributing to tutorial development.
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.
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.
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.
Chris Veenboer
  • web browser maintenance (esp. fixing bugs around spec compliance)
  • prototyping new features using scripting
Alejandro Fernandez
  • usability testing
  • translation to languages other than English
If can do the translation of the documents to spanish.
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.
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




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)
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).
Roger Johansson
  • tutorial development, quick reference, course materials, ...
James Graham
  • test case development (which kind?)
  • validation/checking service development
  • issue tracking, summarization, and clustering
Test cases for parsing in particular
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
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.
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.
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.
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.
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.
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


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
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).
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.
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.
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
Terry Morris
  • tutorial development, quick reference, course materials, ...
  • a periodic survey of top web sites
  • design principles, goals requirements (drafting, review, liaison)
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
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/
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
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
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
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.
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.
Laura Carlson
  • drafting spec text (which features/sections?)
  • issue tracking, summarization, and clustering
Created Wiki page on the "Omitting alt Attribute 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

PFWG official response on alt:
"...the failure of the HTML5 draft to make
@alt on <img> an across-the-board requirement (even if sometimes
it has the value of &quot;&quot;) is a bug....HTML WG should re-work the <img> element section to bring it into line as techniques for implementing WCAG 2.0."
http://lists.w3.org/Archives/Public/public-html/2008Feb/0082.html

Issue-31 missing-alt
"...conformance requirements here should be dictated by WCAG."
http://www.w3.org/html/wg/tracker/issues/31

Action 54 working with Steve Faulkner and Joshue O Connor and others to draft text for HTML 5 spec to require producers/authors to include @alt on img elements. (Section 3.14.2 the img element)
http://www.w3.org/html/wg/tracker/actions/54

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

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

PFWG official response:
"...from an accessibility perspective, dropping 'headers' because
'scope' could afford the same semantics in 'most of the cases' is a
wrong decision; now or, taken in isolation, for the future. But
'scope vs. headers' is not the right frame of reference for the
future. As the requirement isn't limited to tables, we look forward
to a better solution, gracefully migrated to, once the requirements
get looked at in the right breadth of view..."
http://lists.w3.org/Archives/Public/public-html/2007Jun/0145.html
Related ISSUE-20 table-headers
http://www.w3.org/html/wg/tracker/issues/20

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

Started justification wiki pages for dropped/added/changed elements and attributes.
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.
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
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.
Eric Eggert
  • a periodic survey of top web sites
  • design principles, goals requirements (drafting, review, liaison)
Bill Mason
Jirka Kosek
  • formalization (schemas, formal rules, ...)
  • validation/checking service development
Ben Millard
  • drafting spec text (which features/sections?)
  • test case development (which kind?)
  • manual test result (which browser? authoring tools?)
  • a periodic survey of top web sites
  • issue tracking, summarization, and clustering
More detail:
* Ongoing research into accessible table markup: <http://sitesurgeon.co.uk/!dev/tables/>
* Some ability to summarise differing views on controversial issues.

Additional:
* Perspective on how UK commercial and public sector websites are built in practice at all scales.
* Trends and changes in the web industry.
* Tidying markup examples in discussions.
* Accessibility impact of proposals.
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
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.
Marco Neumann
  • prototyping new features using scripting
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.
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
Robert Burns
  • detailed review of substantial sections of spec (which features/sections?)
  • web browser enhancements
  • authoring tool development
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
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).
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
Gonzalo Rubio
  • drafting spec text (which features/sections?)
  • translation to languages other than English
John Bradley
  • tutorial development, quick reference, course materials, ...
  • usability testing
  • security review, risk analysis
Raphael Champeimont
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
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)
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
Julian Reschke
  • formalization (schemas, formal rules, ...)
  • design principles, goals requirements (drafting, review, liaison)
  • issue tracking, summarization, and clustering
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.
Charles McCathieNevile
  • 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.
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
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
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.
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>
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, ...
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.
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
Dean Edridge
  • tutorial development, quick reference, course materials, ...
  • 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)
  • authoring tool development
  • validation/checking service development
  • validation/checking service operations
  • issue tracking, summarization, and clustering
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
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.
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, ...)
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
Kelly Gifford
  • tutorial development, quick reference, course materials, ...
  • usability testing
  • orientation: documenting group norms, helping people learn them

View by choice

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

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

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

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
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.
Chasen Le Hara
Jonas Sicking
Dylan Smith
Murray Maloney
Kornel Lesinski
Ryan King
  • 4.7. Determining the type of a new resource in a browsing context
  • 8.2. Parsing HTML documents
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)
David Dailey
Simon Pieters
  • 2. The Document Object Model
I will review the sections that are implemented somewhere and don't have test cases yet. I'll start with the DOM.
Anne van Kesteren
Henri Sivonen
  • 8.2. Parsing HTML documents
  • 8.3. Namespaces
Henrik Dvergsdal
  • 5. Editing
Chris Veenboer
Alejandro Fernandez
Mihai Sucan
David McClure
Asbjørn Ulsberg
Brad Fults
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
Roger Johansson
James Graham
David Baron
David Håsäther This will depend on the amount of time I can commit.
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.
Laurens Holst
John-Mark Bell
Darren West
Tim McMahon
M. Jackson Wilkinson
Maciej Stachowiak
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.
Andrew Neitsch
Bhasker V Kode
Magnus Kristiansen
Sean Fraser
Ian Hickson
Alfonso Martínez de Lizarrondo
Szymon Pilkowski
Josef Spillner
Henrik Lied
Terry Morris
Stephen Stewart
Matthew Ratzloff
Dominik Tomaszuk
Mikko Honkala
  • 3.16. Forms
  • 4.11. Client-side session and persistent storage of name/value pairs
  • 4.12. Client-side database storage
Gregory Rosmaita
Thomas Higginbotham
David Hyatt
Nicolas LE GALL
Serdar Kiliç
John Boyer
Isac Lagerblad
Rene Saarsoo
Patrick Taylor
Chris Adams
Roman Kitainik