haudio-issues

[boilerplate to follow]

issues

Please add new issues to the bottom of the list by copy and pasting the Template. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

2008

• open issue! 2008-01-10 raised by Andy Mabbett in http://microformats.org/discuss/mail/microformats-discuss/2008-January/011340.html

• 1. contributor (see e-mail; pending expansion here).

• open issue! 2008-10-01 raised by Andy Mabbett in http://microformats.org/discuss/mail/microformats-discuss/2008-January/011342.html

• 1. fn (see e-mail; pending expansion here).

• open issue! 2008-01-10 raised by Andy Mabbett in http://microformats.org/discuss/mail/microformats-discuss/2008-January/011343.html

• 1. The recommended use of "position" in hAudio is contrary to the good practice, semantic use of ordered lists (see also [1] et seq)

• open issue! 2008-10-01 raised by Andy Mabbett in http://microformats.org/discuss/mail/microformats-discuss/2008-January/011344.html

• 1. rel-enclosure (not suitable for streaming media) & linking (see e-mail; pending expansion here).

• open issue! 2008-MM-DD raised by Andy Mabbett in http://microformats.org/discuss/mail/microformats-discuss/2008-January/011345.html

• 1. The "Notes" section of the hAudio spec says By marking up audio content with the hAudio microformat, the expectation is communicated that information about the content MAY be indexed. This has no impact on the copyright of the content itself which the publisher may explicitly specify using rel-license as specified above.. However, that is the first and only reference to rel-license on the page.

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>

see also

• audio-info-issues

related pages

• hAudio
• hAudio cheatsheet - hAudio properties.
• hAudio authoring - learn how to add hAudio markup to your existing web pages.
• hAudio issues - issues with the specification.
  • Audio info issues - issues with the preparatory work.
• hAudio brainstorming - ideas for the specification.
• hAudio-history - the history of the research and development of hAudio.