[Playlist] an alternate xspf over json implementation

[Sebastian Pipping]

Chris Anderson wrote:
> 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.

--------------------------------------------------------------
With mixed extension types we lose the extension order this
way, right? Is that order important to preserve?
--------------------------------------------------------------



> 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.

--------------------------------------------------------------
You mean an auto conversion for an extension from XML to JSON
will work but maybe look bad but extension authors can
define a better JSON edition as well?



Sebastian