XSPF and metadata

I should say that XSPF is a lot more like RSS than anything else. It's a
container for metadata about a set of media objects. Using that metadata
you can construct any and all of HTML, RSS, M3U, SMIL, or Soundblox. As
an example, I created XSLT to perform those conversions — see
http://gonze.com/weblog/story/6-11-4 for details.

For example, these:
http://gonze.com/xspf/organism.smil
http://gonze.com/xspf/organism.html

Both come from this:
http://gonze.com/xspf/organism.xspf

– Lucas

On Mon, 28 Jun 2004, Andreas Haugstrup wrote:

> On Mon, 28 Jun 2004 15:16:18 -0000, petertheman <peter@…>
> wrote:
>
> >> So keep the world wide web alive by linking to the HTML page and
> > not
> >> the video file. It is only fair to the author.
> >
> > But then you're saying we can't do playlists (as in SMIL playlists in
> > a player)… Which would be too bad because the videowatching
> > experience in a playlist is very different from clicking around from
> > site to site… I'm not sure what the solution is…
>
> That would depend (this is still my personal opinion of course). The way
> it is now I wouldn't like SMIL playlists at all for the simple reason that
> there isn't any metadata at all. I'll have to read more about SMIL to find
> out what kind of metadata can be added. Lucas' XSPF format looks alright
> when it comes to metadata (after a first read). Without metadata I don't
> feel it's the same work.
>
> With metadata it's different. Thank you Ryan for making me think more
> about metadata instead of just dismissing it like I did at first. With
> metadata I can make the same information available in the video file
> (SMIL, XSPF etc.) itself. Essentially it'd be like making an RSS feed
> (same content different audience).
> Actually it would be very nice that way since I would be able to have the
> video file on it's own and then pull the metadata from that file (very
> easy since it'd be XML) to display the blog entry. Pretty clever actually.
> I must remember to experiment with that. Actually with windows media and
> quicktime browser plugins it would be dead easy to make a player in the
> web browser. I'm a big fan of keeping things in the web browser – it's a
> good way to make it easily accessible to newcomers. There's no learning
> curve. :o)
>
> I'm a big fan of the Danish copyright law's section on "personal use".
> Basically you can do almost anything with a work as long as it's for
> personal use (in your own home, things like that). I encourage personal
> use always because it's a great way to learn from others. What I wouldn't
> like is a for-profit webjay like service where a company makes money on
> distributing my work. In that case you bet I want to be paid.
>
> If it's a non-profit organization that makes access to works easy then by
> definition I'm for it (still, I need metadata in the files themselves and
> I need that metadata readily accessible to the viewer). However I might
> not be able to afford to support such a service with my bandwidth. In much
> the same way I would love to give $100 each month to Amnesty. :o)
>
> But with good metadata included in the video files themselves I can
> stretch pretty far (unless someone is making money off my work). I'll add
> a couple of notes about metadata in an e-mail about XSPF.
>
> – Andreas
> —
> Personal: <http://www.solitude.dk>
> File Thingie – PHP File Manager <http://www.solitude.dk/filethingie/>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>