Difference between revisions of "media-info-issues"

From Microformats Wiki
Jump to navigation Jump to search
(restrictions on elements)
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>&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.
 +
</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>&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>.
 
</div>
 
</div>
 
</div>
 
</div>

Revision as of 23:01, 11 November 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:

TobyInk

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)?
    2. Would be nice if the spec schema could be layed out using the cheatsheet conventions for plurality, optionality, etc.
    3. Where an image is not linked to using <a>, but embedded using <img> instead, then rel=enclosure cannot be used.
  • 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>.