Difference between revisions of "media-info-issues"

From Microformats Wiki
Jump to navigation Jump to search
(→‎2008 issues: resolving issues)
 
(4 intermediate revisions by 2 users not shown)
Line 7: Line 7:
 
In order of contribution:
 
In order of contribution:
  
[[User:TobyInk|TobyInk]]
+
* [[User:TobyInk|TobyInk]]
 
+
* [[User:WebOrganics|Martin McEvoy]]
 
== Issues Template ==
 
== Issues Template ==
  
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>&lt;a></code>, but embedded using <code>&lt;img></code> instead, then rel=enclosure cannot be used.
 
*# Where an image is not linked to using <code>&lt;a></code>, but embedded using <code>&lt;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>&lt;video></code> element, which would make perfect sense to allow here (for those people who choose to use HTML5). Also, <code>&lt;embed></code> or (for animated GIFs) <code>&lt;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>&lt;video></code> element, which would make perfect sense to allow here (for those people who choose to use HTML5). Also, <code>&lt;embed></code> or (for animated GIFs) <code>&lt;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">
 +
* 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 Media info proposal now states that any appropriate html element may be used such as <code>&lt;object></code>
 +
</div>
 
</div>
 
</div>
 
</div>
 
</div>

Latest revision as of 01:05, 23 December 2008

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 open issue! tag.

Contributors

In order of contribution:

Issues Template

Consider using this format (copy and paste this to the end of the list to add your issues; replace ~~~ with an external link if preferred) to report issues or feedback, so that issues can show up in hAtom subscriptions of this issues page. If open issues lack this markup, please add it.

Please post one issue per entry, to make them easier to manage. Avoid combining multiple issues into single reports, as this can confuse or muddle feedback, and puts a burden of separating the discrete issues onto someone else who 1. may not have the time, and 2. may not understand the issue in the same way as the original reporter.

<div class="hentry">
{{OpenIssue}} 
<span class="entry-summary author vcard">
 <span class="published">2011-MM-DD</span> 
 raised by <span class="fn">~~~</span>
</span>
<div class="entry-content discussion issues">
* <strong class="entry-title">«Short title of issue»</strong>. «Description of Issue»
** Follow-up comment #1
** Follow-up comment #2
</div>
</div>

2008 issues

  • open issue! 2008-11-10 raised by TobyInk
    1. comment: This bends the definitions of several hCard properties. Would it not be better to make the content model for comment not an hCard, but rather an hAtom entry (which may contain an author hCard)?
  • comment is no longer part of the media-info-proposal
    1. Would be nice if the spec schema could be layed out using the 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

    • The Media Info Schema now uses cheatsheet conventions
    1. Where an image is not linked to using <a>, but embedded using <img> instead, then rel=enclosure cannot be used.
  • rel-enclosure should not be used with an in-line photo, 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.
  • open issue! 2008-11-11 raised by TobyInk
    1. 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 includes a <video> element, which would make perfect sense to allow here (for those people who choose to use HTML5). Also, <embed> or (for animated GIFs) <img>.
  • In 2022 or whenever html5 is complete media-info will use the <video> tag, the media-info-proposal is based on examples animated gifs did not feature in any of the examples, the <embed> html tag has not been included so would be authors do not use <embed> 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 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 <object>