Changeset 446 for draft-ietf-httpbis/latest/p3-payload.html

Timestamp:

Feb 20, 2009, 6:59:11 AM (11 years ago)

Author:

julian.reschke@…

Message:

Update to latest version of rfc2629.xslt, and add experimental version of xml2rfc.tcl (supporting the new IPR escape clause), use that clause in P1..P7 (but not for the method registrations).

File:

• draft-ietf-httpbis/latest/p3-payload.html (modified) (8 diffs)

draft-ietf-httpbis/latest/p3-payload.html

@@ -69 +69 @@
   page-break-after: avoid;
 }
-h2 a {
-  color: black;
-}
-h3 {
+h3, h4, h5, h6 {
   font-size: 10pt;
   page-break-after: avoid;
 }
-h3 a {
-  color: black;
-}
-h4 {
-  font-size: 10pt;
-  page-break-after: avoid;
-}
-h4 a {
-  color: black;
-}
-h5 {
-  font-size: 10pt;
-  page-break-after: avoid;
-}
-h5 a {
+h2 a, h3 a, h4 a, h5 a, h6 a {
   color: black;
 }
@@ -389 +372 @@
       <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D">
       <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E">
-      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.415, 2009-01-29 15:06:08, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
+      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.421, 2009-02-20 13:12:03, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
       <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
       <meta name="DC.Creator" content="Fielding, R.">
@@ -485 +468 @@
          <tr>
             <td class="header left"></td>
-            <td class="header right">February 2, 2009</td>
+            <td class="header right">February 20, 2009</td>
          </tr>
       </table>
       <p class="title">HTTP/1.1, part 3: Message Payload and Content Negotiation<br><span class="filename">draft-ietf-httpbis-p3-payload-latest</span></p>
       <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
-      <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>This Internet-Draft is submitted to IETF pursuant to, and in full conformance with, the provisions of BCP 78 and BCP 79. This
+         document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
+         10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
+         allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
+         controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
+         works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
+         it into languages other than English.
       </p>
       <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
@@ -506 +493 @@
       </p>
       <p>This Internet-Draft will expire in August 2009.</p>
+      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
+      <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
+      <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date
+         of publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
+      </p>
       <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
       <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
@@ -618 +610 @@
             </ul>
          </li>
-         <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
          <li class="tocline0"><a href="#rfc.index">Index</a></li>
       </ul>
@@ -1411 +1402 @@
          <tr>
             <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td>
-            <td class="top">International Organization for Standardization, “
-               Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1
-               ”, ISO/IEC&nbsp;8859-1:1998, 1998.
-            </td>
+            <td class="top">International Organization for Standardization, “Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1”, ISO/IEC&nbsp;8859-1:1998, 1998.</td>
          </tr>
          <tr>
@@ -1535 +1523 @@
          <tr>
             <td class="reference"><b id="RFC2388">[RFC2388]</b></td>
-            <td class="top"><a title="Xerox Palo Alto Research Center">Masinter, L.</a>, “<a href="http://tools.ietf.org/html/rfc2388">Returning Values from Forms:  multipart/form-data</a>”, RFC&nbsp;2388, August&nbsp;1998.
+            <td class="top"><a title="Xerox Palo Alto Research Center">Masinter, L.</a>, “<a href="http://tools.ietf.org/html/rfc2388">Returning Values from Forms: multipart/form-data</a>”, RFC&nbsp;2388, August&nbsp;1998.
             </td>
          </tr>
@@ -1893 +1881 @@
          <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
       </ul>
-      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
-      <p>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>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, THE IETF TRUST 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>
-      <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>
-      <p>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>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 &lt;<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>&gt;.
-      </p>
-      <p>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@ietf.org">ietf-ipr@ietf.org</a>.
-      </p>
       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
       <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.U">U</a>