XiphWiki - User contributions [en]

XSPF Examples in the wild

2007-12-21T19:08:00Z

Jchris: note on xml embedding format

This page contains examples of XSPF as found in the wild on playlisting websites and services. Please keep new examples in alphabetical order when adding them, so we can cut down on duplicates. Please use code and pre tags around your examples to avoid nasty surprises in less-capable browsers.

== ccMixter ==

Example XSPF:

<code><pre>
<?xml version="1.0" encoding="UTF-8"?>
<playlist xmlns="http://xspf.org/ns/0/" version="1">
<title>ccMixter</title>
<creator>http://ccmixter.org/</creator>
<annotation>Download, Sample, Cut-up, Share.</annotation>
<info>Download, Sample, Cut-up, Share.</info>
<location>http://ccmixter.org/media/api/query?f=xspf</location>
<date>Sat, 05 May 2007 14:04:44 CDT</date>
<trackList>
<track>
<location>http://ccmixter.org/people/FFGreen/FFGreen_-_Baltimore_Dreaming_(FF_remix).mp3</location>
<identifier>10165</identifier>
<title>Baltimore Dreaming (FF remix)</title>
<creator>FFGreen</creator>
<duration>2976018</duration>
<meta rel="http://creativecommons.org/licenses/by-nc/2.5/">http://creativecommons.org/licenses/by-nc/2.5/</meta>
<image>http://ccmixter.org/avatars/FF-old-ccmixterpic.jpg</image>
</track>
</trackList>
</playlist>
</pre></code>

Commentary:

There is not yet consensus on how to markup Creative Commons licensed music in XSPF. There was a proposal to use http://xspf.org/rel/license/v1 as rel attribute for the link tag when the link url specifies a license document. The ccMixter XSPF predates that proposal and uses the meta tag rather then the rel tag. The confusion on this issue is holding back license-aware user agents and aggregators.

== SeeqPod ==

