Difference between revisions of "haudio-issues"

From Microformats Wiki
Jump to navigation Jump to search
(updating issues)
Line 14: Line 14:
 
<div class="description">
 
<div class="description">
 
*# the wording about <code>contributor</code> could be improved to facilitate more streamlined mark-up (see above e-mail for details).
 
*# the wording about <code>contributor</code> could be improved to facilitate more streamlined mark-up (see above e-mail for details).
* [[haudio#Contributor | hAudio Contributor]] says "The contents of the element SHOULD include a valid [[hcard | hCard microformat]]" and "The contents of the element MAY be specified in plain-text".
+
*#* [[haudio#Contributor | hAudio Contributor]] says "The contents of the element SHOULD include a valid [[hcard | hCard microformat]]" and "The contents of the element MAY be specified in plain-text".
 
</div>
 
</div>
 
</div>
 
</div>
Line 23: Line 23:
 
*# The "overloading" of <code>fn</code> 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 [http://microformats.org/discuss/mail/microformats-new/2008-January/001375.html microformats-new/2008-January/001375.html].
 
*# The "overloading" of <code>fn</code> 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 [http://microformats.org/discuss/mail/microformats-new/2008-January/001375.html microformats-new/2008-January/001375.html].
 
*#*[[User:ManuSporny|Manu Sporny]] has propsosed that <code>"fn"</code> should be replaced with <code>"title"</code> see: [http://microformats.org/discuss/mail/microformats-new/2008-February/001468.html microformats-new/2008-February/001468.html]
 
*#*[[User:ManuSporny|Manu Sporny]] has propsosed that <code>"fn"</code> should be replaced with <code>"title"</code> see: [http://microformats.org/discuss/mail/microformats-new/2008-February/001468.html microformats-new/2008-February/001468.html]
 +
*#* [[User:WebOrganics|Martin McEvoy]] later propsosed that <code>"title"</code> should be replaced with <code>"htitle"</code> see: [http://microformats.org/discuss/mail/microformats-new/2008-August/001692.html microformats-new/2008-August/001692.html]
 
</div>
 
</div>
 
</div>
 
</div>
Line 52: Line 53:
 
<div class="description">
 
<div class="description">
 
*# [[haudio#Notes|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.
 
*# [[haudio#Notes|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.
* Typing error changed to "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 the rel-license microformat". [http://microformats.org/wiki?title=haudio&diff=0&oldid=27951]
+
*#* Typing error changed to "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 the rel-license microformat". [http://microformats.org/wiki?title=haudio&diff=0&oldid=27951]
 
</div>
 
</div>
 
</div>
 
</div>

Revision as of 14:25, 16 August 2008

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

    1. the wording about contributor could be improved to facilitate more streamlined mark-up (see above e-mail for details).
    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)
    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].
    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.
      • Typing error changed to "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 the rel-license microformat". [4]

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

related pages