html5: Difference between revisions
Jump to navigation
Jump to search
(there has been the suggestion of putting the profiles in an http header) |
IanHickson (talk | contribs) |
||
Line 7: | Line 7: | ||
* '''<code>time</code> 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. | * '''<code>time</code> 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. | ||
* '''<code>data-</code> 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. | * '''<code>data-</code> 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. | |||
==Issues== | ==Issues== |
Revision as of 22:29, 30 July 2008
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.
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.
Issues
- The
rev
attribute has been removed. In HTML5,rel
andrev
are no-longer paired, and therel
attribute nolonger describes the direction of a relationship. Microformats which userev
will need to userel
instead.- Or something like data-rev="vote-for".
- The
profile
attribute has been removed. In HTML, theprofile
attribute from thehead
has been removed, with no direct replacement. This causes issues for GRDDL support. It's been suggested that profile URLs be represented inlink
elements instead, or even as a custom HTTP header.