Commit 43fa3a55 authored by Evan Boehs's avatar Evan Boehs
Browse files

Begin conversion to markdown

parent e50922b5
[TOC](#rfc.toc)
Playlist Ad-Hoc Group
L. Gonze
M. Friedrich
R. Kaye
November 2006
XSPF Version 1
XML Shareable Playlist Format ("spiff")
Abstract
========
......@@ -121,6 +106,7 @@ The question for software developers is _why should I support this new XML playl
A very simple document looks like this:
```xml
<?xml version="1.0" encoding="UTF-8"?>
<playlist version="1" xmlns="http://xspf.org/ns/0/">
<trackList>
......@@ -129,9 +115,11 @@ A very simple document looks like this:
<track><location>file:///music/song\_3.mp3</location></track>
</trackList>
</playlist>
```
or this:
```xml
<?xml version="1.0" encoding="UTF-8"?>
<playlist version="1" xmlns="http://xspf.org/ns/0/">
<trackList>
......@@ -140,6 +128,7 @@ or this:
<track><location>http://example.com/song\_3.mp3</location></track>
</trackList>
</playlist>
```
* * *
......@@ -284,9 +273,11 @@ Creation date (not last-modified date) of the playlist, formatted as a [XML sche
A sample date is "2005-01-08T17:10:47-05:00". PHP to produce such a string from a unix timestamp is:
```php
$main\_date = date("Y-m-d\\TH:i:s", $timestamp);
$tz = date("O", $timestamp);
$tz = substr\_replace ($tz, ':', 3, 0);
```
In the absence of a timezone, the element MAY be assumed to use Coordinated Universal Time (UTC, sometimes called "Greenwich Mean Time").
......@@ -302,16 +293,18 @@ An ordered list of URIs. The purpose is to satisfy licenses allowing modificatio
Such a list can grow without limit, so as a practical matter we suggest deleting ancestors more than ten generations back.
```xml
<attribution>
<location>http://bar.com/modified\_version\_of\_original\_playlist.xspf</location>
<identifier>somescheme:original\_playlist.xspf</identifier>
</attribution>
```
### 4.1.1.2.11 link
The link element allows XSPF to be extended without the use of XML namespaces. xspf:playlist elements MAY contain zero or more link elements.
<link rel="http://foaf.example.org/namespace/version1">http://socialnetwork.example.org/foaf/mary.rdfs</link>
`<link rel="http://foaf.example.org/namespace/version1">http://socialnetwork.example.org/foaf/mary.rdfs</link>`
### 4.1.1.2.11.1 attributes
......@@ -327,7 +320,7 @@ URI of a resource.
The meta element allows metadata fields to be added to XSPF. xspf:playlist elements MAY contain zero or more meta elements.
<meta rel="http://example.org/key">value</meta>
`<meta rel="http://example.org/key">value</meta>`
### 4.1.1.2.12.1 attributes
......@@ -343,12 +336,14 @@ Value of the metadata element. This is plain old text, not XML, and it may not c
The extension element allows non-XSPF XML to be included in XSPF documents. The purpose is to allow nested XML, which the meta and link elements do not. xspf:playlist elements MAY contain zero or more extension elements.
```xml
<playlist version="1" xmlns="http://xspf.org/ns/0/" xmlns:cl="http://example.com">
<extension application="http://example.com">
<cl:clip start="25000" end="34500"/>
</extension>
<trackList />
</playlist>
```
### 4.1.1.2.13.1 attributes
......@@ -420,7 +415,7 @@ The time to render a resource, in milliseconds. It MUST be a valid [XML Schema n
The link element allows XSPF to be extended without the use of XML namespaces. xspf:track elements MAY contain zero or more link elements.
<link rel="http://foaf.org/namespace/version1">http://socialnetwork.org/foaf/mary.rdfs</link>
`<link rel="http://foaf.org/namespace/version1">http://socialnetwork.org/foaf/mary.rdfs</link>`
### 4.1.1.2.14.1.1.1.11.1 attributes
......@@ -452,6 +447,7 @@ Value of the metadata element. This is character data, not HTML, and it may not
The extension element allows non-XSPF XML to be included in XSPF documents. The purpose is to allow nested XML, which the meta and link elements do not. xspf:track elements MAY contain zero or more extension elements.
```xml
<playlist version="1" xmlns="http://xspf.org/ns/0/" xmlns:cl="http://example.com">
<trackList>
<track>
......@@ -461,6 +457,7 @@ The extension element allows non-XSPF XML to be included in XSPF documents. The
</track>
</trackList>
</playlist>
```
### 4.1.1.2.14.1.1.1.13.1 attributes
......@@ -506,11 +503,11 @@ The rules for determining the base URI can be be summarized as follows (highest
Generators should take extra care to ensure that relative paths are correctly encoded. Do:
<location>My%20Song.flac</location>
`<location>My%20Song.flac</location>`
Don't:
<location>My Song.flac</location>
`<location>My Song.flac</location>`
6.3 Extension URIs
------------------
......@@ -547,7 +544,7 @@ E-mail: [rob@eorbit.net](mailto:rob@eorbit.net)
Copyright and Patent Statements
===============================
Copyright © Xiph.org Foundation 2005.
Copyright © Xiph.org Foundation 2021.
The primary author of this work is [Lucas Gonze](http://gonze.com/about). He knows of no patent claims related to this work, and hereby forgoes any such claims with regard to his own contributions.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment