This page is intended as a list of [[XSPF]] extensions used in the wild. The goal is to have precise and up to date information which we will need your help with! The more complete this list is the more likely is the future support of a specific extension in more then just one piece of software.

+

This page is intended as a list of [[XSPF]] extensions used in the wild. The goal is to list precise and up to date information which we will need your help with! Information given '''must be understandable''' and (at best) '''should be precise enough to be implementable'''. The more complete this list is the more likely is the future support of a specific extension in more than just one piece of software.

This extension stores additional information about the track's location based on data retrieved from [http://freedesktop.org/Software/HAL HAL].

+

+

The goal is to store information about the locality of a track independent of a mount point (on UNIX-like systems).

+

+

====<volume-udi>====

+

This is a unique identifier for a "volume" (harddisk partition, other kinds of partitions, anything that can be mounted onto a directory).

+

+

====<device-udi>====

+

This is a unique identifier for a device, on which the volume specified by volume-udi resides.

+

+

Both of these identifiers can be obtained from HAL for almost all kinds and types of storage media and partitions/volumes.

+

+

====<volume-relative-path>====

+

This is the path of/to the track, and starts from (and excluding of) the root directory of the named volume.

+

+

This way the location of a track is first identified by the volume-udi and device-udi, from which the '''current''' mount point of a volume (partition, etc.) can be identified,

+

to which the volume-relative path is appended to finally obtain the fully qualified path to the track.

= Project Opus =

= Project Opus =

Line 109:

Line 153:

= YOUR EXTENSION HERE =

= YOUR EXTENSION HERE =

Yes, please.

Yes, please.

+

+

= See also =

+

* [[List of known XSPF metas]]

+

+

[[Category:XSPF]]

Latest revision as of 04:07, 14 November 2012

This page is intended as a list of XSPF extensions used in the wild. The goal is to list precise and up to date information which we will need your help with! Information given must be understandable and (at best) should be precise enough to be implementable. The more complete this list is the more likely is the future support of a specific extension in more than just one piece of software.

Definition

This extension stores additional information about the track's location based on data retrieved from HAL.

The goal is to store information about the locality of a track independent of a mount point (on UNIX-like systems).

<volume-udi>

This is a unique identifier for a "volume" (harddisk partition, other kinds of partitions, anything that can be mounted onto a directory).

<device-udi>

This is a unique identifier for a device, on which the volume specified by volume-udi resides.

Both of these identifiers can be obtained from HAL for almost all kinds and types of storage media and partitions/volumes.

<volume-relative-path>

This is the path of/to the track, and starts from (and excluding of) the root directory of the named volume.

This way the location of a track is first identified by the volume-udi and device-udi, from which the current mount point of a volume (partition, etc.) can be identified,
to which the volume-relative path is appended to finally obtain the fully qualified path to the track.

Playlist / Album

Example

Definition

The <po:info> element contains high level details about a playlist. The "type" attribute refers to the type of playlist being loaded - either an actual playlist, or an album. The "nid" (integer) is the internal ID of the playlist/album within Project Opus.

Definition

<po:clip>

This element contains playback information for the player(s). Right now there is just one integer for track "length" (in milliseconds).

<po:region>

The region element is used to display the locale of the given artist. Right now, the content of this element is the link to a region portal on Project Opus, while the "name" attribute is the actual name of the city or region.

<po:tags>

Tags describe content on Project Opus in a similar manner as what is found on most tag enabled sites. Each tag has an internal ID in the "tid" attribute, while the "size" (integer) is used to govern the size of the tag in a tag cloud, also found in the player. The content of each tag element is the tag text itself.

<po:genre>

Similar to the region element, the genre element is used to display the genre of the given song. Again, the content of this element is the link to a genre portal on Project Opus, while the "name" attribute is the actual name of the genre.

<po:uid>

This element contains the user ID (an integer) of the content publisher.

<po:nid>

This element contains the node ID (an integer) of a track.

<po:num_listens>

The content of this element is the number of times the track has been listened to.

<po:license>

The license element only contains a "type" attribute, which indicates the type of license the song has. A value of "po" means the song is for sale on Project Opus. The other possible values are based on the song being free for download, and licensed through the Creative Commons. Possible CC values are as follows: