media-info-issues - Revision history

WebOrganics: /* 2008 issues */ resolving issues

2008-12-23T01:05:27Z

2008 issues: resolving issues

← Older revision		Revision as of 01:05, 23 December 2008
Line 42:		Line 42:
	* In 2022 or whenever html5 is complete media-info will use the <code><video></code> tag, the media-info-proposal is based on examples animated gifs did not feature in any of the examples, the <code><embed></code> html tag has not been included so would be authors do not use <code><embed></code> for flash video's.		* In 2022 or whenever html5 is complete media-info will use the <code><video></code> tag, the media-info-proposal is based on examples animated gifs did not feature in any of the examples, the <code><embed></code> html tag has not been included so would be authors do not use <code><embed></code> for flash video's.
	** The widely quoted 2022 date for HTML 5. That is Hixie's predicted date for HTML 5 to become a W3C Recommendation. The spec is expected to become a stable draft (and start to become widely used) over the next two to three years, but under current W3C rules, a Recommendation requires at least two interoperable implementations, which is why Hixie is allowing such a long time to reach Recommendation status. See [http://wiki.whatwg.org/wiki/FAQ#When_will_HTML_5_be_finished.3F WHATWG Wiki: FAQ: When will HTML 5 be finished?]		** The widely quoted 2022 date for HTML 5. That is Hixie's predicted date for HTML 5 to become a W3C Recommendation. The spec is expected to become a stable draft (and start to become widely used) over the next two to three years, but under current W3C rules, a Recommendation requires at least two interoperable implementations, which is why Hixie is allowing such a long time to reach Recommendation status. See [http://wiki.whatwg.org/wiki/FAQ#When_will_HTML_5_be_finished.3F WHATWG Wiki: FAQ: When will HTML 5 be finished?]
			*** The Media info proposal now states that any appropriate html element may be used such as <code><object></code>
	</div>		</div>
	</div>		</div>
	</div>		</div>

WebOrganics: /* 2008 issues */ adding styles

2008-12-23T00:58:30Z

2008 issues: adding styles

← Older revision		Revision as of 00:58, 23 December 2008
Line 19:		Line 19:
	<div class="description">		<div class="description">
	*# <code>comment</code>: This bends the definitions of several hCard properties. Would it not be better to make the content model for <code>comment</code> not an hCard, but rather an hAtom entry (which may contain an author hCard)?		*# <code>comment</code>: This bends the definitions of several hCard properties. Would it not be better to make the content model for <code>comment</code> not an hCard, but rather an hAtom entry (which may contain an author hCard)?
	# <code>comment</code> is no longer part of the media-info-proposal		<div class="discussion issues">
			* <code>comment</code> is no longer part of the media-info-proposal
			</div>
	*# Would be nice if the spec schema could be layed out using the [[hcalendar-cheatsheet#Key\|cheatsheet conventions]] for plurality, optionality, etc.		*# Would be nice if the spec schema could be layed out using the [[hcalendar-cheatsheet#Key\|cheatsheet conventions]] for plurality, optionality, etc.
	# The media-info schema is published using the same format most other schemas on the wiki, like many other microformats a separate cheat sheet page will be supplied once the media-info proposal is complete		<div class="discussion issues">
			* The media-info schema is published using the same format most other schemas on the wiki, like many other microformats a separate cheat sheet page will be supplied
			once the media-info proposal is complete
			** The Media Info Schema now uses cheatsheet conventions
			</div>
	*# Where an image is not linked to using <code><a></code>, but embedded using <code><img></code> instead, then rel=enclosure cannot be used.		*# Where an image is not linked to using <code><a></code>, but embedded using <code><img></code> instead, then rel=enclosure cannot be used.
	# rel-enclosure should not be used with an in-line <code>photo</code>, rel-enclosure should only be used to link to the download version of an image, this is not just limited to gif, jpeg, png etc.. it also includes archives such as zip or rar files.		<div class="discussion issues">
			* rel-enclosure should not be used with an in-line <code>photo</code>, rel-enclosure should only be used to link to the download version of an image, this is not just limited to gif, jpeg, png etc.. it also includes archives such as zip or rar files.
			</div>
	</div>		</div>
	</div>		</div>
Line 31:		Line 39:
	<div class="description">		<div class="description">
	*# The schema currently includes: "video[1]. Using the HTML elemens DIV, SPAN or OBJECT." This restriction on which elements may be used seems arbitrary and not very forwards-thinking — for example [[html5\|HTML5]] includes a <code><video></code> element, which would make perfect sense to allow here (for those people who choose to use HTML5). Also, <code><embed></code> or (for animated GIFs) <code><img></code>.		*# The schema currently includes: "video[1]. Using the HTML elemens DIV, SPAN or OBJECT." This restriction on which elements may be used seems arbitrary and not very forwards-thinking — for example [[html5\|HTML5]] includes a <code><video></code> element, which would make perfect sense to allow here (for those people who choose to use HTML5). Also, <code><embed></code> or (for animated GIFs) <code><img></code>.
	# In 2022 or whenever html5 is complete media-info will use the <code><video></code> tag, the media-info-proposal is based on examples animated gifs did not feature in any of the examples, the <code><embed></code> html tag has not been included so would be authors do not use <code><embed></code> for flash video's.		<div class="discussion issues">
	#* The widely quoted 2022 date for HTML 5. That is Hixie's predicted date for HTML 5 to become a W3C Recommendation. The spec is expected to become a stable draft (and start to become widely used) over the next two to three years, but under current W3C rules, a Recommendation requires at least two interoperable implementations, which is why Hixie is allowing such a long time to reach Recommendation status. See [http://wiki.whatwg.org/wiki/FAQ#When_will_HTML_5_be_finished.3F WHATWG Wiki: FAQ: When will HTML 5 be finished?]		* In 2022 or whenever html5 is complete media-info will use the <code><video></code> tag, the media-info-proposal is based on examples animated gifs did not feature in any of the examples, the <code><embed></code> html tag has not been included so would be authors do not use <code><embed></code> for flash video's.
			** The widely quoted 2022 date for HTML 5. That is Hixie's predicted date for HTML 5 to become a W3C Recommendation. The spec is expected to become a stable draft (and start to become widely used) over the next two to three years, but under current W3C rules, a Recommendation requires at least two interoperable implementations, which is why Hixie is allowing such a long time to reach Recommendation status. See [http://wiki.whatwg.org/wiki/FAQ#When_will_HTML_5_be_finished.3F WHATWG Wiki: FAQ: When will HTML 5 be finished?]
			</div>
	</div>		</div>
	</div>		</div>

TobyInk: /* 2008 issues */ html5 schedule

2008-11-13T09:57:00Z

2008 issues: html5 schedule

← Older revision		Revision as of 09:57, 13 November 2008
Line 32:		Line 32:
	*# The schema currently includes: "video[1]. Using the HTML elemens DIV, SPAN or OBJECT." This restriction on which elements may be used seems arbitrary and not very forwards-thinking — for example [[html5\|HTML5]] includes a <code><video></code> element, which would make perfect sense to allow here (for those people who choose to use HTML5). Also, <code><embed></code> or (for animated GIFs) <code><img></code>.		*# The schema currently includes: "video[1]. Using the HTML elemens DIV, SPAN or OBJECT." This restriction on which elements may be used seems arbitrary and not very forwards-thinking — for example [[html5\|HTML5]] includes a <code><video></code> element, which would make perfect sense to allow here (for those people who choose to use HTML5). Also, <code><embed></code> or (for animated GIFs) <code><img></code>.
	# In 2022 or whenever html5 is complete media-info will use the <code><video></code> tag, the media-info-proposal is based on examples animated gifs did not feature in any of the examples, the <code><embed></code> html tag has not been included so would be authors do not use <code><embed></code> for flash video's.		# In 2022 or whenever html5 is complete media-info will use the <code><video></code> tag, the media-info-proposal is based on examples animated gifs did not feature in any of the examples, the <code><embed></code> html tag has not been included so would be authors do not use <code><embed></code> for flash video's.
			#* The widely quoted 2022 date for HTML 5. That is Hixie's predicted date for HTML 5 to become a W3C Recommendation. The spec is expected to become a stable draft (and start to become widely used) over the next two to three years, but under current W3C rules, a Recommendation requires at least two interoperable implementations, which is why Hixie is allowing such a long time to reach Recommendation status. See [http://wiki.whatwg.org/wiki/FAQ#When_will_HTML_5_be_finished.3F WHATWG Wiki: FAQ: When will HTML 5 be finished?]
	</div>		</div>
	</div>		</div>

WebOrganics at 18:56, 12 November 2008

2008-11-12T18:56:41Z

← Older revision		Revision as of 18:56, 12 November 2008
Line 7:		Line 7:
	In order of contribution:		In order of contribution:

	[[User:TobyInk\|TobyInk]]		* [[User:TobyInk\|TobyInk]]
	[[User:WebOrganics\|Martin McEvoy]]		* [[User:WebOrganics\|Martin McEvoy]]
	== Issues Template ==		== Issues Template ==

WebOrganics at 18:56, 12 November 2008

2008-11-12T18:56:23Z

← Older revision		Revision as of 18:56, 12 November 2008
Line 8:		Line 8:

	[[User:TobyInk\|TobyInk]]		[[User:TobyInk\|TobyInk]]
			[[User:WebOrganics\|Martin McEvoy]]
	== Issues Template ==		== Issues Template ==

WebOrganics: /* 2008 issues */

2008-11-12T18:54:27Z

2008 issues

← Older revision		Revision as of 18:54, 12 November 2008
Line 31:		Line 31:
	<div class="description">		<div class="description">
	*# The schema currently includes: "video[1]. Using the HTML elemens DIV, SPAN or OBJECT." This restriction on which elements may be used seems arbitrary and not very forwards-thinking — for example [[html5\|HTML5]] includes a <code><video></code> element, which would make perfect sense to allow here (for those people who choose to use HTML5). Also, <code><embed></code> or (for animated GIFs) <code><img></code>.		*# The schema currently includes: "video[1]. Using the HTML elemens DIV, SPAN or OBJECT." This restriction on which elements may be used seems arbitrary and not very forwards-thinking — for example [[html5\|HTML5]] includes a <code><video></code> element, which would make perfect sense to allow here (for those people who choose to use HTML5). Also, <code><embed></code> or (for animated GIFs) <code><img></code>.
	# In 2022 or whenever html5 is complete media-info will ~~reuse~~ the <code><video></code> tag, the media-info-proposal is based on examples animated gifs did not feature in any of the examples, the <code><embed></code> html tag has not been included so would be authors do not use <code><embed></code> for flash video's.		# In 2022 or whenever html5 is complete media-info will use the <code><video></code> tag, the media-info-proposal is based on examples animated gifs did not feature in any of the examples, the <code><embed></code> html tag has not been included so would be authors do not use <code><embed></code> for flash video's.
	</div>		</div>
	</div>		</div>

WebOrganics: /* 2008 issues */

2008-11-12T18:53:50Z

2008 issues

← Older revision		Revision as of 18:53, 12 November 2008
Line 19:		Line 19:
	<div class="description">		<div class="description">
	*# <code>comment</code>: This bends the definitions of several hCard properties. Would it not be better to make the content model for <code>comment</code> not an hCard, but rather an hAtom entry (which may contain an author hCard)?		*# <code>comment</code>: This bends the definitions of several hCard properties. Would it not be better to make the content model for <code>comment</code> not an hCard, but rather an hAtom entry (which may contain an author hCard)?
			# <code>comment</code> is no longer part of the media-info-proposal
	*# Would be nice if the spec schema could be layed out using the [[hcalendar-cheatsheet#Key\|cheatsheet conventions]] for plurality, optionality, etc.		*# Would be nice if the spec schema could be layed out using the [[hcalendar-cheatsheet#Key\|cheatsheet conventions]] for plurality, optionality, etc.
			# The media-info schema is published using the same format most other schemas on the wiki, like many other microformats a separate cheat sheet page will be supplied once the media-info proposal is complete
	*# Where an image is not linked to using <code><a></code>, but embedded using <code><img></code> instead, then rel=enclosure cannot be used.		*# Where an image is not linked to using <code><a></code>, but embedded using <code><img></code> instead, then rel=enclosure cannot be used.
			# rel-enclosure should not be used with an in-line <code>photo</code>, rel-enclosure should only be used to link to the download version of an image, this is not just limited to gif, jpeg, png etc.. it also includes archives such as zip or rar files.
	</div>		</div>
	</div>		</div>
Line 28:		Line 31:
	<div class="description">		<div class="description">
	*# The schema currently includes: "video[1]. Using the HTML elemens DIV, SPAN or OBJECT." This restriction on which elements may be used seems arbitrary and not very forwards-thinking — for example [[html5\|HTML5]] includes a <code><video></code> element, which would make perfect sense to allow here (for those people who choose to use HTML5). Also, <code><embed></code> or (for animated GIFs) <code><img></code>.		*# The schema currently includes: "video[1]. Using the HTML elemens DIV, SPAN or OBJECT." This restriction on which elements may be used seems arbitrary and not very forwards-thinking — for example [[html5\|HTML5]] includes a <code><video></code> element, which would make perfect sense to allow here (for those people who choose to use HTML5). Also, <code><embed></code> or (for animated GIFs) <code><img></code>.
			# In 2022 or whenever html5 is complete media-info will reuse the <code><video></code> tag, the media-info-proposal is based on examples animated gifs did not feature in any of the examples, the <code><embed></code> html tag has not been included so would be authors do not use <code><embed></code> for flash video's.
	</div>		</div>
	</div>		</div>

TobyInk: restrictions on elements

2008-11-11T23:01:17Z

restrictions on elements

← Older revision		Revision as of 23:01, 11 November 2008
Line 21:		Line 21:
	*# Would be nice if the spec schema could be layed out using the [[hcalendar-cheatsheet#Key\|cheatsheet conventions]] for plurality, optionality, etc.		*# Would be nice if the spec schema could be layed out using the [[hcalendar-cheatsheet#Key\|cheatsheet conventions]] for plurality, optionality, etc.
	*# Where an image is not linked to using <code><a></code>, but embedded using <code><img></code> instead, then rel=enclosure cannot be used.		*# Where an image is not linked to using <code><a></code>, but embedded using <code><img></code> instead, then rel=enclosure cannot be used.
			</div>
			</div>

			<div class="vevent">
			* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-11-11</span> raised by <span class="fn">[[User:TobyInk\|TobyInk]]</span></span>
			<div class="description">
			*# The schema currently includes: "video[1]. Using the HTML elemens DIV, SPAN or OBJECT." This restriction on which elements may be used seems arbitrary and not very forwards-thinking — for example [[html5\|HTML5]] includes a <code><video></code> element, which would make perfect sense to allow here (for those people who choose to use HTML5). Also, <code><embed></code> or (for animated GIFs) <code><img></code>.
	</div>		</div>
	</div>		</div>

WebOrganics at 20:17, 10 November 2008

2008-11-10T20:17:02Z

← Older revision		Revision as of 20:17, 10 November 2008
Line 1:		Line 1:
	= Media info issues =		= Media info issues =
	This page defines the current issues with the hMedia draft specification. Any issues that have not yet been resolved are marked with an {{OpenIssue}} tag.		This page defines the current issues with the [[media-info-proposal\|hMedia draft specification]]. Any issues that have not yet been resolved are marked with an {{OpenIssue}} tag.
	{{TOC-right}}		{{TOC-right}}

WebOrganics: tidy page

2008-11-10T20:15:44Z

tidy page

← Older revision		Revision as of 20:15, 10 November 2008
Line 1:		Line 1:
	=hMedia Issues=		= Media info issues =
			This page defines the current issues with the hMedia draft specification. Any issues that have not yet been resolved are marked with an {{OpenIssue}} tag.
			{{TOC-right}}

			== Contributors ==

			In order of contribution:

			[[User:TobyInk\|TobyInk]]

			== Issues Template ==

			{{issues-format}}

			== 2008 issues ==

	<div class="vevent">		<div class="vevent">