[Playlist] an alternate xspf over json implementation

[Sebastian Pipping]

Chris Anderson wrote:
> 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 disagree here. I think we should cover the full XSPF
feature spectrum and try to make that look best.
-----------------------------------------------------------



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

-----------------------------------------------------------
The article on XML.com was quite interesting.
The "element order doesn't matter" thing hits our
attribution element. I currently think of something
like this as a possible solution:

  "attribution" : {
    "1" : {
      "type" : "identifier",
      "uri" : "http://www.example.com/"
    },
    "2" : {
      "type" : "location",
      "uri" : "http://www.example.com/"
    }
  }

The other elements should not cause any trouble
since their order is arbitrary.
-----------------------------------------------------------



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

-----------------------------------------------------------
While I have no objections to such an order, I don't
think we should leave any feature out. I don't want
people saying "no, the JSON edition cannot do that"
in the future. Let's create a sibling, not a child of XSPF.



Sebastian