[Playlist] an alternate xspf over json implementation

[Sebastian Pipping]

Chris Anderson wrote:
>>   "attribution" : {
>>     "1" : {
>>       "type" : "identifier",
>>       "uri" : "http://www.example.com/"
>>     },
>>     "2" : {
>>       "type" : "location",
>>       "uri" : "http://www.example.com/"
>>     }
>>   }
> 
> Here's another way to do it, preserving order:
> {
>  "attribution" : [
>    {"identifier":"http://www.example.com/"},
>    {"location":"http://www.example.com/"}
>  ]
> }

-------------------------------------------------------
That's nice and simple.
-------------------------------------------------------



>> 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.
> 
> I agree with the goal - I'd just put readability ahead of feature
> parity on the priorities list. It's probably good that we're coming
> from different angles on this, hopefully we'll get a complete and
> readable format!

-------------------------------------------------------
Sounds good!

One more thing: I've seen key names with quotes
and without quotes: is both legal?
What I mean is

  {
    "playlist" : { .. }
  }

versus

  {
    playlist : { .. }
  }

I have searched the RFC but cannot find the place
defining this valid. Did I overlook it?



Sebastian