See the [http://www.seeqpod.com/api/ SeeqPod documentation] here.

Example XSPF:

<code><pre>
<?xml version='1.0' encoding='UTF-8' ?>
<playlist version="1" xmlns="http://xspf.org/ns/0/" start="0" end="0"
total="26" prev="None" next="1">
<title></title>
<trackList>
<track>
<location>http://joniverse.com/resources/music/u2-one.mp3</location>
<title>One</title>
<creator>U2</creator>
<extension application="seeqpod_metadata">
<mp3_url_id>19646033</mp3_url_id>
<has_music_rex>True</has_music_rex>
<song_id>39445</song_id>
</extension>
</track>
</trackList>
</playlist>
</pre></code>

Commentary (from Lucas on the [http://lists.musicbrainz.org/pipermail/playlist/2007-December/001914.html Playlist mailing list]):

First off, let's move the attributes in the root element to a namespace:

<code><pre>
<playlist version="1" xmlns="http://xspf.org/ns/0/"
xmlns:pg="http://xspf.org/ns/pagination"
pg:start="0" pg:end="0" pg:total="26" pg:prev="None" pg:next="1" />
</pre></code>

(I don't know what all those values are, by the way. But I do think it
would be great to do a pagination API, maybe based on Mark Nottingham's
feed history RFC for Atom, and I am confident that this belongs in a
namespace.)

Second, let's move that song_id up a level, so that other apps can use
it too:

<code><pre>
<track>
<location>http://joniverse.com/resources/music/u2-one.mp3</location>
<title>One</title>
<creator>U2</creator>
<identifier>http://seeqpod.com/song_id/39445<identifier>
<extension application="seeqpod_metadata">
<mp3_url_id>19646033</mp3_url_id>
<has_music_rex>True</has_music_rex>
</extension>
</track>
</pre></code>

About the construction of the extension element here, I'm really happy
to see somebody using that element well. Given how unclear the spec is
on the topic it's rare to see that. You might argue that this stuff
needs to be namespaced, but I honestly don't know if that's true. I
would just say that anything within an extension element is not XSPF.

The one correction I'd make to this extension element is to change the
"application" attribute to a URI:

<code><pre>
<extension application="http://seeqpod.com/seeqpod_metadata">
</pre></code>

XSPF Examples in the wild

2007-12-21T19:06:36Z

Jchris: add ccMixter and small license rel rant

This page contains examples of XSPF as found in the wild on playlisting websites and services. Please keep new examples in alphabetical order when adding them, so we can cut down on duplicates.

== ccMixter ==

Example XSPF:

<code><pre>
<?xml version="1.0" encoding="UTF-8"?>
<playlist xmlns="http://xspf.org/ns/0/" version="1">
<title>ccMixter</title>
<creator>http://ccmixter.org/</creator>
<annotation>Download, Sample, Cut-up, Share.</annotation>
<info>Download, Sample, Cut-up, Share.</info>
<location>http://ccmixter.org/media/api/query?f=xspf</location>
<date>Sat, 05 May 2007 14:04:44 CDT</date>
<trackList>
<track>
<location>http://ccmixter.org/people/FFGreen/FFGreen_-_Baltimore_Dreaming_(FF_remix).mp3</location>
<identifier>10165</identifier>
<title>Baltimore Dreaming (FF remix)</title>
<creator>FFGreen</creator>
<duration>2976018</duration>
<meta rel="http://creativecommons.org/licenses/by-nc/2.5/">http://creativecommons.org/licenses/by-nc/2.5/</meta>
<image>http://ccmixter.org/avatars/FF-old-ccmixterpic.jpg</image>
</track>
</trackList>
</playlist>
</pre></code>

Commentary:

There is not yet consensus on how to markup Creative Commons licensed music in XSPF. There was a proposal to use http://xspf.org/rel/license/v1 as rel attribute for the link tag when the link url specifies a license document. The ccMixter XSPF predates that proposal and uses the meta tag rather then the rel tag. The confusion on this issue is holding back license-aware user agents and aggregators.

== SeeqPod ==

See the [http://www.seeqpod.com/api/ SeeqPod documentation] here.

Example XSPF:

<code><pre>
<?xml version='1.0' encoding='UTF-8' ?>
<playlist version="1" xmlns="http://xspf.org/ns/0/" start="0" end="0"
total="26" prev="None" next="1">
<title></title>
<trackList>
<track>
<location>http://joniverse.com/resources/music/u2-one.mp3</location>
<title>One</title>
<creator>U2</creator>
<extension application="seeqpod_metadata">
<mp3_url_id>19646033</mp3_url_id>
<has_music_rex>True</has_music_rex>
<song_id>39445</song_id>
</extension>
</track>
</trackList>
</playlist>
</pre></code>

Commentary (from Lucas on the [http://lists.musicbrainz.org/pipermail/playlist/2007-December/001914.html Playlist mailing list]):

First off, let's move the attributes in the root element to a namespace:

<code><pre>
<playlist version="1" xmlns="http://xspf.org/ns/0/"
xmlns:pg="http://xspf.org/ns/pagination"
pg:start="0" pg:end="0" pg:total="26" pg:prev="None" pg:next="1" />
</pre></code>

(I don't know what all those values are, by the way. But I do think it
would be great to do a pagination API, maybe based on Mark Nottingham's
feed history RFC for Atom, and I am confident that this belongs in a
namespace.)

Second, let's move that song_id up a level, so that other apps can use
it too:

<code><pre>
<track>
<location>http://joniverse.com/resources/music/u2-one.mp3</location>
<title>One</title>
<creator>U2</creator>
<identifier>http://seeqpod.com/song_id/39445<identifier>
<extension application="seeqpod_metadata">
<mp3_url_id>19646033</mp3_url_id>
<has_music_rex>True</has_music_rex>
</extension>
</track>
</pre></code>

About the construction of the extension element here, I'm really happy
to see somebody using that element well. Given how unclear the spec is
on the topic it's rare to see that. You might argue that this stuff
needs to be namespaced, but I honestly don't know if that's true. I
would just say that anything within an extension element is not XSPF.

The one correction I'd make to this extension element is to change the
"application" attribute to a URI:

<code><pre>
<extension application="http://seeqpod.com/seeqpod_metadata">
</pre></code>

XSPF Examples in the wild

2007-12-21T18:56:05Z

Jchris: Initial version of the xspf examples page

This page contains examples of XSPF as found in the wild on playlisting websites and services. Please keep new examples in alphabetical order when adding them, so we can cut down on duplicates.

== SeeqPod ==

See the [http://www.seeqpod.com/api/ SeeqPod documentation] here.

Example XSPF:

<?xml version='1.0' encoding='UTF-8' ?>
<playlist version="1" xmlns="http://xspf.org/ns/0/" start="0" end="0"
total="26" prev="None" next="1">
<title></title>
<trackList>
<track>
<location>http://joniverse.com/resources/music/u2-one.mp3</location>
<title>One</title>
<creator>U2</creator>
<extension application="seeqpod_metadata">
<mp3_url_id>19646033</mp3_url_id>
<has_music_rex>True</has_music_rex>
<song_id>39445</song_id>
</extension>
</track>
</trackList>
</playlist>

Commentary (from Lucas on the [http://lists.musicbrainz.org/pipermail/playlist/2007-December/001914.html Playlist mailing list]):

First off, let's move the attributes in the root element to a namespace:

<playlist version="1" xmlns="http://xspf.org/ns/0/"
xmlns:pg="http://xspf.org/ns/pagination"
pg:start="0" pg:end="0" pg:total="26" pg:prev="None" pg:next="1" />

(I don't know what all those values are, by the way. But I do think it
would be great to do a pagination API, maybe based on Mark Nottingham's
feed history RFC for Atom, and I am confident that this belongs in a
namespace.)

Second, let's move that song_id up a level, so that other apps can use
it too:

<track>
<location>http://joniverse.com/resources/music/u2-one.mp3</location>
<title>One</title>
<creator>U2</creator>
<identifier>http://seeqpod.com/song_id/39445<identifier>
<extension application="seeqpod_metadata">
<mp3_url_id>19646033</mp3_url_id>
<has_music_rex>True</has_music_rex>
</extension>
</track>

About the construction of the extension element here, I'm really happy
to see somebody using that element well. Given how unclear the spec is
on the topic it's rare to see that. You might argue that this stuff
needs to be namespaced, but I honestly don't know if that's true. I
would just say that anything within an extension element is not XSPF.

The one correction I'd make to this extension element is to change the
"application" attribute to a URI:

<extension application="http://seeqpod.com/seeqpod_metadata">

XSPF

2007-12-21T18:36:56Z

Jchris: /* See also */ added link to examples page

'''XML Shareable Playlist Format''' ('''XSPF'''), pronounced "spiff", is a next-generation [http://en.wikipedia.org/wiki/playlist playlist] format for digital media such as songs in Vorbis or MP3 format. This wiki is for developers.

The mime type for XSPF playlists is <tt>application/xspf+xml</tt>.

== Supporting applications ==

These are applications which support XSPF and have not yet been added to the [[http://xspf.org/applications][main applications list]].

* [http://www.jamendo.com/ Jamendo]
** You have to be a member and to select "XSPF" in your preferences to use them by default, but you can look and test a sample playlist here: http://www.jamendo.com/get/track/id/album/audio/xspf/1003/?aue=ogg2
* http://www.ArtistServer.com
** on artist profile pages http://www.artistserver.com/bliss
** on stations and playlists http://www.artistserver.com/stations/
** on genre pages http://www.artistserver.com/DownTempo
* Project Opus http://projectopus.com
** see http://www.projectopus.com/new-player for details
** includes modified version of Fabricio's player

"We added: A Scrubber/Shuttle so the lister can move the playhead to any point along the song. Time Remaining, Elapsed Time Played, Genre of Song, Origin/Location (city) of artist. Site specific stuff which my not be of interest to others is: Review song link: we were adding as a layer to the player but, it got too large and ugly. Buy song link. And a bunch of nice styling/skin tweaks."

* trend of XSLT for xspf to html example
** http://dokerlund.edhsweb.org/wordpress/archives/23 is announce
** http://dokerlund.edhsweb.org/wordpress/xspf/media/playlist.xml is in practice
* Zuardi player modified to support FLV and SWF as well as mp3: http://blitz-xplore.blogspot.com/2006/05/file-xspfplayer.html

== See also ==

* [[XSPF FAQ]]
* [[XSPF v1 Notes and Errata]]
* [[XSPF Conformance Tests]]
* [[XSPF Wish List]]
* [[XSPF Examples in the wild]]
* [[List of known XSPF extensions]]
* [[List of known XSPF metas]]
* [[JSPF Draft|JSPF]] (''JSON Sharable Playlist Format'' a.k.a. ''XSPF on JSON'')

== External links ==

* [http://xspf.org/xspf-v1.html XSPF specification]
* [http://validator.xspf.org/ Online XSPF Validator]
* [https://trac.xiph.org/browser/websites/xspf.org/images/banners "Valid XSPF" button]
* [https://trac.xiph.org/browser/trunk/xspf/ Source control for source code, spec, XSLT, validation]
* [https://trac.xiph.org/browser/websites/xspf.org/ Source control for XSPF.org website]
* [http://downloads.xiph.org/releases/xspf/ XSPF-related releases]
* [http://gonze.com/playlists/playlist-format-survey.html A survey of playlist formats], by Lucas Gonze
* [http://en.wikipedia.org/wiki/XSPF XSPF Reference page on Wikipedia]
* [http://web.archive.org/web/20060410160006/http://playlist.musicbrainz.org/playlist/moin.cgi/ Old XSPF wiki]

JSPF Draft

2007-07-30T22:35:02Z

Jchris: added .ogg and .mp3 to track location examples

This is the JSPF specification workspace.

Example JSPF file:
{
"playlist" : {
"title" : "JSPF example",
"creator" : "Artist name",
"annotation" : "Super playlist",
"info" : "http://example.com/",
"location" : "http://example.com/",
"identifier" : "http://example.com/",
"image" : "http://example.com/",
"date" : "2005-01-08T17:10:47-05:00",
"license" : "http://example.com/",
"attribution" : [
{"identifier" : "http://example.com/"},
{"location" : "http://example.com/"}
],
"link" : [
{"http://example.com/rel/1/" : "http://example.com/body/1/"},
{"http://example.com/rel/2/" : "http://example.com/body/2/"}
],
"meta" : [
{"http://example.com/rel/1/" : "my meta 14"},
{"http://example.com/rel/2/" : "345"}
],
"extension" : {
"http://example.com/app/1/" : [ARBITRARY_EXTENSION_BODY, ARBITRARY_EXTENSION_BODY],
"http://example.com/app/2/" : [ARBITRARY_EXTENSION_BODY]
},
"track" : [
{
"location" : ["http://example.com/1.ogg", "http://example.com/2.mp3"],
"identifier" : ["http://example.com/1/", "http://example.com/2/"],
"title" : "Track title",
"creator" : "Artist name",
"annotation" : "Some text",
"info" : "http://example.com/",
"image" : "http://example.com/",
"album" : "Album name",
"trackNum" : 1,
"duration" : 0,
"link" : [
{"http://example.com/rel/1/" : "http://example.com/body/1/"},
{"http://example.com/rel/2/" : "http://example.com/body/2/"}
],
"meta" : [
{"http://example.com/rel/1/" : "my meta 14"},
{"http://example.com/rel/2/" : "345"}
],
"extension" : {
"http://example.com/app/1/" : [ARBITRARY_EXTENSION_BODY, ARBITRARY_EXTENSION_BODY],
"http://example.com/app/2/" : [ARBITRARY_EXTENSION_BODY]
}
}
]
}
}

JSPF Draft

2007-06-15T03:57:17Z

Jchris: trying a simpler syntax for location and identifier

This is the JSPF specification workspace.

Example JSPF file:
{
"playlist" : {
"title" : "JSPF example",
"creator" : "Artist name",
"annotation" : "Super playlist",
"info" : "http://example.com/",
"location" : "http://example.com/",
"identifier" : "http://example.com/",
"image" : "http://example.com/",
"date" : "2005-01-08T17:10:47-05:00",
"license" : "http://example.com/",
"attribution" : [
{"identifier" : "http://example.com/"},
{"location" : "http://example.com/"}
],
"link" : [
{"http://example.com/rel/1/" : "http://example.com/body/1/"},
{"http://example.com/rel/2/" : "http://example.com/body/2/"}
],
"meta" : [
{"http://example.com/rel/1/" : "my meta 14"},
{"http://example.com/rel/2/" : "345"}
],
"extension" : {
"http://example.com/app/1/" : [ARBITRARY_EXTENSION_BODY, ARBITRARY_EXTENSION_BODY],
"http://example.com/app/2/" : [ARBITRARY_EXTENSION_BODY]
},
"track" : [
{
"location" : ["http://example.com/1/", "http://example.com/2/"],
"identifier" : ["http://example.com/1/", "http://example.com/2/"],
"title" : "Track title",
"creator" : "Artist name",
"annotation" : "Some text",
"info" : "http://example.com/",
"image" : "http://example.com/",
"album" : "Album name",
"trackNum" : 1,
"duration" : 0,
"link" : [
{"http://example.com/rel/1/" : "http://example.com/body/1/"},
{"http://example.com/rel/2/" : "http://example.com/body/2/"}
],
"meta" : [
{"http://example.com/rel/1/" : "my meta 14"},
{"http://example.com/rel/2/" : "345"}
],
"extension" : {
"http://example.com/app/1/" : [ARBITRARY_EXTENSION_BODY, ARBITRARY_EXTENSION_BODY],
"http://example.com/app/2/" : [ARBITRARY_EXTENSION_BODY]
}
}
]
}
}

JSPF Draft

2007-06-13T20:37:00Z

Jchris: added an example of the extension element