You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@labs.apache.org by fi...@apache.org on 2007/10/13 08:08:59 UTC

svn commit: r584374 - in /labs/webarch/trunk/http/draft-fielding-http: p3-payload.html p3-payload.xml

Author: fielding
Date: Fri Oct 12 23:08:59 2007
New Revision: 584374

URL: http://svn.apache.org/viewvc?rev=584374&view=rev
Log:
Resolve [LABS-10]: [i8] Media type registrations, by updating to RFC 4288

Modified:
    labs/webarch/trunk/http/draft-fielding-http/p3-payload.html
    labs/webarch/trunk/http/draft-fielding-http/p3-payload.xml

Modified: labs/webarch/trunk/http/draft-fielding-http/p3-payload.html
URL: http://svn.apache.org/viewvc/labs/webarch/trunk/http/draft-fielding-http/p3-payload.html?rev=584374&r1=584373&r2=584374&view=diff
==============================================================================
--- labs/webarch/trunk/http/draft-fielding-http/p3-payload.html (original)
+++ labs/webarch/trunk/http/draft-fielding-http/p3-payload.html Fri Oct 12 23:08:59 2007
@@ -609,7 +609,7 @@
          this section.
       </p>
       <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a id="media.types" href="#media.types">Media Types</a></h2>
-      <p id="rfc.section.2.3.p.1">HTTP uses Internet Media Types <a href="#RFC1590" id="rfc.xref.RFC1590.1"><cite title="Media Type Registration Procedure">[5]</cite></a> in the Content-Type (<a href="#header.content-type" id="rfc.xref.header.content-type.1" title="Content-Type">Section&nbsp;5.9</a>) and Accept (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;5.1</a>) header fields in order to provide open and extensible data typing and type negotiation.
+      <p id="rfc.section.2.3.p.1">HTTP uses Internet Media Types <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[5]</cite></a> in the Content-Type (<a href="#header.content-type" id="rfc.xref.header.content-type.1" title="Content-Type">Section&nbsp;5.9</a>) and Accept (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;5.1</a>) header fields in order to provide open and extensible data typing and type negotiation.
       </p>
       <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>    media-type     = type "/" subtype *( ";" parameter )
     type           = token
@@ -626,7 +626,7 @@
       <p id="rfc.section.2.3.p.6">Note that some older HTTP applications do not recognize media type parameters. When sending data to older HTTP applications,
          implementations <em class="bcp14">SHOULD</em> only use media type parameters when they are required by that type/subtype definition.
       </p>
-      <p id="rfc.section.2.3.p.7">Media-type values are registered with the Internet Assigned Number Authority (IANA <a href="#RFC1700" id="rfc.xref.RFC1700.3"><cite title="Assigned Numbers">[6]</cite></a>). The media type registration process is outlined in RFC 1590 <a href="#RFC1590" id="rfc.xref.RFC1590.2"><cite title="Media Type Registration Procedure">[5]</cite></a>. Use of non-registered media types is discouraged.
+      <p id="rfc.section.2.3.p.7">Media-type values are registered with the Internet Assigned Number Authority (IANA <a href="#RFC1700" id="rfc.xref.RFC1700.3"><cite title="Assigned Numbers">[6]</cite></a>). The media type registration process is outlined in RFC 4288 <a href="#RFC4288" id="rfc.xref.RFC4288.2"><cite title="Media Type Specifications and Registration Procedures">[5]</cite></a>. Use of non-registered media types is discouraged.
       </p>
       <h3 id="rfc.section.2.3.1"><a href="#rfc.section.2.3.1">2.3.1</a>&nbsp;<a id="canonicalization.and.text.defaults" href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></h3>
       <p id="rfc.section.2.3.1.p.1">Internet media types are registered with a canonical form. An entity-body transferred via HTTP messages <em class="bcp14">MUST</em> be represented in the appropriate canonical form prior to its transmission except for "text" types, as defined in the next
@@ -1175,8 +1175,8 @@
             </td>
          </tr>  
          <tr>
-            <td class="reference"><b id="RFC1590">[5]</b></td>
-            <td class="top"><a title="USC/Information Sciences Institute">Postel, J.</a>, “<a href="http://tools.ietf.org/html/rfc1590">Media Type Registration Procedure</a>”, RFC&nbsp;1590, November&nbsp;1996.
+            <td class="reference"><b id="RFC4288">[5]</b></td>
+            <td class="top"><a title="Sun Microsystems">Freed, N.</a> and <a>J. Klensin</a>, “<a href="http://tools.ietf.org/html/rfc4288">Media Type Specifications and Registration Procedures</a>”, BCP&nbsp;13, RFC&nbsp;4288, December&nbsp;2005.
             </td>
          </tr>  
          <tr>
@@ -1497,7 +1497,6 @@
                </ul>
             </li>
             <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
