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:
Please say a few words about any relevant background experience that you bring to the HTML WG.
|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.|
|Chris Veenboer||Software/web development.|
A good knowledge of Voice Interactivity technologies, like VoiceXML, Speech Grammar, Semantic Interpretation, and related.
Recent experience with SVG development.
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.|
|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 . |
|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.|
|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.|
|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.|
|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.|
|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|
|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).|
|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.|
|Thomas Bradley||Several years education and experience in front-end and back-end development and design.|
|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.|
|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
Presentations on Video Editing and Publishing content on the Web using Ogg Theora/Vorbis
Open Source Video Editing and Publication Sydney, 27th July 2006
Capture and Editing in Linux using Kino, Sydney 31 August 2007
|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.|
|Wesley Upchurch||7 years of web design and development experience.|
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.|
|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.|
|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.|
|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
* 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:|
* Moderator and active participant at Accessify Forum:
* 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):
* 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.|
|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:|
|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.|
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.
|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|
|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|
|translation to languages other than English||7|
|serve as scribe for teleconferences||3|
Skip to view by choice.
|Responder||What tasks are you here to help with?||Comments|
|Chasen Le Hara||
||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.
||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.|
||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.
||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.
||(when time allows)|
I review any section of the spec, and provide my suggestions.
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.
||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.
||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.
|M. Jackson Wilkinson||
||willing to lead insofar as educational materials are concerned|
||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
|Bhasker V Kode||
||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.|
||No particular reservations on test case types (yet).|
|Alfonso Martínez de Lizarrondo||
||Now I'm colaborating in the development of FCKeditor, so I can try to help adding there new features or fix existing problems.|
||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.
||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).|
||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.
|Nicolas Le Gall||
||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).|
||I have done some previous work on analyzing/validating the markup on a number of pages . Also some periodic surveys on Estonian websites .|
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.
||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
||Drafting for and reviewing the full HTML spec.|
Tests for the 4 major browsers though mostly for firefox.
Browser maintenance and development for firefox.
||It would be rewarding to see the skills and expertise I was lucky to accumulate put to good use. Any kind of good use.|
||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||
||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.|
||Re: review, I can tackle any section that's needed. |
Re: testing results in IE6, IE7, WebKit, Gecko, Opera 9 and TextMate authoring tool.
||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.|
||I'm open to any section. Just let me know what is expected.|
||Test cases for parsing in particular|
||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|
||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.|
||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.|
||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
||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.|
||A conformance checking service and a schema are already well under way:|
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.
||Sections to review are detailed in answer to next question.|
||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.|
||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|
||I've done some test cases, and I expect to do more.|
||Review of sections related to my experience and interests.|
|Joshue O Connor||
||We have a full user testing facility in our head office where we can video users (using Morae) and conduct extensive user tests.|
||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.|
||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.|
||If can do the translation of the documents to spanish.|
||I'd like to contribute translations to French with an educational approach.|
||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.
||I could do some translation work (Japanese)|
||Concentration on semantics, structure and accessibility.|
||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|
||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
|Sander van Lambalgen||
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||
- 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.
||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
||- translation of the wg publications in french|
||Particular interest in forms. Also in the new document semantics (sections, articles, etc) and newly specificied behaviour of elements (e.g. DFN).|
||Testing mobile UAs|
||Happy to provide testing on Safari/WebKit|
||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.|
||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.|
||My PhD thesis at should be relevant info:|
||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||
||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.|
||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).
||exploring release of internal test framework to public domain.|
||I'm particulary interesting by making turorial development and helping people to learn.|
||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.|
||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.
||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.
||accessibility features of html|
||Primarily interested in items relevant to web application development.|
||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.
||* Research into accessible table markup:|
* Newest round of research, with broader scope:
* 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.
||I'm particularly interested in testing the tree construction stuff in a validator-like online service.|
||TEXT ALTERNATIVES ISSUE (@alt):|
- Working on ISSUE 31 with SteveF, Joshue O Connor and others
- Created Wiki page on the "Omitting Text Alternatives for Critical Content" issue.
- Requested PFWG WAI to review Omitting alt Attribute for Critical Content and provide advice on the potential accessibility impact.
- 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.
- Created Wiki page "Action 54: First Draft"
- Created Discussion Page for "Action 54: First Draft"
- Created Wiki page "Action 54: Second Draft"
- Created Wiki page "Action 54: Third Draft"
- Participated in WAI CG Task Force which produced Consensus Resolutions on Text alternatives in HTML 5
- Worked with SteveF Cynthia Shelly, Matt May and others on ACTION 131 to draft ALT spec
- Action 131 Deliverable
- Working on ISSUE-32 with SteveF, Joshue O Connor and others on table summary
- Worked on "Mechanism to Summarize a Table" Wiki page
- Worked on ACTION-66 with SteveF, Joshue O Connor and others to collate information
- Worked on ACTION-111 to move issue 32 toward resolution by asking PFWG for comments on several items:
- Working on ISSUE-74 Canvas accessibility
- Created Wiki page "New canvas Element Accessibility Issues"
MULTIMEDIA <Audio> <Video>
- Created Wiki page "Multimedia Accessibility (<Audio> <Video>)"
- Requested PFWG WAI to review multimedia accessibility requirements <audio> <video>
- Collaborated with other working group members to author:
"Request to Strengthen the HTML5 Accessibility Design Principle"
- Helped with Design Principles Wiki page. e.g. helped identify and document disputed principles.
ACCESSIBILITY ISSUES PROCEDURE
- Collaborated with other working group members to author:
"Procedure to Promote Progress With Accessibility Issues in HTML5" Proposal
- Created Discussion Page for Accessibility Issues Procedure:
- Requested PFWG WAI to review headers/id attribute and provide advice on the on the potential accessibility impact.
- Created Wiki page "headers attribute Issue"
- Worked on ISSUES-57/20 with SteveF, Joshue O Connor and others on @headers
- Worked on ACTION-72 with SteveF, Joshue O Connor and others to draft text for the HTML 5 spec
- Created Wiki page "ACTION 72: @headers rewrite" deliverable:
- Created Wiki page "headers/id Testing (Bug 5822)"
- Created Wiki page "Cyclic Header Chains"
- FURTHER WG WORK
- Helped with HTML Working Group Issue and Action Definitions
- Created Wiki page "HTML WG Meeting Minutes"
- Created Wiki page "HTML WG Surveys"
- Created Wiki page "HTML WG Email Lists"
- Created Wiki page "HTML WG Teleconferences"
- Created Wiki page "HTMLWG Requests and PFWG Responses"
- Participating in PFWG Caucus on HTML5 Issues
- Started justification Wiki pages for dropped/added/changed elements and attributes.
||X3D integration related tasks.|
||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.
|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, ...)||
|a periodic survey of top web sites||
|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||
|prototyping new features using scripting||
|validation/checking service development||
|validation/checking service operations||
|issue tracking, summarization, and clustering||
|security review, risk analysis||
|translation to languages other than English||
|serve as scribe for teleconferences||
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.
|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.6. The root element||4|
|3.7. Document metadata||8|
|3.10. Preformatted text||6|
|3.12. Phrase elements||7|
|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.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.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.10. Browser state||3|
|4.11. Client-side session and persistent storage of name/value pairs||6|
|4.12. Client-side database storage||4|
|7. Repetition templates||4|
|8. The HTML syntax: * 8.1. Writing HTML documents||6|
|8.2. Parsing HTML documents||6|
|9. WYSIWYG editors||6|
|11. Things that you can't do with this||3|
Skip to view by choice.
|Responder||Which section(s) are you planning to review in detail in the coming weeks?||Comments|
|Chasen Le Hara|
|M. Jackson Wilkinson|
|Bhasker V Kode|
|Alfonso Martínez de Lizarrondo|
|Nicolas Le Gall|
|Anne van Kesteren|
||I might review other sections if I have the time.|
|David Håsäther||This will depend on the amount of time I can commit.|
|Joshue O Connor||I am particularly interested in HTML 5 and accessibility/usability.|
|Marek Pawlowski||I'm not sure I'd have time for detailed review but I'll try do some brief review.|
||If the spec details the DOM of designMode, I'll happily review it.|
|Sander van Lambalgen||
||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|
||May review limited portions of sections not checked above.|
|Marghanita da Cruz||
|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|
||focus on the media elements, and their usage and accessibility|
||Primarily interested in items relevant to web application development.|
|Cynthia Shelly||On the July 9, 2008 Editors draft|
2.5 Common DOM interfaces
3.7 Dynamic Content Insertion
4.7 Embedded Content
4.11 Interactive Elements
10 Rendering and User Agent Behavior
6. User Interaction
|Simon Pieters||I review most of the spec as it's being edited, and more throughly when we implement or write tests for something.|
||looks like the intro has most of the references to other work, i.e. cross-WG stuff, so the chair should look it over.|
||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.|
|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.|
|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.6. The root element||
|3.7. Document metadata||
|3.10. Preformatted text||
|3.12. Phrase 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||
|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.18. Interactive elements (inc. datagrid)||
|3.19. Miscellaneous elements (legend, div)||
|4. Web browsers (4.1 browsing context to 4.3 Session history)||
|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.10. Browser state||
|4.11. Client-side session and persistent storage of name/value pairs||
|4.12. Client-side database storage||
|7. Repetition templates||
|8. The HTML syntax: * 8.1. Writing HTML documents||
|8.2. Parsing HTML documents||
|9. WYSIWYG editors||
|11. Things that you can't do with this||
Make your best guess. Feel free to update it later.
(88 responses didn't contain an answer to this question)
|Responder||When do you plan to complete your detailed review of the above section(s)?|
|Chasen Le Hara|
|M. Jackson Wilkinson|
|Bhasker V Kode|
|Alfonso Martínez de Lizarrondo|
|Nicolas Le Gall|
|Anne van Kesteren|
|Joshue O Connor|
|Jon Barnett||2007-08-30||possibly later as spec evolves.|
|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...|
|Ben Boyle||2007-08-30||(working my way through it)|
|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.|
|Marghanita da Cruz||2007-08-30||New Target 31st October 2007|
|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.
|Justin Thorp||The end of the year.|
|Sierk Bornemann||2007-08-30||to be done|
|Karl Groves||All options above are in the past. ;-)|
|Cynthia Shelly||August 15, 2008|
|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. :-/|
|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.|
The following persons have not answered the questionnaire:
Send an email to all the non-responders.