Microformats in HTML 5

(Difference between revisions)

Jump to: navigation, search
(Issues: adding HTML5 validation issue with colon-less timezones (as recommended on value-class-pattern page))
(microdata: updated attribute definitions and uses, changed microdata vocabulary links to working versions, removed out-of-date warnings about using microdata vocabularies)
Line 18: Line 18:
* <code>itemprop</code> attribute is a more specific version of <code>class</code>, for field names
* <code>itemprop</code> attribute is a more specific version of <code>class</code>, for field names
* <del><code>subject</code> attribute allows semantically linking within the page. Conceptually similar to the [[include-pattern]].</del>
* <del><code>subject</code> attribute allows semantically linking within the page. Conceptually similar to the [[include-pattern]].</del>
-
* <code>&lt;itemref refid="x" /&gt;</code> allows semantically linking within the page. Conceptually similar to the [[include-pattern]].
+
* <code>&lt;itemref="" /&gt;</code> allows including properties elsewhere on the page that are not descendants of <code>itemscope</code>. Takes space-separated ids. Conceptually similar to the [[include-pattern]].
-
* <code>content</code> attribute on the <code>meta</code> element can be used to invisibly include data. Conceptually similar to the [[value-class-pattern]].  
+
* <code>content</code> attribute on the <code>meta</code> element can be used to include data that is not part of the content. As current browsers move <code>meta</code> inside <code>&lt;head&gt;</code>, make sure to include via <code>itemref</code>. Conceptually similar to the [[value-class-pattern]].
-
* <code>itemscope</code> attribute identifies blocks to be marked as structure data. Conceptually similar to the [[mfo]] brainstorming?
+
* <code>itemscope</code> attribute identifies blocks to be marked as structured data. Conceptually similar to the [[mfo]] brainstorming?
* <code>itemtype</code> attribute to specify the type for an item (for example: <code><nowiki>itemtype="http://microformats.org/profile/hcard"</nowiki></code>)
* <code>itemtype</code> attribute to specify the type for an item (for example: <code><nowiki>itemtype="http://microformats.org/profile/hcard"</nowiki></code>)
==== microdata vocabularies ====
==== microdata vocabularies ====
-
* [http://dev.w3.org/html5/mdvcard/ 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.
+
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#vcard microdata vCard] - this is based directly on vCard. Alternatively use Google’s Rich Snippets vocabularies ([http://www.data-vocabulary.org/Person/ Person] and [http://www.data-vocabulary.org/Organization/ Organization]), which are simplified versions also based on vCard
-
* [http://dev.w3.org/html5/mdvevent/ microdata 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.
+
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#vevent microdata vEvent] - this is based directly on iCalendar. Alternatively use Google’s Rich Snippets vocabulary ([http://www.data-vocabulary.org/Event/ Event]), which is a simplified version also based on iCalendar
-
* [http://dev.w3.org/html5/mdwork/ microdata Licensing Works] - see also [[licensing-brainstorming]]
+
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#licensing-works microdata Licensing Works] - see also [[licensing-brainstorming]]
=== data attributes ===
=== data attributes ===

Revision as of 14:48, 12 July 2010


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.

Contents

New features in HTML5

time element

time element 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.

article element

article element for major, independent compositions of content within a page. Perhaps synonymous with hAtom hentry. Could be parsed as hentry within explicit hfeed blocks?

microdata

microdata. HTML5 provides a set of attributes and associated DOM APIs for extracting data from web pages.

microdata vocabularies

data attributes

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.

Current microformat compatibility

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

Requests

Issues

  • 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
    • See rel-profile which is the replacement for the profile attribute. Tantek 23:24, 5 November 2009 (UTC)
  • 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)
  • 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)

see also

Microformats in HTML 5 was last modified: Wednesday, December 31st, 1969

Views