html5: Difference between revisions
Jump to navigation
Jump to search
(→microdata: updated attribute definitions and uses, changed microdata vocabulary links to working versions, removed out-of-date warnings about using microdata vocabularies) |
m (→microdata: fixed itemref presentation, added example) |
||
| 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> | * <code>itemref</code> attribute allows including properties elsewhere on the page that are not descendants of <code>itemscope</code>. Takes space-separated ids (for example <code>itemref="address phone"</code> would include the elements with <code>id="address"</code> and <code>id="phone"</code>). Conceptually similar to the [[include-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><head></code>, make sure to include via <code>itemref</code>. 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><head></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 structured 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? | ||
Revision as of 14:51, 12 July 2010
<entry-title>Microformats in HTML 5</entry-title>
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
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.
timetakes an optionalpubdateattribute, to indicate the publication date of anarticle. Synonymous with hAtompublished, may imply hAtomupdated, may imply hReviewdtreviewed, may imply hListingdtlisted
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.
itempropattribute is a more specific version ofclass, for field namessubjectattribute allows semantically linking within the page. Conceptually similar to the include-pattern.itemrefattribute allows including properties elsewhere on the page that are not descendants ofitemscope. Takes space-separated ids (for exampleitemref="address phone"would include the elements withid="address"andid="phone"). Conceptually similar to the include-pattern.contentattribute on themetaelement can be used to include data that is not part of the content. As current browsers movemetainside<head>, make sure to include viaitemref. Conceptually similar to the value-class-pattern.itemscopeattribute identifies blocks to be marked as structured data. Conceptually similar to the mfo brainstorming?itemtypeattribute to specify the type for an item (for example:itemtype="http://microformats.org/profile/hcard")
microdata vocabularies
- microdata vCard - this is based directly on vCard. Alternatively use Google’s Rich Snippets vocabularies (Person and Organization), which are simplified versions also based on vCard
- microdata vEvent - this is based directly on iCalendar. Alternatively use Google’s Rich Snippets vocabulary (Event), which is a simplified version also based on iCalendar
- microdata Licensing Works - see also licensing-brainstorming
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.
- Note that the data-* stuff is explicitly not for microformats. 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. There may be some cases of private poshformats that are never intended for interchange that may be used in data-* attributes.
Current microformat compatibility
There seems to be no issue with current implementation of the following microformats in HTML 5:
Requests
- "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
timeelement for dates and times for microformats). See (and add to if necessary) :- hCard brainstorming - how to use with HTML5
- hCalendar brainstorming - how to use with HTML5 e.g. hCalendar with the
timeelement - citation brainstorming - how to use with HTML5
- if nothing special is required for HTML5, then after performing the analysis, that should be noted as well, for the purpose of clarity.
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.- Or something like data-rev="vote-for"
- As above,
data-attributes are for application-context functionality, not shared vocabularies. Further, the HTML5 specification makesrelthe correct attribute to use, regardless of direction, through the changed specification. --BenWard 17:53, 12 May 2009 (UTC)
- As above,
- Or something like data-rev="vote-for"
- 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, 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
itempropduplicatesclassdata. 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)