[microformats-discuss] Video Pop-up Link Maker

[Joshua Kinberg]

> An enclosure is an enclosure.
>
> It can stand on its own, by itself. It can also be a part of a larger
> construct (a vlog- or pod-post, for example).
>
> So, instead of making rel-enclosure bigger (to handle a specific use
> case), it should remain as it is- small, simple and solving a
> discrete problem. Then, a vlog format, a podcast format and an app-
> cast format can all make use of it (by composition, ie embedding it).

What I've proposed is a set of optional and general extensions:

- fully exploit XHTML by including *optional* Title and Type
attributes within relEnclosure links
- an *optional* class="enclosure" block to handle the use case of
multiple instances of the same enclosure (a valid point brought up on
the Wiki page for relEnclosure). This could be the same document in
PDF, DOC, or TXT for example, so it is not specific to podcasting or
videoblogging, but is geared toward a practical and general use case
for multiple enclosures.

Neither of these change the core of relEnclosure which remains
simple... it just makes slightly more advanced uses for the
Microformat *possible*.

As for the optional <img> element... you might argue that may be too
videoblogging or podcasting specific, but I would disagree. There
could be many instances where someone might wish to show an image
representation of the enclosure regardless of whether the enclosure is
a media file. Besides, if the element is optional I don't see how it
makes relEnclosure that much different. This is really just exploiting
what's available in XHTML, i.e. image links.

-Josh


On 10/14/05, Ryan King <ryan at technorati.com> wrote:
> On Oct 14, 2005, at 3:50 PM, Joshua Kinberg wrote:
>
> >> Actually, I think instead of adding to rel-enclosure, a new format is
> >> in order.
> >
> > Please explain further...
>
> An enclosure is an enclosure.
>
> It can stand on its own, by itself. It can also be a part of a larger
> construct (a vlog- or pod-post, for example).
>
> So, instead of making rel-enclosure bigger (to handle a specific use
> case), it should remain as it is- small, simple and solving a
> discrete problem. Then, a vlog format, a podcast format and an app-
> cast format can all make use of it (by composition, ie embedding it).
>
> -ryan
> _______________________________________________
> microformats-discuss mailing list
> microformats-discuss at microformats.org
> http://microformats.org/mailman/listinfo/microformats-discuss
>
>