[xiph-commits] r11854 -
websites/xspf.org/specs/draft-gonze-media-type-xspf
lgonze at svn.xiph.org
lgonze at svn.xiph.org
Sat Sep 23 14:43:04 PDT 2006
Author: lgonze
Date: 2006-09-23 14:43:02 -0700 (Sat, 23 Sep 2006)
New Revision: 11854
Added:
websites/xspf.org/specs/draft-gonze-media-type-xspf/draft-gonze-media-type-xspf-01.html
websites/xspf.org/specs/draft-gonze-media-type-xspf/draft-gonze-media-type-xspf-01.txt
websites/xspf.org/specs/draft-gonze-media-type-xspf/draft-gonze-media-type-xspf-01.xml
Log:
update abstract and references for to accomodate likely nits.
Added: websites/xspf.org/specs/draft-gonze-media-type-xspf/draft-gonze-media-type-xspf-01.html
===================================================================
--- websites/xspf.org/specs/draft-gonze-media-type-xspf/draft-gonze-media-type-xspf-01.html 2006-09-23 15:55:59 UTC (rev 11853)
+++ websites/xspf.org/specs/draft-gonze-media-type-xspf/draft-gonze-media-type-xspf-01.html 2006-09-23 21:43:02 UTC (rev 11854)
@@ -0,0 +1,442 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html lang="en"><head><title>The application/xspf+xml Media Type</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<meta name="description" content="The application/xspf+xml Media Type">
+<meta name="generator" content="xml2rfc v1.31 (http://xml.resource.org/)">
+<style type='text/css'><!--
+ body {
+ font-family: verdana, charcoal, helvetica, arial, sans-serif;
+ font-size: small; color: #000; background-color: #FFF;
+ margin: 2em;
+ }
+ h1, h2, h3, h4, h5, h6 {
+ font-family: helvetica, monaco, "MS Sans Serif", arial, sans-serif;
+ font-weight: bold; font-style: normal;
+ }
+ h1 { color: #900; background-color: transparent; text-align: right; }
+ h3 { color: #333; background-color: transparent; }
+
+ td.RFCbug {
+ font-size: x-small; text-decoration: none;
+ width: 30px; height: 30px; padding-top: 2px;
+ text-align: justify; vertical-align: middle;
+ background-color: #000;
+ }
+ td.RFCbug span.RFC {
+ font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
+ font-weight: bold; color: #666;
+ }
+ td.RFCbug span.hotText {
+ font-family: charcoal, monaco, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
+ font-weight: normal; text-align: center; color: #FFF;
+ }
+
+ table.TOCbug { width: 30px; height: 15px; }
+ td.TOCbug {
+ text-align: center; width: 30px; height: 15px;
+ color: #FFF; background-color: #900;
+ }
+ td.TOCbug a {
+ font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, sans-serif;
+ font-weight: bold; font-size: x-small; text-decoration: none;
+ color: #FFF; background-color: transparent;
+ }
+
+ td.header {
+ font-family: arial, helvetica, sans-serif; font-size: x-small;
+ vertical-align: top; width: 33%;
+ color: #FFF; background-color: #666;
+ }
+ td.author { font-weight: bold; font-size: x-small; margin-left: 4em; }
+ td.author-text { font-size: x-small; }
+
+ /* info code from SantaKlauss at http://www.madaboutstyle.com/tooltip2.html */
+ a.info {
+ /* This is the key. */
+ position: relative;
+ z-index: 24;
+ text-decoration: none;
+ }
+ a.info:hover {
+ z-index: 25;
+ color: #FFF; background-color: #900;
+ }
+ a.info span { display: none; }
+ a.info:hover span.info {
+ /* The span will display just on :hover state. */
+ display: block;
+ position: absolute;
+ font-size: smaller;
+ top: 2em; left: -5em; width: 15em;
+ padding: 2px; border: 1px solid #333;
+ color: #900; background-color: #EEE;
+ text-align: left;
+ }
+
+ a { font-weight: bold; }
+ a:link { color: #900; background-color: transparent; }
+ a:visited { color: #633; background-color: transparent; }
+ a:active { color: #633; background-color: transparent; }
+
+ p { margin-left: 2em; margin-right: 2em; }
+ p.copyright { font-size: x-small; }
+ p.toc { font-size: small; font-weight: bold; margin-left: 3em; }
+ table.toc { margin: 0 0 0 3em; padding: 0; border: 0; vertical-align: text-top; }
+ td.toc { font-size: small; font-weight: bold; vertical-align: text-top; }
+
+ ol.text { margin-left: 2em; margin-right: 2em; }
+ ul.text { margin-left: 2em; margin-right: 2em; }
+ li { margin-left: 3em; }
+
+ /* RFC-2629 <spanx>s and <artwork>s. */
+ em { font-style: italic; }
+ strong { font-weight: bold; }
+ dfn { font-weight: bold; font-style: normal; }
+ cite { font-weight: normal; font-style: normal; }
+ tt { color: #036; }
+ tt, pre, pre dfn, pre em, pre cite, pre span {
+ font-family: "Courier New", Courier, monospace; font-size: small;
+ }
+ pre {
+ text-align: left; padding: 4px;
+ color: #000; background-color: #CCC;
+ }
+ pre dfn { color: #900; }
+ pre em { color: #66F; background-color: #FFC; font-weight: normal; }
+ pre .key { color: #33C; font-weight: bold; }
+ pre .id { color: #900; }
+ pre .str { color: #000; background-color: #CFF; }
+ pre .val { color: #066; }
+ pre .rep { color: #909; }
+ pre .oth { color: #000; background-color: #FCF; }
+ pre .err { background-color: #FCC; }
+
+ /* RFC-2629 <texttable>s. */
+ table.full, table.headers, table.none {
+ font-size: small; text-align: center; border-width: 2px;
+ vertical-align: top; border-collapse: collapse;
+ }
+ table.full { border-style: solid; border-color: black; }
+ table.headers, table.none { border-style: none; }
+ th {
+ font-weight: bold; border-color: black;
+ border-width: 2px 2px 3px 2px;
+ }
+ table.full th { border-style: solid; }
+ table.headers th { border-style: none none solid none; }
+ table.none th { border-style: none; }
+ table.full td {
+ border-style: solid; border-color: #333;
+ border-width: 1px 2px;
+ }
+ table.headers td, table.none td { border-style: none; }
+
+ hr { height: 1px; }
+ hr.insert {
+ width: 80%; border-style: none; border-width: 0;
+ color: #CCC; background-color: #CCC;
+ }
+--></style>
+</head>
+<body>
+<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
+<table summary="layout" width="66%" border="0" cellpadding="0" cellspacing="0"><tr><td><table summary="layout" width="100%" border="0" cellpadding="2" cellspacing="1">
+<tr><td class="header">Network Working Group</td><td class="header">L. Gonze</td></tr>
+<tr><td class="header">Internet-Draft</td><td class="header">Yahoo! Music</td></tr>
+<tr><td class="header">Intended status: Informational</td><td class="header">September 23, 2006</td></tr>
+<tr><td class="header">Expires: March 27, 2007</td><td class="header"> </td></tr>
+</table></td></tr></table>
+<h1><br />The application/xspf+xml Media Type<br />draft-gonze-media-type-xspf-01</h1>
+
+<h3>Status of this Memo</h3>
+<p>
+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.</p>
+<p>
+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.</p>
+<p>
+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.”</p>
+<p>
+The list of current Internet-Drafts can be accessed at
+<a href='http://www.ietf.org/ietf/1id-abstracts.txt'>http://www.ietf.org/ietf/1id-abstracts.txt</a>.</p>
+<p>
+The list of Internet-Draft Shadow Directories can be accessed at
+<a href='http://www.ietf.org/shadow.html'>http://www.ietf.org/shadow.html</a>.</p>
+<p>
+This Internet-Draft will expire on March 27, 2007.</p>
+
+<h3>Copyright Notice</h3>
+<p>
+Copyright © The Internet Society (2006).</p>
+
+<h3>Abstract</h3>
+
+<p>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.
+</p>
+<p>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.
+</p><a name="toc"></a><br /><hr />
+<h3>Table of Contents</h3>
+<p class="toc">
+<a href="#anchor1">1.</a>
+Requirements notation<br />
+<a href="#anchor2">2.</a>
+Registration<br />
+<a href="#anchor3">3.</a>
+Security considerations<br />
+<a href="#rfc.references1">4.</a>
+Normative References<br />
+<a href="#rfc.authors">§</a>
+Author's Address<br />
+<a href="#rfc.copyright">§</a>
+Intellectual Property and Copyright Statements<br />
+</p>
+<br clear="all" />
+
+<a name="anchor1"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
+<a name="rfc.section.1"></a><h3>1.
+Requirements notation</h3>
+
+<p>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 <a class='info' href='#RFC2119'>[RFC2119]<span> (</span><span class='info'>Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.</span><span>)</span></a>.
+</p>
+<a name="anchor2"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
+<a name="rfc.section.2"></a><h3>2.
+Registration</h3>
+
+<p>
+ </p>
+<blockquote class="text"><dl>
+<dt>Type name:</dt>
+<dd>
+ application
+
+</dd>
+<dt>Subtype name:</dt>
+<dd>
+ xspf+xml
+
+</dd>
+<dt>Required parameters:</dt>
+<dd>
+ none
+
+</dd>
+<dt>Optional parameters:</dt>
+<dd>
+ charset. Same as charset parameter of application/xml as
+ specified in <a class='info' href='#RFC3023'>[RFC3023]<span> (</span><span class='info'>Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.</span><span>)</span></a>.
+
+</dd>
+<dt>Encoding considerations:</dt>
+<dd>
+ Same as encoding considerations of application/xml as
+ specified in <a class='info' href='#RFC3023'>[RFC3023]<span> (</span><span class='info'>Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.</span><span>)</span></a>.
+
+</dd>
+<dt>Interoperability considerations:</dt>
+<dd>
+ 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.
+
+</dd>
+<dt>Published specification:</dt>
+<dd>
+
+<blockquote class="text"><dl>
+<dt></dt>
+<dd>http://xspf.org/xspf-v1 (version 1)
+</dd>
+<dt></dt>
+<dd>http://xspf.org/xspf-v0 (version 0)
+</dd>
+</dl></blockquote>
+
+</dd>
+<dt>Applications that use this media type:</dt>
+<dd>
+ 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)
+
+</dd>
+<dt>Additional information:</dt>
+<dd>
+
+<blockquote class="text"><dl>
+<dt>Magic number(s):</dt>
+<dd>
+ none, but see section 3.1 of <a class='info' href='#RFC3023'>[RFC3023]<span> (</span><span class='info'>Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.</span><span>)</span></a>.
+
+</dd>
+<dt>File extension(s):</dt>
+<dd>
+ .xspf
+
+</dd>
+<dt>Macintosh file type code(s):</dt>
+<dd>
+ "TEXT"
+
+</dd>
+<dt>Fragment/anchor identifiers:</dt>
+<dd>
+ see <a class='info' href='#RFC3023'>[RFC3023]<span> (</span><span class='info'>Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.</span><span>)</span></a>.
+
+</dd>
+</dl></blockquote>
+
+</dd>
+<dt>Person & email address to contact for further information:</dt>
+<dd>
+ Lucas Gonze <lucas at gonze.com>
+
+</dd>
+<dt>Intended usage:</dt>
+<dd>
+ COMMON
+
+</dd>
+<dt>Restrictions on usage:</dt>
+<dd>
+ none
+
+</dd>
+<dt>Author/change controller:</dt>
+<dd>
+ 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 at gonze.com>, Matthias Friedrich
+ <matt at mafr.de>, and Robert Kaye <rob at eorbit.net>.
+
+</dd>
+<dt>XML namespace:</dt>
+<dd>
+ http://xspf.org/ns/0
+
+</dd>
+<dt>Base URIs:</dt>
+<dd>
+ see <a class='info' href='#RFC3023'>[RFC3023]<span> (</span><span class='info'>Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.</span><span>)</span></a>.
+
+</dd>
+<dt>BOM:</dt>
+<dd>
+ see <a class='info' href='#RFC3023'>[RFC3023]<span> (</span><span class='info'>Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.</span><span>)</span></a>.
+
+</dd>
+</dl></blockquote><p>
+
+</p>
+<a name="anchor3"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
+<a name="rfc.section.3"></a><h3>3.
+Security considerations</h3>
+
+<p>
+ </p>
+<blockquote class="text">
+<p>The XML-based media type being registered has all
+ of the security considerations described in <a class='info' href='#RFC3023'>[RFC3023]<span> (</span><span class='info'>Murata, M., St. Laurent, S., and D. Kohn, “XML Media Types,” January 2001.</span><span>)</span></a> plus additional
+ considerations.
+</p>
+<p>Playlist authors who publish documents containing
+ local filesystem paths should take care to not reveal
+ confidential information contained in those
+ strings.
+</p>
+<p>The registration does not employ active content.
+</p>
+</blockquote><p>
+
+</p>
+<a name="rfc.references1"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
+<h3>4. Normative References</h3>
+<table width="99%" border="0">
+<tr><td class="author-text" valign="top"><a name="RFC2119">[RFC2119]</a></td>
+<td class="author-text"><a href="mailto:sob at harvard.edu">Bradner, S.</a>, “<a href="ftp://ftp.isi.edu/in-notes/rfc2119.txt">Key words for use in RFCs to Indicate Requirement Levels</a>,” BCP 14, RFC 2119, March 1997 (<a href="ftp://ftp.isi.edu/in-notes/rfc2119.txt">TXT</a>, <a href="http://xml.resource.org/public/rfc/html/rfc2119.html">HTML</a>, <a href="http://xml.resource.org/public/rfc/xml/rfc2119.xml">XML</a>).</td></tr>
+<tr><td class="author-text" valign="top"><a name="RFC3023">[RFC3023]</a></td>
+<td class="author-text">Murata, M., St. Laurent, S., and D. Kohn, “<a href="ftp://ftp.isi.edu/in-notes/rfc3023.txt">XML Media Types</a>,” RFC 3023, January 2001.</td></tr>
+</table>
+
+<a name="rfc.authors"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
+<h3>Author's Address</h3>
+<table width="99%" border="0" cellpadding="0" cellspacing="0">
+<tr><td class="author-text"> </td>
+<td class="author-text">Lucas Gonze</td></tr>
+<tr><td class="author-text"> </td>
+<td class="author-text">Yahoo! Music</td></tr>
+<tr><td class="author-text"> </td>
+<td class="author-text">Venice, CA</td></tr>
+<tr><td class="author-text"> </td>
+<td class="author-text">US</td></tr>
+<tr><td class="author" align="right">Email: </td>
+<td class="author-text"><a href="mailto:lucas at gonze.com">lucas at gonze.com</a></td></tr>
+</table>
+<a name="rfc.copyright"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
+<h3>Full Copyright Statement</h3>
+<p class='copyright'>
+Copyright © The Internet Society (2006).</p>
+<p class='copyright'>
+This document is subject to the rights,
+licenses and restrictions contained in BCP 78,
+and except as set forth therein,
+the authors retain all their rights.</p>
+<p class='copyright'>
+This document and the information contained herein are provided
+on an “AS IS” basis and THE CONTRIBUTOR,
+THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY),
+THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM
+ALL WARRANTIES,
+EXPRESS OR IMPLIED,
+INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
+INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
+WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.</p>
+<h3>Intellectual Property</h3>
+<p class='copyright'>
+The IETF takes no position regarding the validity or scope of any
+Intellectual Property Rights or other rights that might be claimed
+to pertain to the implementation or use of the technology
+described in this document or the extent to which any license
+under such rights might or might not be available; nor does it
+represent that it has made any independent effort to identify any
+such rights.
+Information on the procedures with respect to
+rights in RFC documents can be found in BCP 78 and BCP 79.</p>
+<p class='copyright'>
+Copies of IPR disclosures made to the IETF Secretariat and any
+assurances of licenses to be made available,
+or the result of an attempt made to obtain a general license or
+permission for the use of such proprietary rights by implementers or
+users of this specification can be obtained from the IETF on-line IPR
+repository at <a href='http://www.ietf.org/ipr'>http://www.ietf.org/ipr</a>.</p>
+<p class='copyright'>
+The IETF invites any interested party to bring to its attention
+any copyrights,
+patents or patent applications,
+or other
+proprietary rights that may cover technology that may be required
+to implement this standard.
+Please address the information to the IETF at <a href='mailto:ietf-ipr at ietf.org'>ietf-ipr at ietf.org</a>.</p>
+<h3>Acknowledgment</h3>
+<p class='copyright'>
+Funding for the RFC Editor function is provided by
+the IETF Administrative Support Activity (IASA).</p>
+</body></html>
+
Added: websites/xspf.org/specs/draft-gonze-media-type-xspf/draft-gonze-media-type-xspf-01.txt
===================================================================
--- websites/xspf.org/specs/draft-gonze-media-type-xspf/draft-gonze-media-type-xspf-01.txt 2006-09-23 15:55:59 UTC (rev 11853)
+++ websites/xspf.org/specs/draft-gonze-media-type-xspf/draft-gonze-media-type-xspf-01.txt 2006-09-23 21:43:02 UTC (rev 11854)
@@ -0,0 +1,505 @@
+
+
+
+Network Working Group L. Gonze
+Internet-Draft Yahoo! Music
+Intended status: Informational September 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 (C) The Internet Society (2006).
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Gonze Expires March 27, 2007 [Page 1]
+
+Internet-Draft Media type application/xspf+xml September 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 . . . . . . . . . . . . . . . . . . . . . 3
+ 2. Registration . . . . . . . . . . . . . . . . . . . . . . . . . 4
+ 3. Security considerations . . . . . . . . . . . . . . . . . . . . 6
+ 4. Normative References . . . . . . . . . . . . . . . . . . . . . 7
+ Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8
+ Intellectual Property and Copyright Statements . . . . . . . . . . 9
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Gonze Expires March 27, 2007 [Page 2]
+
+Internet-Draft Media type application/xspf+xml September 2006
+
+
+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].
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Gonze Expires March 27, 2007 [Page 3]
+
+Internet-Draft Media type application/xspf+xml September 2006
+
+
+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].
+
+ Encoding considerations: Same as encoding considerations of
+ application/xml as specified in [RFC3023].
+
+ 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].
+
+ File extension(s): .xspf
+
+ Macintosh file type code(s): "TEXT"
+
+ Fragment/anchor identifiers: see [RFC3023].
+
+ Person & email address to contact for further information: Lucas
+ Gonze <lucas at gonze.com>
+
+
+
+
+
+
+Gonze Expires March 27, 2007 [Page 4]
+
+Internet-Draft Media type application/xspf+xml September 2006
+
+
+ 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 at gonze.com>, Matthias Friedrich
+ <matt at mafr.de>, and Robert Kaye <rob at eorbit.net>.
+
+ XML namespace: http://xspf.org/ns/0
+
+ Base URIs: see [RFC3023].
+
+ BOM: see [RFC3023].
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Gonze Expires March 27, 2007 [Page 5]
+
+Internet-Draft Media type application/xspf+xml September 2006
+
+
+3. Security considerations
+
+ The XML-based media type being registered has all of the security
+ considerations described in [RFC3023] 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.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Gonze Expires March 27, 2007 [Page 6]
+
+Internet-Draft Media type application/xspf+xml September 2006
+
+
+4. Normative References
+
+ [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
+ Requirement Levels", BCP 14, RFC 2119, March 1997.
+
+ [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
+ Types", RFC 3023, January 2001.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Gonze Expires March 27, 2007 [Page 7]
+
+Internet-Draft Media type application/xspf+xml September 2006
+
+
+Author's Address
+
+ Lucas Gonze
+ Yahoo! Music
+ Venice, CA
+ US
+
+ Email: lucas at gonze.com
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Gonze Expires March 27, 2007 [Page 8]
+
+Internet-Draft Media type application/xspf+xml September 2006
+
+
+Full Copyright Statement
+
+ Copyright (C) The Internet Society (2006).
+
+ This document is subject to the rights, licenses and restrictions
+ contained in BCP 78, and except as set forth therein, the authors
+ retain all their rights.
+
+ This document and the information contained herein are provided on an
+ "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
+ OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
+ ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
+ INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
+ INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
+ WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
+
+
+Intellectual Property
+
+ The IETF takes no position regarding the validity or scope of any
+ Intellectual Property Rights or other rights that might be claimed to
+ pertain to the implementation or use of the technology described in
+ this document or the extent to which any license under such rights
+ might or might not be available; nor does it represent that it has
+ made any independent effort to identify any such rights. Information
+ on the procedures with respect to rights in RFC documents can be
+ found in BCP 78 and BCP 79.
+
+ Copies of IPR disclosures made to the IETF Secretariat and any
+ assurances of licenses to be made available, or the result of an
+ attempt made to obtain a general license or permission for the use of
+ such proprietary rights by implementers or users of this
+ specification can be obtained from the IETF on-line IPR repository at
+ http://www.ietf.org/ipr.
+
+ The IETF invites any interested party to bring to its attention any
+ copyrights, patents or patent applications, or other proprietary
+ rights that may cover technology that may be required to implement
+ this standard. Please address the information to the IETF at
+ ietf-ipr at ietf.org.
+
+
+Acknowledgment
+
+ Funding for the RFC Editor function is provided by the IETF
+ Administrative Support Activity (IASA).
+
+
+
+
+
+Gonze Expires March 27, 2007 [Page 9]
+
+
Added: websites/xspf.org/specs/draft-gonze-media-type-xspf/draft-gonze-media-type-xspf-01.xml
===================================================================
--- websites/xspf.org/specs/draft-gonze-media-type-xspf/draft-gonze-media-type-xspf-01.xml 2006-09-23 15:55:59 UTC (rev 11853)
+++ websites/xspf.org/specs/draft-gonze-media-type-xspf/draft-gonze-media-type-xspf-01.xml 2006-09-23 21:43:02 UTC (rev 11854)
@@ -0,0 +1,175 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
+<!ENTITY rfc2119 PUBLIC ''
+'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
+<!ENTITY rfc3023 PUBLIC ''
+'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3023.xml'>
+]>
+
+<rfc ipr="full3978" docName="draft-gonze-media-type-xspf-01">
+
+ <?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
+
+ <?rfc toc="yes" ?>
+ <?rfc symrefs="yes" ?>
+ <?rfc sortrefs="yes"?>
+ <?rfc iprnotified="no" ?>
+ <?rfc strict="yes" ?>
+
+ <front>
+ <title abbrev="Media type application/xspf+xml">The application/xspf+xml Media Type</title>
+
+ <author
+ fullname="Lucas Gonze"
+ initials="L."
+ surname="Gonze">
+
+ <organization>Yahoo! Music</organization>
+ <address>
+ <postal>
+ <street/>
+ <city>Venice</city> <region>CA</region>
+ <country>US</country>
+ </postal>
+ <email>lucas at gonze.com</email>
+ </address>
+ </author>
+
+ <date month="September" year="2006"/>
+ <abstract><t>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.</t>
+
+ <t>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.</t>
+ </abstract>
+ </front>
+
+ <middle>
+ <section title="Requirements notation">
+ <t>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 <xref target="RFC2119"/>.</t>
+ </section>
+
+ <section title="Registration">
+
+ <t>
+ <list style="hanging">
+
+ <t hangText="Type name:">
+ application
+ </t>
+
+ <t hangText="Subtype name:">
+ xspf+xml
+ </t>
+
+ <t hangText="Required parameters:">
+ none
+ </t>
+
+ <t hangText="Optional parameters:">
+ charset. Same as charset parameter of application/xml as
+ specified in <xref target="RFC3023"/>.
+ </t>
+
+ <t hangText="Encoding considerations:">
+ Same as encoding considerations of application/xml as
+ specified in <xref target="RFC3023"/>.
+ </t>
+
+ <t hangText="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.
+ </t>
+
+ <t hangText="Published specification:">
+ <list>
+ <t>http://xspf.org/xspf-v1 (version 1)</t>
+ <t>http://xspf.org/xspf-v0 (version 0)</t>
+ </list>
+ </t>
+
+ <t hangText="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)
+ </t>
+
+ <t hangText="Additional information:">
+ <list style="hanging">
+ <t hangText="Magic number(s):">
+ none, but see section 3.1 of <xref target="RFC3023"/>.
+ </t>
+ <t hangText="File extension(s):">
+ .xspf
+ </t>
+ <t hangText="Macintosh file type code(s):">
+ "TEXT"
+ </t>
+ <t hangText="Fragment/anchor identifiers:">
+ see <xref target="RFC3023"/>.
+ </t>
+ </list>
+ </t>
+
+ <t hangText="Person & email address to contact for further information:">
+ Lucas Gonze <lucas at gonze.com>
+ </t>
+
+ <t hangText="Intended usage:">
+ COMMON
+ </t>
+
+ <t hangText="Restrictions on usage:">
+ none
+ </t>
+
+ <t hangText="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 at gonze.com>, Matthias Friedrich
+ <matt at mafr.de>, and Robert Kaye <rob at eorbit.net>.
+ </t>
+
+ <t hangText="XML namespace:">
+ http://xspf.org/ns/0
+ </t>
+
+ <t hangText="Base URIs:">
+ see <xref target="RFC3023"/>.
+ </t>
+
+ <t hangText="BOM:">
+ see <xref target="RFC3023"/>.
+ </t>
+
+ </list>
+ </t>
+ </section><!-- end Registration -->
+
+ <section title="Security considerations">
+ <t>
+ <list>
+ <t>The XML-based media type being registered has all
+ of the security considerations described in <xref
+ target="RFC3023"/> plus additional
+ considerations.</t>
+
+ <t>Playlist authors who publish documents containing
+ local filesystem paths should take care to not reveal
+ confidential information contained in those
+ strings.</t>
+
+ <t>The registration does not employ active content.</t>
+ </list>
+ </t>
+ </section>
+
+ </middle>
+
+ <back>
+ <references title='Normative References'>&rfc2119;&rfc3023;</references>
+ </back>
+
+</rfc>
More information about the commits
mailing list