[Playlist] an alternate xspf over json implementation

[Chris Anderson]

I've been a little quiet on the front lately - the Grabb.it launch has
been all-consuming.

It seems to me that the principle challenge and constraint in defining
JSPF will be ensuring readability. If we consider JSPF to be the
gateway drug into using XSPF for more demanding applications, then
we'll have to work hard to design a format that is useful, readable,
and appealing.

While lossless XML -> JSON conversion is possible, the results look
more like a meditation on the capabilities of XML, than like a
convenient serialization of the salient aspects of the data being
modeled. [1]

I did a google-dive to find some of the articles I'd been reading when
originally working on JSPF, and tagged the best. [2]

Because we have the luxury of working with the XSPF data model, we
don't have to follow a general purpose conversion, except insofar as
XSPF allows arbitrary XML to be included.

How to proceed? Perhaps we should figure out what the "core" data
fields are of XSPF (perhaps those elements without attributes), and
build the basic JSPF format from them (some intersection of Fabricio's
and my work probably hits this sweet spot). Once we have these "core"
fields worked out, we can start to add the richer fields.

[1] http://www.xml.com/pub/a/2006/05/31/converting-between-xml-and-json.html
[2] http://del.icio.us/jchris/json

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