[Playlist] an alternate xspf over json implementation

[Chris Anderson]

On 6/13/07, Sebastian Pipping <webmaster at hartwork.org> wrote:
> I just opened a wiki page as Ivo suggested.
> It currently holds an unfinished JSPF example file.
>
> http://wiki.xiph.org/index.php/JSPF_Draft
>

I updated the page to handle extension elements. I was surprised to
see how easy it was to handle multiple extensions from the same
application. One interesting deviation from the XML, and worth
discussing: Rather than have the extensions contain a JSON conversion
of arbitrary XML - which is the stuff that can get complicated quick -
I've got them containing arbitrary JSON.

What this means is that it will be up to each extension developer to
decide how they want to express their extensions in JSON. Should they
choose a verbose raw transform from XML, they are able to do that, but
should they choose a tighter format more native to JSON, we'll support
that as well.

To me this seems to best parallel the intentions and data model of
XSPF's extension element.

Thoughts?


-- 
Chris Anderson
http://jchris.mfdz.com