On Jun 4, 2007, at 6:33 PM, Joe Andrieu wrote:
The alternative to the above that I thought you were going for was
something like this:
halbum
playlist/XOXO
haudio
haudio
haudio
haudio
That makes sense to me.
But then in your example, you did something like this:
halbum
haudio
playlist/XOXO
track
haudio
track
haudio
track
haudio
That was definitely confusing.
I was also confused by that. I spent a while trying to figure out
what exactly class="haudio" would mean in this schema, and it looks
like haudio has an incredibly generic meaning along the lines of
"information about some type of audio" where both albums and tracks
are potential types of audio. I think that's far too general to be
useful. The container and item labels should be specific enough to
make that unnecessary. If we can't assume class="halbum" refers to
audio, I think it's a poor class name and another name should be
chosen that clearly indicates the content relates to audio without
any need for additional labels like "haudio."
--
Scott Reynen
MakeDataMakeSense.com
_______________________________________________
microformats-new mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-new
