[Playlist] an alternate xspf over json implementation

[Sebastian Pipping]

Chris Anderson wrote:
> On 6/13/07, Sebastian Pipping <webmaster at hartwork.org> wrote:
>> My idea is we finish the example and then
>> derive the spec from it. This way we all know
>> what it looks like before we go to the dirty
>> spec work.
> 
> I had floated the idea of creating a reference parser in Javascript
> that turns valid XSPF into valid JSPF. We can still go that route, as
> well. I've been having a little trouble getting my existing parser to
> work on IE 6, so I haven't checked it into the repository yet.

---------------------------------------------
A reference converter would be nice.
I think we should finish the format
before coding though so no code has to
b thrown away and written again.
---------------------------------------------



> I'm not sure how one would spec a JSON format. I'm sure it can be done
> - but some of the key differences from XML are that a JSON format
> ought to allow arbitrary keys to be added to the document, as long as
> the required keys are present and any keys that are part of the spec
> are valid.

---------------------------------------------
This conflicts to the extension concept
of XSPF. While I'm not sure which concept
is better, I think we should try to
make the semantics of JSPF as close to
that of XSPF to be able to convert from
JSPF to XSPF without problems.



Sebastian