[Playlist] Re: [Icecast] How's XSPF support on Icecast if any?

[Lucas Gonze]

>> On Fri, 20 Jul 2007, Sebastian Pipping wrote:
>>> I guess we have to start testing and reviewing
>>> XSPF implementations in the wild and actively
>>> help improving them. VLC for example creates
>>> XSPF files with non-URI locations!
...
> I guess among the most important ones
> are Amarok and VLC but what comes after that?
> I guess if we make a real plan for it showing
> not only top one and two, the chance is bigger we
> get help from more people, maybe even by people
> part of that project and reading this list.
>
> Some names coming to my mind are:
> Audacious, BMPx, cmus, Juk, Kaffeine, MPD, MPlayer,
> Rhythmbox, Songbird, Totem, Xine.
>
> What else? In what order?

The Flash players could stand some work.

And what are the things we want?  Here's a start at a prioritized list:

1) Do not ever ever die if you get valid XSPF.  VLC, for example, throws 
an error on much legal XSPF.
2) Do not ever emit invalid XSPF.
3) Support X list of features in Y order
    - all formal metadata fields should be displayed
    - annotation fields should be displayed
    - images should be displayed
    - info links should be displayed
    - etc

The point of the feature list is to generally up the feature level that 
comes with XSPF.  For example, the track link and image elements are 
widely supported, and that ups the general value of a playlist.