html5 - Revision history

GRegorLove: s///

2023-07-26T21:27:28Z

s/<source>/<syntaxhighlight>/

← Older revision		Revision as of 21:27, 26 July 2023
Line 24:		Line 24:
	Here is the [[hcalendar#Examples\|hCalendar spec example]] updated to use section instead of div, and time instead of abbr.		Here is the [[hcalendar#Examples\|hCalendar spec example]] updated to use section instead of div, and time instead of abbr.

	<~~source~~ lang=~~html4strict~~>		<syntaxhighlight lang="html">
	<section class="vevent">		<section class="vevent">
	<a class="url" href="http://conferences.oreillynet.com/pub/w/40/program.html">		<a class="url" href="http://conferences.oreillynet.com/pub/w/40/program.html">
Line 34:		Line 34:
	at the <span class="location">Argent Hotel, San Francisco, CA</span>		at the <span class="location">Argent Hotel, San Francisco, CA</span>
	</section>		</section>
	</~~source~~>		</syntaxhighlight>

	=== article element ===		=== article element ===

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:28:09Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:28, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~Microformats in HTML5~~</entry-title>~~		{{DISPLAYTITLE:Microformats in HTML5}}

	''This page is to document '''future''' use of microformats in [http://www.w3.org/html/wg/html5 HTML5]. 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.''		''This page is to document '''future''' use of microformats in [http://www.w3.org/html/wg/html5 HTML5]. 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.''

Tantek: /* data attributes / add example of when data- attribute may be ok - site-specific library/API hooks

2013-11-21T19:47:03Z

data attributes: add example of when data-* attribute may be ok - site-specific library/API hooks

← Older revision		Revision as of 19:47, 21 November 2013
Line 42:		Line 42:
	'''<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 <em>not</em> 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.		* Note that the data-* stuff is explicitly <em>not</em> 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.

			Since data-* attributes are not for general data interchange or generic APIs supported by multiple sites / pieces of software, what are actual valid uses of data-* attributes? One example (feel free to add more)
			* Twitter's use of data-* attributes in markup to be picked up only by Twitter's javascript [https://dev.twitter.com/docs/tweet-button library for Tweet buttons], e.g. <code>data-related="indiewebcamp"</code> - indicates [https://twitter.com/indiewebcamp @indiewebcamp] is a related Twitter account for a tweet button.

	=== new semantic elements ===		=== new semantic elements ===

Tantek: /* time element */ pubdate has been dropped and other updates to the time element

2013-01-15T19:24:44Z

time element: pubdate has been dropped and other updates to the time element

← Older revision		Revision as of 19:24, 15 January 2013
Line 9:		Line 9:
	=== time element ===		=== time element ===
	'''<code>time</code> element for representing date times'''. In HTML5, the machine form of datetimes can be represented natively. In some cases it may be possible to replace the date-time design pattern with native HTML5.		'''<code>time</code> element for representing date times'''. In HTML5, the machine form of datetimes can be represented natively. In some cases it may be possible to replace the date-time design pattern with native HTML5.
	* <code>time</code> takes an optional <code>pubdate</code> attribute, to indicate the publication date of an <code>article</code>. Synonymous with [[hAtom]] <code>published</code>, may imply [[hAtom]] <code>updated</code>, may imply [[hReview]] <code>dtreviewed</code>, may imply [[hListing]] <code>dtlisted</code>

	Note that there are documented [http://wiki.whatwg.org/wiki/Time limitations in the time element]. Please add additional opinions and use cases to that wiki page so that we can help improve the time element.

	* Recommendation: Use the [[value-class-pattern]], in particular preferably <strong>date-time-separation</strong> for accessibly marking up dates and times while following the <abbr title="Don't Repeat Yourself">DRY</abbr> [[principle]] as much as possible.		* Recommendation: Use the [[value-class-pattern]], in particular preferably <strong>date-time-separation</strong> for accessibly marking up dates and times while following the <abbr title="Don't Repeat Yourself">DRY</abbr> [[principle]] as much as possible.
Line 18:		Line 15:

	* Try http://dev.h2vx.com/ (the beta version of [[H2VX]]) as it now has preliminary support for <code><time datetime></code> as well as the new semantic HTML5 elements.		* Try http://dev.h2vx.com/ (the beta version of [[H2VX]]) as it now has preliminary support for <code><time datetime></code> as well as the new semantic HTML5 elements.

			Note: that there are documented [http://wiki.whatwg.org/wiki/Time proposals to extend the time element]. Please add additional opinions and use cases to that wiki page so that we can help improve the time element.

			There was briefly an optional <code>pubdate</code> attribute, to indicate the publication date of an <code>article</code>, but it was dropped in 2012 since it is both unnecessary and insufficient. Rather than use the one-off pubdate attribute, it's much better to:
			* Use the [[hAtom]] microformat for articles, and the hAtom <code>published</code> property, as well as the hAtom <code>updated</code> property.

	==== hCalendar with time element ====		==== hCalendar with time element ====

Tantek: Issue: Some websites are not ready to upgrade to HTML5 - noted example by ChiefRA in IRC

2011-06-30T16:10:56Z

Issue: Some websites are not ready to upgrade to HTML5 - noted example by ChiefRA in IRC

← Older revision		Revision as of 16:10, 30 June 2011
Line 78:		Line 78:
	** 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. --[[User:BenWard\|BenWard]] 21:12, 4 September 2009 (UTC)		** 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. --[[User:BenWard\|BenWard]] 21:12, 4 September 2009 (UTC)
	* '''The [http://microformats.org/wiki/value-class-pattern#Date_and_time_parsing 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: [http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html#global-dates-and-times HTML5 time microsyntax for <time>] --[[User:Oli\|Oli]] 14:40, 14 February 2010 (+9)		* '''The [http://microformats.org/wiki/value-class-pattern#Date_and_time_parsing 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: [http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html#global-dates-and-times HTML5 time microsyntax for <time>] --[[User:Oli\|Oli]] 14:40, 14 February 2010 (+9)
			* '''Some websites are not ready to upgrade to HTML5''' and must stick with HTML4 (or XHTML1 served/interpreted as HTML4) for now. For example:
			** http://www.ascentsir.com/eng - according to [[IRC]] "ChiefRA" on 2011-06-30
	</div>		</div>

	== see also ==		== see also ==
	* [[HTML3]]		* [[HTML3]]

Tantek: /* The rel/rev attributes */ remove hypothetical authorOf relation (which doesn't exist, and also implies a camelcase pattern which microformats don't use) and use XFN parent/child example instead.

2011-01-31T23:38:35Z

The rel/rev attributes: remove hypothetical authorOf relation (which doesn't exist, and also implies a camelcase pattern which microformats don't use) and use XFN parent/child example instead.

← Older revision		Revision as of 23:38, 31 January 2011
Line 52:		Line 52:
	== Changes in HTML5 ==		== Changes in HTML5 ==
	=== The rel/rev attributes ===		=== The rel/rev attributes ===
	The <code>rev</code> attribute has been removed from HTML5. The <code>rel</code> attribute can be still be used in the same way, but microformats that assumed the existence of <code>rev</code> and thus only defined a single forward-facing relation may need to be changed to include an opposite relation as well. That is, for every ~~'authoredBy' relation, consider defining an 'authorOf'~~ relation, if the ~~opposite~~ relation is indeed useful.		The <code>rev</code> attribute has been removed from HTML5. The <code>rel</code> attribute can be still be used in the same way, but microformats that assumed the existence of <code>rev</code> and thus only defined a single forward-facing relation may need to be changed to include an opposite relation as well. That is, for every relation that goes in one direction (e.g. [[rel-parent]] of [[xfn]]), you must explicitly name and define the inverse relationship (e.g. [[rel-child]] of [[xfn]]) if the inverse relation is indeed useful.

	== Additions beyond HTML5 ==		== Additions beyond HTML5 ==

TabAtkins: Removed the rel/rev issue, as it was factually incorrect. Instead added a new section covering HTML5 changes that details the effect of the removal of @rel.

2011-01-31T19:12:15Z

Removed the rel/rev issue, as it was factually incorrect. Instead added a new section covering HTML5 changes that details the effect of the removal of @rel.

← Older revision		Revision as of 19:12, 31 January 2011
Line 49:		Line 49:

	AND try http://dev.h2vx.com/ (the beta version of [[H2VX]]) as it now has preliminary support for the new semantic HTML5 elements as well as <code><time datetime></code>.		AND try http://dev.h2vx.com/ (the beta version of [[H2VX]]) as it now has preliminary support for the new semantic HTML5 elements as well as <code><time datetime></code>.

			== Changes in HTML5 ==
			=== The rel/rev attributes ===
			The <code>rev</code> attribute has been removed from HTML5. The <code>rel</code> attribute can be still be used in the same way, but microformats that assumed the existence of <code>rev</code> and thus only defined a single forward-facing relation may need to be changed to include an opposite relation as well. That is, for every 'authoredBy' relation, consider defining an 'authorOf' relation, if the opposite relation is indeed useful.

	== Additions beyond HTML5 ==		== Additions beyond HTML5 ==
Line 69:		Line 73:
	==Issues==		==Issues==
	<div class='discussion issues'>		<div class='discussion issues'>
	* '''The <code>rev</code> attribute has been removed'''. In HTML5, <code>rel</code> and <code>rev</code> are no-longer paired, and the <code>rel</code> attribute nolonger describes the direction of a relationship. Microformats which use <code>rev</code> will need to use <code>rel</code> instead.
	** Or something like data-rev="vote-for"
	*** As above, <code>data-</code> attributes are for application-context functionality, ''not'' shared vocabularies. Further, the HTML5 specification makes <code>rel</code> the correct attribute to use, regardless of direction, through the changed specification. --[[User:BenWard\|BenWard]] 17:53, 12 May 2009 (UTC)
	** This is incorrect. <code>rel</code> is still directional, with the same semantic it has always had - If X has a link to Y with REL, then the relationship is X REL Y. <code>rev</code> has been removed, but that only means that relationships with opposite implication should be defined when necessary. That is, for every 'authoredBy' rel, there can be an 'authorOf' rel describing the opposite relation, if such a thing is necessary. [[User:TabAtkins\|TabAtkins]] 18:41, 31 January 2011 (UTC)
	* '''The <code>profile</code> attribute has been removed'''. In HTML, the <code>profile</code> attribute from the <code>head</code> has been removed, with no direct replacement. This causes issues for GRDDL support. It's been suggested that profile URLs be represented in <code>link</code> elements instead, or even as a custom HTTP header. See [[grddl]] and [[profile-uris]]		* '''The <code>profile</code> attribute has been removed'''. In HTML, the <code>profile</code> attribute from the <code>head</code> has been removed, with no direct replacement. This causes issues for GRDDL support. It's been suggested that profile URLs be represented in <code>link</code> 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. [[User:Tantek\|Tantek]] 23:24, 5 November 2009 (UTC)		** See [[rel-profile]] which is the replacement for the profile attribute. [[User:Tantek\|Tantek]] 23:24, 5 November 2009 (UTC)

TabAtkins: /* Issues */ The "rel is directionless in HTML5" issue is incorrect, so I provided a correction.

2011-01-31T18:41:09Z

Issues: The "rel is directionless in HTML5" issue is incorrect, so I provided a correction.

← Older revision		Revision as of 18:41, 31 January 2011
Line 72:		Line 72:
	** Or something like data-rev="vote-for"		** Or something like data-rev="vote-for"
	*** As above, <code>data-</code> attributes are for application-context functionality, ''not'' shared vocabularies. Further, the HTML5 specification makes <code>rel</code> the correct attribute to use, regardless of direction, through the changed specification. --[[User:BenWard\|BenWard]] 17:53, 12 May 2009 (UTC)		*** As above, <code>data-</code> attributes are for application-context functionality, ''not'' shared vocabularies. Further, the HTML5 specification makes <code>rel</code> the correct attribute to use, regardless of direction, through the changed specification. --[[User:BenWard\|BenWard]] 17:53, 12 May 2009 (UTC)
			** This is incorrect. <code>rel</code> is still directional, with the same semantic it has always had - If X has a link to Y with REL, then the relationship is X REL Y. <code>rev</code> has been removed, but that only means that relationships with opposite implication should be defined when necessary. That is, for every 'authoredBy' rel, there can be an 'authorOf' rel describing the opposite relation, if such a thing is necessary. [[User:TabAtkins\|TabAtkins]] 18:41, 31 January 2011 (UTC)
	* '''The <code>profile</code> attribute has been removed'''. In HTML, the <code>profile</code> attribute from the <code>head</code> has been removed, with no direct replacement. This causes issues for GRDDL support. It's been suggested that profile URLs be represented in <code>link</code> elements instead, or even as a custom HTTP header. See [[grddl]] and [[profile-uris]]		* '''The <code>profile</code> attribute has been removed'''. In HTML, the <code>profile</code> attribute from the <code>head</code> has been removed, with no direct replacement. This causes issues for GRDDL support. It's been suggested that profile URLs be represented in <code>link</code> 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. [[User:Tantek\|Tantek]] 23:24, 5 November 2009 (UTC)		** See [[rel-profile]] which is the replacement for the profile attribute. [[User:Tantek\|Tantek]] 23:24, 5 November 2009 (UTC)

TobyInk: /* time element */ HTML::Microformats supports .

2010-12-22T09:58:35Z

time element: HTML::Microformats supports <time>.

← Older revision		Revision as of 09:58, 22 December 2010
Line 14:		Line 14:

	* Recommendation: Use the [[value-class-pattern]], in particular preferably <strong>date-time-separation</strong> for accessibly marking up dates and times while following the <abbr title="Don't Repeat Yourself">DRY</abbr> [[principle]] as much as possible.		* Recommendation: Use the [[value-class-pattern]], in particular preferably <strong>date-time-separation</strong> for accessibly marking up dates and times while following the <abbr title="Don't Repeat Yourself">DRY</abbr> [[principle]] as much as possible.

			* [[parsers#HTML::Microformats\|HTML::Microformats]] and its predecessors have supported the <code>time</code> element since July 2008.

	* Try http://dev.h2vx.com/ (the beta version of [[H2VX]]) as it now has preliminary support for <code><time datetime></code> as well as the new semantic HTML5 elements.		* Try http://dev.h2vx.com/ (the beta version of [[H2VX]]) as it now has preliminary support for <code><time datetime></code> as well as the new semantic HTML5 elements.

Tantek: /* New features in HTML5 */ try dev.h2vx.com for HTML5 support

2010-09-02T16:09:54Z

New features in HTML5: try dev.h2vx.com for HTML5 support

← Older revision		Revision as of 16:09, 2 September 2010
Line 14:		Line 14:

	* Recommendation: Use the [[value-class-pattern]], in particular preferably <strong>date-time-separation</strong> for accessibly marking up dates and times while following the <abbr title="Don't Repeat Yourself">DRY</abbr> [[principle]] as much as possible.		* Recommendation: Use the [[value-class-pattern]], in particular preferably <strong>date-time-separation</strong> for accessibly marking up dates and times while following the <abbr title="Don't Repeat Yourself">DRY</abbr> [[principle]] as much as possible.

			* Try http://dev.h2vx.com/ (the beta version of [[H2VX]]) as it now has preliminary support for <code><time datetime></code> as well as the new semantic HTML5 elements.

	==== hCalendar with time element ====		==== hCalendar with time element ====
Line 36:		Line 38:
	'''<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 <em>not</em> 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.		* Note that the data-* stuff is explicitly <em>not</em> 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.

			=== new semantic elements ===
			HTML5 has numerous new semantic elements.

			Most microformats [[parsers]] probably won't recognize those elements and may ignore them - so avoid using microformats classes on new HTML5 semantic elements for anything in production.

			HOWEVER, do try experimenting with microformats and new semantic HTML5,

			AND try http://dev.h2vx.com/ (the beta version of [[H2VX]]) as it now has preliminary support for the new semantic HTML5 elements as well as <code><time datetime></code>.

	== Additions beyond HTML5 ==		== Additions beyond HTML5 ==