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

[Thomas B. Ruecker]

Sebastian Pipping wrote:
> Thomas B. Ruecker wrote:
>   
>> Ivo Emanuel Gonçalves wrote:
>>     
>>> On 5/15/07, Thomas B. Ruecker <ruecker at ruecker-itk.de> wrote:
>>>       
>>>> I've built a first version of a xslt that produces xspf output.
>>>> You can find it here:
>>>> http://www.ruecker-itk.de/icecast/xspf/
>>>> stats.xml - raw xml metadata for the whole server at some point in time
>>>> xspf.xsl - the xslt sheet
>>>> xspf.xsl.out - the output as produced by the server
>>>>         
>
> ---------------------------------------------------------------------
> Nice! One thing unclear to me is why the location tags
> in <xspf.xsl.out> are empty? Also shouldn't it be
> extracted from <listenurl> instead of the mount attribute?
> Extra problem is, that empty location tags are not allowed
> in XSPF so they would have to be omitted then.
> ---------------------------------------------------------------------
>
>   
whoops, looks like I've overlooked an obvious bug. :-/
Funny though I think the xspf validator did not complain.
Will fix that later tonight.
>> I'd be grateful for some hints about what to do to the metadata that
>> ended up in <annotation>.
>>     
>
> ---------------------------------------------------------------------
> You mean losing the structure inside the annotation tag?
> You could in addition create an extension, that holds
> the same elements that the icecast stats do.
> What I have in mind looks like this:
>
>    <track>
>      <extension application="your_URI_here">
>        <server_description>copied over</server_description>
>        <server_name>copied over</server_name>
>        [..]
>      </extension>
>    </track>
>
> That way you can have best of both worlds: Informative
> <annotation> and preservation of the old structure.
>   
So is <annotation> in fact the right place to store that multiline
plaintext content? (do I need to put some sort of linebreak chars? for
now i've just forced CR LF)
> In case you like the extension idea let us know if
> you need help defining it.
>   
yes, I guess that's the way to go then. help would be greatly appreciated.
IIRC there is also <meta> elements in the spec. What about those?

Also what happens from the player application point of view?
Or is xspf still being adopted so that such additions would encourage
application developers to add support for those?

Cheers

Thomas