[uf-new] collection-design-pattern proposal
scott at makedatamakesense.com
Mon Apr 23 12:04:01 PDT 2007
On Apr 23, 2007, at 12:12 PM, Manu Sporny wrote:
> Scott Reynen wrote:
>> On Apr 23, 2007, at 12:12 AM, Manu Sporny wrote:
>>> <div id="ktsampler" class="haudio">
>>> <div id="ktsampler.bh" class="haudio">
>> What's wrong with this:
>> <div class="audio-album">
>> <div class="audio-track">
> Nothing really, if the problem of collections of tracks were isolated.
> What about podcasts? Symphonies? Speeches? We can't use 'audio-album'
> and 'audio-track' for those... well - we can, but the Microformat
> namespace will become incredibly bloated as we try to re-create the
> concept of a collection/relationship for each uF format.
I don't know about those. The only documentation of those types of
collections I see in the wiki is media-info, and that's full of many
examples that have nothing to do with collections. If you want to
solve the specific problem of collections, I'd encourage you to first
document the specific problem of collections. Right now, it doesn't
seem to me it's a problem we can solve generally, rather than in
specific contexts, but I'm just speculating about abstract concepts.
That's not how successful microformats develop, and I think we should
follow the process here, e.g. first documentation, then analysis,
>> It seems to me a collection pattern is solving a problem we could
>> better by using more specific class names. In this case, tracks and
>> albums are two different things, so they should have two different
>> names. Albums contain tracks by definition, so no need for
>> semantics here, right?
> You are correct for the specific case of albums and tracks. However,
> we're going to keep seeing this problem crop up. Video is next and it
> has the exact same 'collection' problem that audio does. The same goes
> for images (photo albums, collages, etc.)
Again, I'd encourage you to make a page in the wiki with real-world
collection-examples of all of those together, if only to save
yourself the trouble of explaining the scope of the problem you're
trying to solve via email again and again.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the microformats-new