<div dir="ltr"><div><div>Lucas,<br><br></div>I think the concept of portability is still relevant, it's just expanded beyond a file sent between individuals. If XSPF's goal was to make playlists portable between people, maybe JSPF is to make a common protocol for sharing playlists between RESTful services. Whether the .jspf is a static file or transient response shouldn't really matter to whatever application or player is consuming it.<br>
</div><div><br>- zirafa<br></div><div><br><a href="http://www.pushtape.com">www.pushtape.com</a><br><a href="http://zirafa.github.io/pushtape-player.js/">zirafa.github.io/pushtape-player.js/</a><br></div><div><br><br><div>
<br><br><br><br><br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Aug 26, 2014 at 3:42 PM, Lucas Gonze <span dir="ltr"><<a href="mailto:lucas@gonze.com" target="_blank">lucas@gonze.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>With the passage of much time since we created XSPF, I have three observations.<br><br>
</div>1. "Content resolution" was a powerful idea that has been picked up and adopted widely. <br>
<br></div>2, XML is dead. Long live JSON. Out of the formats we considered - RDF, XML and Xoxo - JSON wasn't even on the list.<br><br></div>3.
The idea of playlists as portable files that you might carry around or
repurpose has little demand. Playlists are used as transient views of
RESTful resources.<br><br><br></div>(For those on both generations of this list, you got two copies because I originally sent to the old list).<br></div>
<br>_______________________________________________<br>
Playlist mailing list<br>
<a href="mailto:Playlist@xiph.org">Playlist@xiph.org</a><br>
<a href="http://lists.xiph.org/mailman/listinfo/playlist" target="_blank">http://lists.xiph.org/mailman/listinfo/playlist</a><br>
<br></blockquote></div><br></div>