[Playlist] an alternate xspf over json implementation

[Sebastian Pipping]

Sorry for not coming to this earlier, but I guess we still
have to define an official JSPF format. From what I have
seen here

   http://jchris.mfdz.com/jspf/xspf_parser_spec.html

and here

   http://cchits.ning.com/recent/?fmt=json&var=cchitsPlaylist

both formats are good work but do not seem fully XSPF compatible
to me, thinking of several extension "instances" with the very
same URI for example. (Does JSON allow key overloading?)

To not end up in interoperability hell I suggest we come
together again and create *the* JSON derivate of XSPF.
Who's with me?



Sebastian