[xiph-commits] r11655 - websites/xspf.org/specs/draft-gonze-media-type-xspf

lgonze at svn.xiph.org lgonze at svn.xiph.org
Sun Jun 25 15:45:50 PDT 2006


Author: lgonze
Date: 2006-06-25 15:45:49 -0700 (Sun, 25 Jun 2006)
New Revision: 11655

Modified:
   websites/xspf.org/specs/draft-gonze-media-type-xspf/index.html
Log:
Many small improvements.


Modified: websites/xspf.org/specs/draft-gonze-media-type-xspf/index.html
===================================================================
--- websites/xspf.org/specs/draft-gonze-media-type-xspf/index.html	2006-06-25 22:36:53 UTC (rev 11654)
+++ websites/xspf.org/specs/draft-gonze-media-type-xspf/index.html	2006-06-25 22:45:49 UTC (rev 11655)
@@ -1,457 +1,422 @@
-<html>
-<head>
-<title>Registration of media type application/xspf+xml</title>
-</head>
-<body>
-<pre>
+<!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.30 (http://xml.resource.org/)">
+<style type='text/css'>
+<!--
+    body {
+        font-family: verdana, charcoal, helvetica, arial, sans-serif;
+        margin: 2em;
+        font-size: small ; color: #000000 ; background-color: #ffffff ; }
+    .title { color: #990000; font-size: x-large ;
+        font-weight: bold; text-align: right;
+        font-family: helvetica, monaco, "MS Sans Serif", arial, sans-serif;
+        background-color: transparent; }
+    .filename { color: #666666; font-size: 18px; line-height: 28px;
+        font-weight: bold; text-align: right;
+        font-family: helvetica, arial, sans-serif;
+        background-color: transparent; }
+    td.rfcbug { background-color: #000000 ; width: 30px ; height: 30px ;
+        text-align: justify; vertical-align: middle ; padding-top: 2px ; }
+    td.rfcbug span.RFC { color: #666666; font-weight: bold; text-decoration: none;
+        background-color: #000000 ;
+        font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
+        font-size: x-small ; }
+    td.rfcbug span.hotText { color: #ffffff; font-weight: normal; text-decoration: none;
+        text-align: center ;
+        font-family: charcoal, monaco, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
+        font-size: x-small ; background-color: #000000; }
+    /* info code from SantaKlauss at http://www.madaboutstyle.com/tooltip2.html */
+    div#counter{margin-top: 100px}
 
+    a.info{
+        position:relative; /*this is the key*/
+        z-index:24;
+        text-decoration:none}
 
+    a.info:hover{z-index:25; background-color:#990000 ; color: #ffffff ;}
 
-Network Working Group                                           L. Gonze
-Internet-Draft                                              Yahoo! Music
-Expires: December 5, 2006                                   June 3, 2006
+    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:2em; width:15em;
+        padding: 2px ;
+        border:1px solid #333333;
+        background-color:#eeeeee; color:#990000;
+        text-align: left ;}
 
-            Registration of media type application/xspf+xml
-                    draft-gonze-media-type-xspf.txt
+     A { font-weight: bold; }
+     A:link { color: #990000; background-color: transparent ; }
+     A:visited { color: #333333; background-color: transparent ; }
+     A:active { color: #333333; background-color: transparent ; }
 
-Status of this Memo
+    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; }
 
-   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.
+    span.emph { font-style: italic; }
+    span.strong { font-weight: bold; }
+    span.verb, span.vbare { font-family: "Courier New", Courier, monospace ; }
 
-   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.
+    span.vemph { font-style: italic; font-family: "Courier New", Courier, monospace ; }
+    span.vstrong { font-weight: bold; font-family: "Courier New", Courier, monospace ; }
+    span.vdeluxe { font-weight: bold; font-style: italic; font-family: "Courier New", Courier, monospace ; }
 
-   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."
+    ol.text { margin-left: 2em; margin-right: 2em; }
+    ul.text { margin-left: 2em; margin-right: 2em; }
+    li { margin-left: 3em;  }
 
-   The list of current Internet-Drafts can be accessed at
-   http://www.ietf.org/ietf/1id-abstracts.txt.
+    pre { margin-left: 3em; color: #333333;  background-color: transparent;
+        font-family: "Courier New", Courier, monospace ; font-size: small ;
+        text-align: left;
+        }
 
-   The list of Internet-Draft Shadow Directories can be accessed at
-   http://www.ietf.org/shadow.html.
+    h3 { color: #333333; font-size: medium ;
+        font-family: helvetica, arial, sans-serif ;
+        background-color: transparent; }
+    h4 { font-size: small; font-family: helvetica, arial, sans-serif ; }
 
-   This Internet-Draft will expire on December 5, 2006.
+    table.bug { width: 30px ; height: 15px ; }
+    td.bug { color: #ffffff ; background-color: #990000 ;
+        text-align: center ; width: 30px ; height: 15px ;
+         }
+    td.bug A.link2 { color: #ffffff ; font-weight: bold;
+        text-decoration: none;
+        font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, sans-serif;
+        font-size: x-small ; background-color: transparent }
 
-Copyright Notice
+    td.header { color: #ffffff; font-size: x-small ;
+        font-family: arial, helvetica, sans-serif; vertical-align: top;
+        background-color: #666666 ; width: 33% ; }
+    td.author { font-weight: bold; margin-left: 4em; font-size: x-small ; }
+    td.author-text { font-size: x-small; }
+    table.full { vertical-align: top ; border-collapse: collapse ;
+        border-style: solid solid solid solid ;
+        border-color: black black black black ;
+        font-size: small ; text-align: center ; }
+    table.headers, table.none { vertical-align: top ; border-collapse: collapse ;
+        border-style: none;
+        font-size: small ; text-align: center ; }
+    table.full th { font-weight: bold ;
+        border-style: solid ;
+        border-color: black black black black ; }
+    table.headers th { font-weight: bold ;
+        border-style: none none solid none;
+        border-color: black black black black ; }
+    table.none th { font-weight: bold ;
+        border-style: none; }
+    table.full td {
+        border-style: solid solid solid solid ;
+        border-color: #333333 #333333 #333333 #333333 ; }
+    table.headers td, table.none td { border-style: none; }
 
-   Copyright (C) The Internet Society (2006).
+    hr { height: 1px }
+-->
+</style>
+</head>
+<body>
+<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2">&nbsp;TOC&nbsp;</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">Expires: December 27, 2006</td><td class="header">June 25, 2006</td></tr>
+</table></td></tr></table>
+<div align="right"><span class="title"><br />The application/xspf+xml Media Type</span></div>
+<div align="right"><span class="title"><br />draft-gonze-media-type-xspf</span></div>
 
-Abstract
+<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&nbsp;6 of BCP&nbsp;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 &ldquo;work in progress.&rdquo;</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 December 27, 2006.</p>
 
-   This is the media type specification for application/xspf+xml, which
-   will map to the playlist format XSPF ("spiff").
+<h3>Copyright Notice</h3>
+<p>
+Copyright &copy; The Internet Society (2006).</p>
 
+<h3>Abstract</h3>
 
+<p>This is the media type specification for the playlist format XSPF ("spiff").
+</p><a name="toc"></a><br /><hr />
+<h3>Table of Contents</h3>
+<p class="toc">
+<a href="#anchor1">1.</a>&nbsp;
+Requirements notation<br />
+<a href="#anchor2">2.</a>&nbsp;
+Registration<br />
+<a href="#anchor3">3.</a>&nbsp;
+Security considerations<br />
+<a href="#rfc.references1">4.</a>&nbsp;
+References<br />
+<a href="#rfc.authors">&#167;</a>&nbsp;
+Author's Address<br />
+<a href="#rfc.copyright">&#167;</a>&nbsp;
+Intellectual Property and Copyright Statements<br />
+</p>
+<br clear="all" />
 
+<a name="anchor1"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2">&nbsp;TOC&nbsp;</a></td></tr></table>
+<a name="rfc.section.1"></a><h3>1.&nbsp;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., &ldquo;Key words for use in RFCs to Indicate Requirement Levels,&rdquo; March&nbsp;1997.</span><span>)</span></a>.
+</p>
+<a name="anchor2"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2">&nbsp;TOC&nbsp;</a></td></tr></table>
+<a name="rfc.section.2"></a><h3>2.&nbsp;Registration</h3>
 
+<p>
+	</p>
+<blockquote class="text"><dl>
+<dt>Type name:</dt>
+<dd>
+	    application
+	  
+</dd>
+<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, &ldquo;XML Media Types,&rdquo; January&nbsp;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, &ldquo;XML Media Types,&rdquo; January&nbsp;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.
+	  
+</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, &ldquo;XML Media Types,&rdquo; January&nbsp;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, &ldquo;XML Media Types,&rdquo; January&nbsp;2001.</span><span>)</span></a>.
+		 
+</dd>
+</dl></blockquote>
+	  
+</dd>
+<dt>Person &amp; email address to contact for further information:</dt>
+<dd>
+	    Lucas Gonze &lt;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 &lt;lucas at gonze.com>, Matthias Friedrich
+	    &lt;matt at mafr.de>, and Robert Kaye &lt;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, &ldquo;XML Media Types,&rdquo; January&nbsp;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, &ldquo;XML Media Types,&rdquo; January&nbsp;2001.</span><span>)</span></a>.
+	  
+</dd>
+</dl></blockquote><p>
+      
+</p>
+<a name="anchor3"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2">&nbsp;TOC&nbsp;</a></td></tr></table>
+<a name="rfc.section.3"></a><h3>3.&nbsp;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, &ldquo;XML Media Types,&rdquo; January&nbsp;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="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2">&nbsp;TOC&nbsp;</a></td></tr></table>
+<h3>4.&nbsp;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>, &ldquo;<a href="ftp://ftp.isi.edu/in-notes/rfc2119.txt">Key words for use in RFCs to Indicate Requirement Levels</a>,&rdquo; BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;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, &ldquo;<a href="ftp://ftp.isi.edu/in-notes/rfc3023.txt">XML Media Types</a>,&rdquo; RFC&nbsp;3023, January&nbsp;2001.</td></tr>
+</table>
 
-
-
-
-Gonze                   Expires December 5, 2006                [Page 1]
-
-Internet-Draft       Media type application/xspf+xml           June 2006
-
-
-Table of Contents
-
-   1.  Requirements notation . . . . . . . . . . . . . . . . . . . . . 3
-   2.  Registration  . . . . . . . . . . . . . . . . . . . . . . . . . 4
-     2.1.  Type name . . . . . . . . . . . . . . . . . . . . . . . . . 4
-     2.2.  Subtype name  . . . . . . . . . . . . . . . . . . . . . . . 4
-     2.3.  Required parameters . . . . . . . . . . . . . . . . . . . . 4
-     2.4.  Optional parameters . . . . . . . . . . . . . . . . . . . . 4
-     2.5.  Encoding considerations . . . . . . . . . . . . . . . . . . 4
-     2.6.  Security considerations . . . . . . . . . . . . . . . . . . 4
-     2.7.  Interoperability considerations . . . . . . . . . . . . . . 4
-     2.8.  Published specification . . . . . . . . . . . . . . . . . . 4
-     2.9.  Applications that use this media type . . . . . . . . . . . 5
-     2.10. Additional information  . . . . . . . . . . . . . . . . . . 5
-       2.10.1.  Magic number(s)  . . . . . . . . . . . . . . . . . . . 5
-       2.10.2.  File extension(s)  . . . . . . . . . . . . . . . . . . 5
-       2.10.3.  Macintosh file type code(s)  . . . . . . . . . . . . . 5
-       2.10.4.  Fragment/anchor identifiers  . . . . . . . . . . . . . 5
-     2.11. Person & email address to contact for further
-           information . . . . . . . . . . . . . . . . . . . . . . . . 5
-     2.12. Intended usage  . . . . . . . . . . . . . . . . . . . . . . 5
-     2.13. Restrictions on usage . . . . . . . . . . . . . . . . . . . 5
-     2.14. Author/change controller  . . . . . . . . . . . . . . . . . 5
-     2.15. XML namespace . . . . . . . . . . . . . . . . . . . . . . . 5
-     2.16. Base URIs . . . . . . . . . . . . . . . . . . . . . . . . . 6
-     2.17. BOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
-   3.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 6
-   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 7
-   Intellectual Property and Copyright Statements  . . . . . . . . . . 8
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-Gonze                   Expires December 5, 2006                [Page 2]
-
-Internet-Draft       Media type application/xspf+xml           June 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 December 5, 2006                [Page 3]
-
-Internet-Draft       Media type application/xspf+xml           June 2006
-
-
-2.  Registration
-
-2.1.  Type name
-
-   application
-
-2.2.  Subtype name
-
-   xspf+xml
-
-2.3.  Required parameters
-
-   none
-
-2.4.  Optional parameters
-
-   charset.  Same as charset parameter of application/xml as specified
-   in [RFC3023].
-
-2.5.  Encoding considerations
-
-   Same as encoding considerations of application/xml as specified in
-   [RFC3023].
-
-2.6.  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.
-
-2.7.  Interoperability considerations
-
-   Versions 0 and 1 are compatible except for some playlist publication
-   dates which precede the first publication of either specification.
-
-2.8.  Published specification
-
-   http://xspf.org/xspf-v1 (version 1)
-
-   http://xspf.org/xspf-v0 (version 0)
-
-
-
-
-
-
-Gonze                   Expires December 5, 2006                [Page 4]
-
-Internet-Draft       Media type application/xspf+xml           June 2006
-
-
-2.9.  Applications that use this media type
-
-   Gnomoradio, Webjay.org, Musicplayer, Playr, Yahoo Music Engine,
-   Videolan Client, AmaroK, BMPx, I/ON, (others)
-
-2.10.  Additional information
-
-2.10.1.  Magic number(s)
-
-   none, but see section 3.1 of [RFC3023].
-
-2.10.2.  File extension(s)
-
-   .xspf
-
-2.10.3.  Macintosh file type code(s)
-
-   "TEXT"
-
-2.10.4.  Fragment/anchor identifiers
-
-   see [RFC3023].
-
-2.11.  Person & email address to contact for further information
-
-   Lucas Gonze <lucas at gonze.com>
-
-2.12.  Intended usage
-
-   COMMON
-
-2.13.  Restrictions on usage
-
-   none
-
-2.14.  Author/change controller
-
-   The XSPF specification is a work product of the Xiph.org Foundation's
-   XSPF Group homed at http://xspf.org.  The specification was edited by
-   Lucas Gonze <lucas at gonze.com>, Matthias Friedrich <matt at mafr.de>, and
-   Robert Kaye <rob at eorbit.net>
-
-2.15.  XML namespace
-
-   http://xspf.org/ns/0
-
-
-
-
-
-
-Gonze                   Expires December 5, 2006                [Page 5]
-
-Internet-Draft       Media type application/xspf+xml           June 2006
-
-
-2.16.  Base URIs
-
-   see [RFC3023].
-
-2.17.  BOM
-
-   see [RFC3023].
-
-3.  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 December 5, 2006                [Page 6]
-
-Internet-Draft       Media type application/xspf+xml           June 2006
-
-
-Author's Address
-
-   Lucas Gonze
-   Yahoo! Music
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-Gonze                   Expires December 5, 2006                [Page 7]
-
-Internet-Draft       Media type application/xspf+xml           June 2006
-
-
-Intellectual Property Statement
-
-   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.
-
-
-Disclaimer of Validity
-
-   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.
-
-
-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.
-
-
-Acknowledgment
-
-   Funding for the RFC Editor function is currently provided by the
-   Internet Society.
-
-
-
-
-Gonze                   Expires December 5, 2006                [Page 8]
-
-</pre>
-</body>
-</html>
\ No newline at end of file
+<a name="rfc.authors"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2">&nbsp;TOC&nbsp;</a></td></tr></table>
+<h3>Author's Address</h3>
+<table width="99%" border="0" cellpadding="0" cellspacing="0">
+<tr><td class="author-text">&nbsp;</td>
+<td class="author-text">Lucas Gonze</td></tr>
+<tr><td class="author-text">&nbsp;</td>
+<td class="author-text">Yahoo! Music</td></tr>
+<tr><td class="author-text">&nbsp;</td>
+<td class="author-text">Venice, CA</td></tr>
+<tr><td class="author-text">&nbsp;</td>
+<td class="author-text">US</td></tr>
+<tr><td class="author" align="right">Email:&nbsp;</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="bug" align="right"><tr><td class="bug"><a href="#toc" class="link2">&nbsp;TOC&nbsp;</a></td></tr></table>
+<h3>Intellectual Property Statement</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&nbsp;78 and BCP&nbsp;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>Disclaimer of Validity</h3>
+<p class='copyright'>
+This document and the information contained herein are provided
+on an &ldquo;AS IS&rdquo; 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>Copyright Statement</h3>
+<p class='copyright'>
+Copyright &copy; The Internet Society (2006).
+This document is subject to the rights,
+licenses and restrictions contained in BCP&nbsp;78,
+and except as set forth therein,
+the authors retain all their rights.</p>
+<h3>Acknowledgment</h3>
+<p class='copyright'>
+Funding for the RFC Editor function is currently provided by the
+Internet Society.</p>
+</body></html>



More information about the commits mailing list