html5: Difference between revisions
Jump to navigation
Jump to search
(time element, not t element.) |
|||
| Line 5: | Line 5: | ||
==New features in HTML5== | ==New features in HTML5== | ||
* '''<code> | * '''<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 | * '''<code>data-</code> naming convention for tag attributes'''. the draft specification states that any | ||
Revision as of 13:19, 24 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
timeelement 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.
Issues
- The
revattribute has been removed. In HTML5,relandrevare no-longer paired, and therelattribute nolonger describes the direction of a relationship. Microformats which userevwill need to userelinstead. - The
profileattribute has been removed. In HTML, theprofileattribute from theheadhas been removed, with no direct replacement. This causes issues for GRDDL support. It's been suggested that profile URLs be represented inlinkelements instead.