-                  <li class="indline1"><em>RFC1590</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1590.1">2.3</a>, <a class="iref" href="#rfc.xref.RFC1590.2">2.3</a>, <a class="iref" href="#RFC1590"><b>8</b></a></li>
                   <li class="indline1"><em>RFC1700</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1700.1">2.1</a>, <a class="iref" href="#rfc.xref.RFC1700.2">2.1</a>, <a class="iref" href="#rfc.xref.RFC1700.3">2.3</a>, <a class="iref" href="#RFC1700"><b>8</b></a></li>
                   <li class="indline1"><em>RFC1766</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1766.1">2.5</a>, <a class="iref" href="#RFC1766"><b>8</b></a></li>
                   <li class="indline1"><em>RFC1806</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1806.1">6.2</a>, <a class="iref" href="#RFC1806"><b>8</b></a>, <a class="iref" href="#rfc.xref.RFC1806.2">B.1</a></li>
@@ -1521,6 +1520,7 @@
                   <li class="indline1"><em>RFC2183</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2183.1">6.2</a>, <a class="iref" href="#RFC2183"><b>8</b></a></li>
                   <li class="indline1"><em>RFC2277</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2277.1">2.1</a>, <a class="iref" href="#RFC2277"><b>8</b></a></li>
                   <li class="indline1"><em>RFC2279</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2279.1">2.1</a>, <a class="iref" href="#RFC2279"><b>8</b></a></li>
+                  <li class="indline1"><em>RFC4288</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC4288.1">2.3</a>, <a class="iref" href="#rfc.xref.RFC4288.2">2.3</a>, <a class="iref" href="#RFC4288"><b>8</b></a></li>
                   <li class="indline1"><em>RFC822</em>&nbsp;&nbsp;<a class="iref" href="#RFC822"><b>8</b></a>, <a class="iref" href="#rfc.xref.RFC822.1">A</a></li>
                </ul>
             </li>

Modified: labs/webarch/trunk/http/draft-fielding-http/p3-payload.xml
URL: http://svn.apache.org/viewvc/labs/webarch/trunk/http/draft-fielding-http/p3-payload.xml?rev=584374&r1=584373&r2=584374&view=diff
==============================================================================
--- labs/webarch/trunk/http/draft-fielding-http/p3-payload.xml (original)
+++ labs/webarch/trunk/http/draft-fielding-http/p3-payload.xml Fri Oct 12 23:08:59 2007
@@ -307,7 +307,7 @@
 
 <section title="Media Types" anchor="media.types">
 <t>
-   HTTP uses Internet Media Types <xref target="RFC1590"/> in the Content-Type (<xref target="header.content-type"/>)
+   HTTP uses Internet Media Types <xref target="RFC4288"/> in the Content-Type (<xref target="header.content-type"/>)
    and Accept (<xref target="header.accept"/>) header fields in order to provide
    open and extensible data typing and type negotiation.
 </t>
@@ -343,7 +343,7 @@
 <t>
    Media-type values are registered with the Internet Assigned Number
    Authority (IANA <xref target="RFC1700"/>). The media type registration process is
-   outlined in RFC 1590 <xref target="RFC1590"/>. Use of non-registered media types is
+   outlined in RFC 4288 <xref target="RFC4288"/>. Use of non-registered media types is
    discouraged.
 </t>
 
@@ -1469,24 +1469,25 @@
 <seriesInfo name="RFC" value="1867"/>
 </reference>
 
-<reference anchor="RFC1590">
-<front>
-<title>Media Type Registration Procedure</title>
-<author initials="J." surname="Postel" fullname="Jon Postel">
-<organization>USC/Information Sciences Institute</organization>
-<address>
-<postal>
-<street>4676 Admiralty Way</street>
-<city>Marina del Rey</city>
-<region>CA</region>
-<code>90292</code>
-<country>US</country></postal>
-<phone>+1 310 822 1511</phone>
-<facsimile>+1 310 823 6714</facsimile>
-<email>Postel@ISI.EDU</email></address></author>
-<date month="November" year="1996"/>
-</front>
-<seriesInfo name="RFC" value="1590"/>
+<reference anchor="RFC4288">
+  <front>
+    <title>Media Type Specifications and Registration Procedures</title>
+    <author initials="N." surname="Freed" fullname="N. Freed">
+      <organization>Sun Microsystems</organization>
+      <address>
+        <email>ned.freed@mrochek.com</email>
+      </address>
+    </author>
+    <author initials="J." surname="Klensin" fullname="J. Klensin">
+      <organization/>
+      <address>
+        <email>klensin+ietf@jck.com</email>
+      </address>
+    </author>
+    <date year="2005" month="December"/>
+  </front>
+  <seriesInfo name="BCP" value="13"/>
+  <seriesInfo name="RFC" value="4288"/>
 </reference>
 
 <reference anchor="RFC1700">



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@labs.apache.org
For additional commands, e-mail: commits-help@labs.apache.org