Generic Metadata Mechanisms - Revision history

GPHemsley: +spec

2012-11-10T16:13:28Z

+spec

← Older revision		Revision as of 16:13, 10 November 2012
Line 1:		Line 1:
	{{obsolete}}		{{obsolete\|spec=[http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html#microdata HTML Standard: Microdata]}}

	There have been some requests for introducing generic metadata mechanisms into HTML5.		There have been some requests for introducing generic metadata mechanisms into HTML5.

2012-11-10T15:44:22Z

microdata was added to html

← Older revision		Revision as of 15:44, 10 November 2012
Line 1:		Line 1:
			{{obsolete}}

	There have been some requests for introducing generic metadata mechanisms into HTML5.		There have been some requests for introducing generic metadata mechanisms into HTML5.

2011-01-26T12:10:28Z

Block or external metadata

2009-04-22T00:32:32Z

← Older revision		Revision as of 00:32, 22 April 2009
Line 7:		Line 7:
	= Goals =		= Goals =
	== What is the problem we are trying to solve? ==		== What is the problem we are trying to solve? ==
	~~'''Nobody has yet answered this in this wiki; please see http://lists~~.~~whatwg.org/pipermail/whatwg-whatwg.org/2008-September/016186.html for commentary and advice on how to fill this in.'''~~		See [[Microdata Problem Descriptions]].

	== Who faces this problem? ==		== Who faces this problem? ==

2008-12-01T11:54:05Z

adding extrenal metadata con; commenting out the "notes to me"; the reader gets the impression of reading a diary

2008-12-01T11:49:11Z

← Older revision		Revision as of 11:49, 1 December 2008
Line 152:		Line 152:
	* Con: Requires new metadata format to be created.		* Con: Requires new metadata format to be created.
	* Con: CSS-like targeting or use of class or id to apply metadata adds complexity/indirection.		* Con: CSS-like targeting or use of class or id to apply metadata adds complexity/indirection.

			[[Category:Feature Request]]

2008-09-23T15:03:00Z

DOM consistency

← Older revision		Revision as of 15:03, 23 September 2008
Line 46:		Line 46:
	== DOM consistency ==		== DOM consistency ==

	The DOM has to be consistent between HTML and XHTML representations. If it isn't, then migrating between the two becomes non-trivial, especially for scripting.		The DOM has to be consistent between the HTML and XHTML representations of the HTML5 specification. If it isn't, then migrating between the two becomes non-trivial, especially for scripting.

	== Ease of deployment ==		== Ease of deployment ==

2008-09-23T14:59:42Z

Machine-readable

← Older revision		Revision as of 14:59, 23 September 2008
Line 24:		Line 24:
	== Machine-readable ==		== Machine-readable ==

	A machine-readable and standardized way to apply semantic properties (metadata) to DOM elements in HTML5 ~~(text/html)~~ and XHTML5 ~~(application/xhtml+xml)~~.		A machine-readable and standardized way to apply semantic properties (metadata) to DOM elements in HTML5 and XHTML5.

	'''Needs more detail. What does it mean to be machine-readable?'''		'''Needs more detail. What does it mean to be machine-readable?'''

2008-09-23T14:59:07Z

Machine-readable

← Older revision		Revision as of 14:59, 23 September 2008
Line 24:		Line 24:
	== Machine-readable ==		== Machine-readable ==

	A machine-readable and standardized way to apply semantic properties (metadata) to DOM elements in HTML5 and ~~probably XHTML~~.		A machine-readable and standardized way to apply semantic properties (metadata) to DOM elements in HTML5 (text/html) and XHTML5 (application/xhtml+xml).

	'''Needs more detail. What does it mean to be machine-readable?'''		'''Needs more detail. What does it mean to be machine-readable?'''

2008-09-11T04:05:20Z

Related Proposals, Research and Discussions

@@ Line 102: / Line 102: @@
 * [http://www.foaf-project.org/ Friend of a Friend Project (FOAF)]
 * [http://dublincore.org/ Dublin Core Metadata Initiative (DCMI)]
 == Proposals ==