Microformats in HTML 5
This page is to document future use of microformats in HTML 5. None of the items documented are supported now, and may change upon proper development within the microformats community, or changes in the HTML 5 specification. This page is to track HTML5 enabled enhancements to microformats, and issues that HTML5 raises. It may be used to track issues which we need to push back into the HTML 5 development process.
If there are things that Microformats would like to mark up that aren't handled by HTML5 explicitly, please let the WHATWG know, so we can improve HTML5. This is how
time came to be, for instance.
New features in HTML5
timeelement for representing date times. In HTML5, the machine form of datetimes can be represented natively. It should be possible to replace the date-time design pattern with native HTML.
data-naming convention for tag attributes. the draft specification states that any attribute that starts with "data-" will be treated as a storage area for private data.
- Note that the data-* stuff is explicitly 'not' for Microformats, at least not Microformats that ever want to be handled natively by the browser. Those attributes are defined in such a way that browsers will never do anything special with them, ever. They are intended for script authors to have a space in which they can play without ever clashing with anything the browser does.
revattribute has been removed. In HTML5,
revare no-longer paired, and the
relattribute nolonger describes the direction of a relationship. Microformats which use
revwill need to use
- Or something like data-rev="vote-for".
profileattribute has been removed. In HTML, the
profileattribute from the
headhas been removed, with no direct replacement. This causes issues for GRDDL support. It's been suggested that profile URLs be represented in
linkelements instead, or even as a custom HTTP header.