(Difference between revisions)

Jump to: navigation, search
(added some microdata vocabularies)
(Current microformat compatibility: noted microdata vocabulary flaws and which microformats to use instead, noted see also license-brainstorming)
Line 27: Line 27:
Microdata vocabularies:
Microdata vocabularies:
* [ vCard]
* [ microdata vCard] - use [[hCard]] instead, taking into account the [[hcard-faq|hCard FAQ]] and [[hcard-issues-resolved|resolved]]+[[hcard-issues-closed|closed issues]]. hCard 1.0.1 (under development) is incorporating these errata. Avoid the "microdata vCard" vocabulary as it is an out-of-date fork/snapshot of hCard.
* [ vEvent]
* [ vEvent] - use [[hCalendar]] instead, taking into account the [[hcalendar-faq|hCalendar FAQ]] and [[hcalendar-issues-resolved|resolved]]+[[hcalendar-issues-closed|closed issues]].  hCalendar 1.0.1 is incorporating these errata. Avoid the "microdata vEvent" vocabulary, as it is an out-of-date fork/snapshot of hCalendar's vevent root class name and applicable properties.
* [ Licensing Works]
* [ Licensing Works] - see also [[licensing-brainstorming]]
== Requests ==
== Requests ==

Revision as of 00:54, 14 October 2009


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

Current microformat compatibility

There seems to be no issue with current implementation of the following microformats in HTML 5:

Microdata vocabularies:



  • The rev attribute has been removed. In HTML5, rel and rev are no-longer paired, and the rel attribute nolonger describes the direction of a relationship. Microformats which use rev will need to use rel instead.
    • Or something like data-rev="vote-for"
      • As above, data- attributes are for application-context functionality, not shared vocabularies. Further, the HTML5 specification makes rel the correct attribute to use, regardless of direction, through the changed specification. --BenWard 17:53, 12 May 2009 (UTC)
  • The profile attribute has been removed. In HTML, the profile attribute from the head has been removed, with no direct replacement. This causes issues for GRDDL support. It's been suggested that profile URLs be represented in link elements instead, or even as a custom HTTP header. See grddl and profile-uris
  • Microdata itemprop duplicates class data. 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)

see also

html5 was last modified: Wednesday, December 31st, 1969