haudio-issues

hAudio issues

These are externally raised issues about hAudio with broadly varying degrees of merit. Thus some issues are rejected for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be accepted and perhaps cause changes or improved explanations in the spec.

Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible.

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! D1: 2008-01-10 raised by Andy Mabbett in microformats-discuss/2008-January/011340.html

• 1. the wording about contributor could be improved to facilitate more streamlined mark-up (see above e-mail for details).

• open issue! D2: 2008-01-10 raised by Andy Mabbett in [1]

• 1. The "overloading" of fn for both the tile of a work and the name of a contributor causes problems (see above e-mail for examples). Another example of this problem is a table, where the "artist" column comes before the "title" column. For discussion, see also microformats-new/2008-January/001375.html.
     • Manu Sporny has propsosed that "fn" should be replaced with "title" see: microformats-new/2008-February/001468.html

• open issue! D3: 2008-01-10 raised by Andy Mabbett in 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 example and suggested solution in the above e-mail; also [2] et seq)
     • For Cognition I'm considering an extension: if no position has been explicitly marked up, and the item is <li class="item"> within an ordered list, then the position is taken to be the numerical value of the list marker. (To calculate the numerical value for the list marker, find the most recent sibling <li> element which has a value attribute. The numerical value is the number in that value attribute added to the count of <li> elements after that value attribute up to the current one. If there are no such <li> elements with value attributes, then you should assume that the value attribute of the first list item is equal to the start attribute of the ordered list itself, or "1" if there is no such start attribute. TobyInk 04:24, 29 Jul 2008 (PDT)

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

• 1. The required use of rel-enclosure does not allow for links to streaming files, which are not cacheable, and are thus outside the scope of rel-enclosure. An example on the BBC website has the relevant link is below the heading "LISTEN AGAIN". (see discussion at microformats-new/2008-January/001339.html et seq).

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

• 1. There appears to be no mechanism to mark up an hAudio, expressed in plain text on page A, which links to an interim page, B, which in turn links to a file download. For example, the radio shows listed on [3].

• open issue! D6: 2008-01-10 raised by Andy Mabbett in 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.