[uf-new] hAudio 1.0 Draft Release

[Scott Reynen]

On [Oct 15], Martin McEvoy wrote:

> Sigh!

Indeed.

>> The content type should certainly be made explicit when known, but  
>> making it a class name is a mistake - the type attribute should be  
>> used as above. Making it into a class takes it away from the link,  
>> so you end up with stuff like this, which is meaningless:
>>
>>    <div class="haudio">
>>      <span class="fn">Example</span>
>>      <a rel="enclosure" href="foo1">download 1</a>
>>      <span class="type">audio/ogg</span>
>>      <a rel="enclosure" href="foo2">download 2</a>
>>    </div>
> Do you ever read any of my emails? ...don't you mean....
>
>   <div class="haudio">
>     <span class="fn">Example</span>
>     <a  rel="enclosure" href="foo1" type="audio/ogg">download 1</a>
>     <a rel="enclosure" href="foo2" type="audio/ogg">download 2</a>
>   </div>


You're both saying the same thing.

> In haudio Item is not Opaque


Another imagined disagreement:

> Item
>
> [...]
>
>     * The element MUST be processed opaquely.

http://microformats.org/wiki/haudio#Item

--
Scott Reynen
MakeDataMakeSense.com