Microformats in HTML5
This page is to document future use of microformats in HTML5. 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 the
time element came to be, for instance.
New features in HTML5
time element for representing date times. In HTML5, the machine form of datetimes can be represented natively. In some cases it may be possible to replace the date-time design pattern with native HTML5.
- Recommendation: Use the Value Class Pattern, in particular preferably date-time-separation for accessibly marking up dates and times while following the DRY principles as much as possible.
- HTML::Microformats and its predecessors have supported the
timeelement since July 2008.
- Try http://dev.h2vx.com/ (the beta version of H2VX) as it now has preliminary support for
<time datetime>as well as the new semantic HTML5 elements.
Note: that there are documented proposals to extend the time element. Please add additional opinions and use cases to that wiki page so that we can help improve the time element.
There was briefly an optional
pubdate attribute, to indicate the publication date of an
article, but it was dropped in 2012 since it is both unnecessary and insufficient. Rather than use the one-off pubdate attribute, it's much better to:
- Use the hAtom 0.1 microformat for articles, and the hAtom
publishedproperty, as well as the hAtom
hCalendar with time element
Here is the hCalendar spec example updated to use section instead of div, and time instead of abbr.
<section class="vevent"> <a class="url" href="http://conferences.oreillynet.com/pub/w/40/program.html"> http://conferences.oreillynet.com/pub/w/40/program.html </a> <span class="summary">Web 2.0 Conference</span>: <time class="dtstart" datetime="2005-10-05">October 5</time>- <time class="dtend" datetime="2005-10-07">7</time>, at the <span class="location">Argent Hotel, San Francisco, CA</span> </section>
article element for major, independent compositions of content within a page. Perhaps synonymous with hAtom 0.1
hentry. Could be parsed as
hentry within explicit
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. 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. There may be some cases of private poshformats that are never intended for interchange that may be used in data-* attributes.
Since data-* attributes are not for general data interchange or generic APIs supported by multiple sites / pieces of software, what are actual valid uses of data-* attributes? One example (feel free to add more)
data-related="indiewebcamp"- indicates @indiewebcamp is a related Twitter account for a tweet button.
new semantic elements
HTML5 has numerous new semantic elements.
Most microformats Microformats Parsers probably won't recognize those elements and may ignore them - so avoid using microformats classes on new HTML5 semantic elements for anything in production.
HOWEVER, do try experimenting with microformats and new semantic HTML5,
Changes in HTML5
The rel/rev attributes
rev attribute has been removed from HTML5. The
rel attribute can be still be used in the same way, but microformats that assumed the existence of
rev and thus only defined a single forward-facing relation may need to be changed to include an opposite relation as well. That is, for every relation that goes in one direction (e.g. rel-parent of XFN - The XHTML Friends Network), you must explicitly name and define the inverse relationship (e.g. rel-child of XFN - The XHTML Friends Network) if the inverse relation is indeed useful.
Additions beyond HTML5
microdata is an extension to HTML5 that provides a set of attributes and associated DOM APIs for semantically marking up and extracting data from existing content in web pages, similar to microformats but with new attributes.
Current microformat compatibility
There seems to be no issue with current implementation of the following microformats in HTML 5:
- "how to use with HTML5" sections that include (a) microformats examples that use Microformats in HTML5, and (b) microformats parsing details that specify what to do (if anything special is required) with HTML5 elements (e.g. how to parse the
timeelement for dates and times for microformats). See (and add to if necessary) :
- hCard brainstorming - how to use with HTML5
- hCalendar brainstorming - how to use with HTML5 e.g. hCalendar with the
- citation brainstorming - how to use with HTML5
- if nothing special is required for HTML5, then after performing the analysis, that should be noted as well, for the purpose of clarity.
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. See grddl and profile-uris
classdata. the new attribute itemprop is designed to hold some meaningful data about an element, but class already exists to hold this data. Unsure of reasons why itemprop required?
- This is because microdata is designed to be generically parsable, even when the parser does not understand the vocabulary. As such, property names have to be on an explicit attribute, not shared with other, non-data classnames. --BenWard 21:12, 4 September 2009 (UTC)
- The recommended removal of the colon in timezone doesn’t validate The relevant uF wiki text is “However the colons ":" separating the hours and minutes of any timezone offset are optional and discouraged in order to make it less likely that a timezone offset will be confused for a time.” ref: HTML5 time microsyntax for <time> --Oli 14:40, 14 February 2010 (+9)
- Some websites are not ready to upgrade to HTML5 and must stick with HTML4 (or XHTML1 served/interpreted as HTML4) for now. For example: