[uf-new] Microformat for Music Downloads

Alexandre Van de Sande alexandrevandesande at gmail.com
Mon Apr 9 10:52:38 PDT 2007


again I really do not understand the point on using hReview

If you are not putting a review about a song, you must not use
hReview, even if it has some fields that  solves your problem. It's
semantically wrong.

The semantic way to put hAtom together is if you are syndicating
reviews, or reviewing a syndication of content (a review on a blog for
example).

Of course you can syndicate audio or review music, but it's wrong to
try to fit hreview or hAtom for something totally different

On 4/9/07, Manu Sporny <msporny at digitalbazaar.com> wrote:
> Martin McEvoy wrote:
> > Marian's problem is very involved, its a bid to allow music players and
> > web players to view media info without actually having to download part
> > of the file first to read the info contained in the download.?
>
> Ahhh, this is important! The problem that you are solving is not
> Marian's problem, nor is it the one listed on music-examples, nor it is
> the one listed on music-info. It is a very small subset of all of them.
>
> That is not to say that it isn't an important problem to solve - but by
> noting that it isn't any of the prior music-related problems, the
> problem-set has been constrained greatly (which is good):
>
> As I understand it, these the fields that we are interested in?
>
> artist, title, file format
>
> If this is the case, we could easily use a combination of rel-enclosure
> (Martin's suggestion) and the title attribute to solve the problem using
> either hAtom or hReview:
>
> <a rel="enclosure" type="MIME/TYPE" title="ARTIST - TITLE"
>    href="madonna-hung_up.mp3">Hung Up</a>
>
> Then we could do the following in hAtom:
>
> <div class="hentry">
>   <h2 class="entry-title">Madonna - Hung Up</h2>
>   <abbr class="updated" title="20070401T1122-0400">Apr 1, 2007</abbr>
>   <address class="vcard author">
>     <a href="http://www.musicfreak.org/" class="url fn">MusicFreak</a>
>   </address>
>   <div class="entry-content">
>     <p>The song <a rel="enclosure" type="audio/mpeg"
>                    title="Madonna - Hung Up"
>                    href="madonna-hung_up.mp3">Hung Up</a> by
>        Madonna.</p>
>   </div>
> </div>
>
> and the following in hReview:
>
> <div class="hreview" id="hreview-Hung-Up-by-Madonna">
>   <h2 class="summary">Hung Up by Madonna</h2>
>   <abbr class="dtreviewed" title="20070401T1126-0400">Apr 1, 2007</abbr>
>   by <span class="reviewer vcard">
>     <span class="fn">anonymous</span>
>   </span>
>   <span class="type" style="display: none;">product</span>
>   <div class="item">
>     <span class="fn">Madonna - Hung Up</span>
>   </div>
>   <blockquote class="description">
>     <p>The song <a rel="enclosure" type="audio/mpeg"
>                    title="Madonna - Hung Up"
>                    href="madonna-hung_up.mp3">Hung Up</a> by
>        Madonna.</p>
>   </blockquote>
>   <span class="version" style="display: none;">0.3</span>
> </div>
>
> Does this solution work for everybody?
>
> I tend to agree with Alexandre Van de Sande and David Janes on moving
> forward with media-info as the long-term solution. As Scott stated, that
> will probably mean breaking it up into bite-sized pieces in the short
> term. Solving those smaller problems will help solve the bigger
> media-info problem in the long term.
>
> -- manu
>
> _______________________________________________
> microformats-new mailing list
> microformats-new at microformats.org
> http://microformats.org/mailman/listinfo/microformats-new
>


More information about the microformats-new mailing list