TOC 
Network Working GroupL. Gonze
Internet-DraftYahoo! Music
Intended status: InformationalSeptember 23, 2006
Expires: March 27, 2007 


The application/xspf+xml Media Type
draft-gonze-media-type-xspf-01

Status of this Memo

By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work in progress.”

The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt.

The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html.

This Internet-Draft will expire on March 27, 2007.

Copyright Notice

Copyright © The Internet Society (2006).

Abstract

This document defines a new media type for the XML Shareable Playlist Format (XSPF, pronounced like "spiff"). XSPF allows playlists to be exchanged between different software, across networks and across administrative boundaries. A media type registration enhances shareability.

An XSPF playlist describes a sequence of objects to be rendered in time. Objects might be audio, video, text, playlists, or any other media type with an inherent duration. The function of an XSPF document is to identify the objects and communicate their order.



Table of Contents

1.  Requirements notation
2.  Registration
3.  Security considerations
4.  Normative References
§  Author's Address
§  Intellectual Property and Copyright Statements




 TOC 

1.  Requirements notation

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119] (Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.).



 TOC 

2.  Registration

Type name:
application
Subtype name:
xspf+xml
Required parameters:
none
Optional parameters:
charset. Same as charset parameter of application/xml as specified in [RFC3023] (Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.).
Encoding considerations:
Same as encoding considerations of application/xml as specified in [RFC3023] (Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.).
Interoperability considerations:
Versions 0 and 1 are compatible except for some playlist publication dates which precede the first publication of either specification, hence are impossible in practice. This media type registration encompasses both versions.
Published specification:
http://xspf.org/xspf-v1 (version 1)
http://xspf.org/xspf-v0 (version 0)
Applications that use this media type:
Gnomoradio, Webjay.org, Musicplayer, Playr, Jinzora, Yahoo Music Engine, Serpentine, Plurn, ultraPh0nZ FMP256, Spiffy, Plext, BMPx, I/ON, Drupal playlist module, Wordpress playlist module, Ning, Music For Dozens, Musicmobs/Mobster, VLC media player, AmaroK, Pear::Package::File_XSPF, CPAN XML::XSPF, Odeo, Jamendo, ArtistServer, Project Opus, (others)
Additional information:
Magic number(s):
none, but see section 3.1 of [RFC3023] (Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.).
File extension(s):
.xspf
Macintosh file type code(s):
"TEXT"
Fragment/anchor identifiers:
see [RFC3023] (Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.).
Person & email address to contact for further information:
Lucas Gonze <lucas@gonze.com>
Intended usage:
COMMON
Restrictions on usage:
none
Author/change controller:
The XSPF specification is a work product of the Xiph.org Foundation's Playlist Ad Hoc Group. The working group's home on the web is http://xspf.org. The specifications were edited by Lucas Gonze <lucas@gonze.com>, Matthias Friedrich <matt@mafr.de>, and Robert Kaye <rob@eorbit.net>.
XML namespace:
http://xspf.org/ns/0
Base URIs:
see [RFC3023] (Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.).
BOM:
see [RFC3023] (Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.).



 TOC 

3.  Security considerations

The XML-based media type being registered has all of the security considerations described in [RFC3023] (Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.) plus additional considerations.

Playlist authors who publish documents containing local filesystem paths should take care to not reveal confidential information contained in those strings.

The registration does not employ active content.



 TOC 

4. Normative References

[RFC2119] Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” BCP 14, RFC 2119, March 1997 (TXT, HTML, XML).
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” RFC 3023, January 2001.


 TOC 

Author's Address

  Lucas Gonze
  Yahoo! Music
  Venice, CA
  US
Email:  lucas@gonze.com


 TOC 

Full Copyright Statement

Intellectual Property

Acknowledgment