Looking to learn more about HTML5?

Check out my video+booklet:

HTML5 Now: A Step-by-Step Video Tutorial for Getting Started Today.

Last year (2009-203) I joined the W3C HTML Working Group as a public invited expert and am reviewing various HTML5 materials so that I may provide constructive feedback to improve the state of HTML5

Feedback

in general

• http://www.zeldman.com/superfriends/ specifically: 
• http://www.zeldman.com/superfriends/guide/

time element

• http://wiki.whatwg.org/wiki/Time_Element

cite element

• http://wiki.whatwg.org/wiki/Cite_element

Reviewing

• http://www.whatwg.org/specs/web-apps/current-work/multipage/
• http://dev.w3.org/html5/html4-differences/
• http://wiki.whatwg.org/wiki/FAQ
• http://www.w3.org/People/Bos/DesignGuide/introduction.html
• http://adactio.com/journal/1600/
• Microsoft joins HTML 5 standard fray in earnest - CNET
• public-html: Feedback on the current editor's draft by Adrian Bateman <adrianba@microsoft.com>
• http://coffeeonthekeyboard.com/reservations-about-html5-271/
• Regarding methodology, conflict resolution, research, burdens of proof:
• anecdotal expertise vs. research data: http://lists.w3.org/Archives/Public/public-html/2009Aug/0111.html
• how do you proceed when anecdotal experts disagree?
• e.g. WAI WCAG2 vs. government documents vs. Joe Clark WCAG Samurai ("To Hell With WCAG2" article, fork of WCAG1 to do WCAG1 errata as alternative to WCAG2)
• http://www.access-board.gov/sec508/guide/1194.22.htm#(g) (Last paragraph of section h.) raised as an example of conflicting expert advice in an email from Ian Hickson.
• "Requiring consensus is only a viable when the parties to be involved in the consensus all have interests in the success of the standard." -David Baron
• Controversial issues
• http://wiki.whatwg.org/wiki/Table_Summary
• lots of email traffic generated in 2009-08
• Intranets not being a good source for design influence

Suggestions

These are suggested changes to the HTML5 draft, and very much in progress.

• Reference rather than fork predefined microdata vocabularies
• instead of "vcard" microdata vocabulary, reference hCard 1.0.1 if necessary to note this functionality in HTML5
• needs hCard 1.0.1 draft with sufficient author and user agent compliance details
• needs hCard 1.0.1 section on HTML5 and how to use HTML5 specific features if desired like <time> element, microdata, instead of (or in addition to) HTML class names.
• progress: the vcard microdata vocab references the hCard profile URL.
• instead of "vevent" microdata vocabulary, reference hCalendar 1.0.1 if necessary
• needs hCalendar 1.0.1 draft with sufficient author and user agent compliance details
• needs hCalendar 1.0.1 section on HTML5 and how to use HTML5 specific features if desired like <time> element, microdata, instead of (or in addition to) HTML class names.
• progress: the vevent microdata vocab references the hCalendar profile URL.
• instead of licensing "work" microdata vocabulary, reference licensing microformat if necessary
• requires writing draft of licensing microformat (from licensing brainstorming) including "item-license", with sufficient author and user agent compliance details, and how to use HTML5 specific features if desired like <time> element, microdata, instead of (or in addition to) HTML class names.
• rel values that should normatively reference microformats instead of incorporating/describing them:
• replace HTML5 description of "license", with a normative reference to the rel-license microformat
• replace the *incorrect* (refers to whole document) HTML5 description of "tag", with a normative reference to the rel-tag microformat
• other rel values. per HTML5 Other link types, add well established rel microformats to the WHATWG wiki RelExtensions page.
• Note: XFN is already on that WHATWG wiki page, and all XFN values are "Accepted." Re-iterate good feedback on this point.

Resolved

Progress. These are suggested changes to the HTML5 draft that have shown at least some improvement (specifics documented below). Any outstanding issues with the suggested changes are kept in the Suggestions section above.

* As of 2009-11 (apparently resolved sometime in late September or October)

• Remove predefined microdata vocabularies.  Originally requested 2009-08.  The predefined microdata vocabularies for "vcard", "vevent" and licensing have been removed from the core HTML5 specification, and moved to a separate set of drafts. This is an improvement in HTML5.

Return to ProjectsList \ FrontPage