Difference between revisions of "html5"

From Microformats Wiki
html5
Jump to navigation Jump to search
(Added list notes about the microdata stuff.)
(→‎Requests: updated to reference specific brainstorm pages on respective microformats)
Line 22: Line 22:
  
 
== Requests ==
 
== Requests ==
* microformats examples that use HTML5, e.g.
+
* "how to use with HTML5" sections that include (a) microformats examples that use [[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 <code>time</code> element for dates and times for microformats). See (and add to if necessary) :
** hCalendar with the <code>time</code> element
+
** [[hcard-brainstorming#how_to_use_with_HTML5|hCard brainstorming - how to use with HTML5]]
* microformats parsing details that specify what to do (if anything special is required) with HTML5 elements
+
** [[hcalendar-brainstorming#how_to_use_with_HTML5|hCalendar brainstorming - how to use with HTML5]] e.g. hCalendar with the <code>time</code> element
** how to parse the <code>time</code> element for dates and times for microformats
+
** [[citation-brainstorming#how_to_use_with_HTML5|citation brainstorming - how to use with HTML5]]
** if nothing special is required, then after performing the analysis, that should be noted as well, for the purpose of clarity.
+
** if nothing special is required for HTML5, then after performing the analysis, that should be noted as well, for the purpose of clarity.
  
 
==Issues==
 
==Issues==

Revision as of 21:25, 29 June 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

  • 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.
  • 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.
  • Microdata. HTML5 provides a set of attributes and associated DOM APIs for extracting data from web pages.
    • itemprop attribute is a more specific version of class, for field names
    • subject attribute allows semantically linking within the page. Conceptually similar to the include-pattern.
    • content attribute on the meta element can be used to invisibly include data. Conceptually similar to the Value Class Pattern.
    • item attribute identifies blocks to be marked as structure data. Conceptually similar to the mfo-examples brainstorming?

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
  • 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?