Changeset 1786 for draft-ietf-httpbis/latest

Timestamp:

15/07/12 08:31:40 (10 years ago)

Author:

fielding@…

Message:

reference all of p1 instead of just architecture

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (1 diff)
• p2-semantics.html (modified) (6 diffs)
• p2-semantics.xml (modified) (1 diff)
• p4-conditional.html (modified) (7 diffs)
• p4-conditional.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p1-messaging.html

@@ -756 +756 @@
          </li>
       </ul>
-      <p id="rfc.section.1.p.2">This HTTP/1,1 specification obsoletes and moves to historic status <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">RFC 2616</cite>, its predecessor <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.1">RFC 2068</cite>, <cite title="Use and Interpretation of HTTP Version Numbers" id="rfc.xref.RFC2145.1">RFC 2145</cite> (on HTTP versioning), and <cite title="Upgrading to TLS Within HTTP/1.1" id="rfc.xref.RFC2817.1">2817</cite> (on using CONNECT for TLS upgrades).
+      <p id="rfc.section.1.p.2">This HTTP/1,1 specification obsoletes and moves to historic status <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">RFC 2616</cite>, its predecessor <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2068.1">RFC 2068</cite>, <cite title="Use and Interpretation of HTTP Version Numbers" id="rfc.xref.RFC2145.1">RFC 2145</cite> (on HTTP versioning), and <cite title="Upgrading to TLS Within HTTP/1.1" id="rfc.xref.RFC2817.1">RFC 2817</cite> (on using CONNECT for TLS upgrades).
       </p>
       <p id="rfc.section.1.p.3">HTTP is a generic interface protocol for information systems. It is designed to hide the details of how a service is implemented

draft-ietf-httpbis/latest/p2-semantics.html

@@ -449 +449 @@
   } 
   @bottom-center {
-       content: "Expires January 15, 2013"; 
+       content: "Expires January 16, 2013"; 
   } 
   @bottom-right {
@@ -498 +498 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2012-07-14">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-07-15">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
@@ -529 +529 @@
             </tr>
             <tr>
-               <td class="left">Expires: January 15, 2013</td>
+               <td class="left">Expires: January 16, 2013</td>
                <td class="right">greenbytes</td>
             </tr>
             <tr>
                <td class="left"></td>
-               <td class="right">July 14, 2012</td>
+               <td class="right">July 15, 2012</td>
             </tr>
          </tbody>
@@ -561 +561 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on January 15, 2013.</p>
+      <p>This Internet-Draft will expire on January 16, 2013.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -805 +805 @@
          interprets the message semantics in relation to the identified request target, and responds to that request with one or more
          response messages. This document defines HTTP/1.1 request and response semantics in terms of the architecture, syntax notation,
-         and conformance criteria defined in <a href="p1-messaging.html#architecture" title="Architecture">Section 2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
+         and conformance criteria defined in <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
       </p>
       <p id="rfc.section.1.p.2">HTTP provides a uniform interface for interacting with resources regardless of their type, nature, or implementation. HTTP
@@ -4896 +4896 @@
                   <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">2</a>, <a href="#rfc.xref.Part1.3">2.2.1</a>, <a href="#rfc.xref.Part1.4">2.3.1</a>, <a href="#rfc.xref.Part1.5">2.3.7</a>, <a href="#rfc.xref.Part1.6">2.3.7</a>, <a href="#rfc.xref.Part1.7">2.3.8</a>, <a href="#rfc.xref.Part1.8">3</a>, <a href="#rfc.xref.Part1.9">3.1</a>, <a href="#rfc.xref.Part1.10">3.1</a>, <a href="#rfc.xref.Part1.11">3.1</a>, <a href="#rfc.xref.Part1.12">3.1</a>, <a href="#rfc.xref.Part1.13">3.1</a>, <a href="#rfc.xref.Part1.14">3.2</a>, <a href="#rfc.xref.Part1.15">3.2</a>, <a href="#rfc.xref.Part1.16">3.3</a>, <a href="#rfc.xref.Part1.17">4.3.1</a>, <a href="#rfc.xref.Part1.18">4.3.2</a>, <a href="#rfc.xref.Part1.19">4.4.4</a>, <a href="#rfc.xref.Part1.20">4.4.6</a>, <a href="#rfc.xref.Part1.21">4.6.15</a>, <a href="#rfc.xref.Part1.22">4.7.6</a>, <a href="#rfc.xref.Part1.23">5.4</a>, <a href="#rfc.xref.Part1.24">5.4</a>, <a href="#rfc.xref.Part1.25">5.4</a>, <a href="#rfc.xref.Part1.26">5.4.1</a>, <a href="#rfc.xref.Part1.27">5.4.1</a>, <a href="#rfc.xref.Part1.28">6.1</a>, <a href="#rfc.xref.Part1.29">6.2</a>, <a href="#rfc.xref.Part1.30">7</a>, <a href="#rfc.xref.Part1.31">7.1</a>, <a href="#rfc.xref.Part1.32">8.1</a>, <a href="#rfc.xref.Part1.33">9.1</a>, <a href="#rfc.xref.Part1.34">9.3</a>, <a href="#rfc.xref.Part1.35">9.8</a>, <a href="#rfc.xref.Part1.36">9.11</a>, <a href="#rfc.xref.Part1.37">9.17</a>, <a href="#rfc.xref.Part1.38">9.17</a>, <a href="#rfc.xref.Part1.39">9.18</a>, <a href="#rfc.xref.Part1.40">10</a>, <a href="#rfc.xref.Part1.41">10</a>, <a href="#rfc.xref.Part1.42">10</a>, <a href="#rfc.xref.Part1.43">10</a>, <a href="#rfc.xref.Part1.44">10</a>, <a href="#rfc.xref.Part1.45">10</a>, <a href="#rfc.xref.Part1.46">10</a>, <a href="#rfc.xref.Part1.47">10</a>, <a href="#rfc.xref.Part1.48">10</a>, <a href="#rfc.xref.Part1.49">10</a>, <a href="#rfc.xref.Part1.50">10</a>, <a href="#rfc.xref.Part1.51">10</a>, <a href="#rfc.xref.Part1.52">11.4</a>, <a href="#rfc.xref.Part1.53">11.4</a>, <a href="#rfc.xref.Part1.54">11.4</a>, <a href="#rfc.xref.Part1.55">13</a>, <a href="#Part1"><b>14.1</b></a>, <a href="#rfc.xref.Part1.56">C</a><ul>
                         <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.40">10</a></li>
-                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1</a></li>
                         <li><em>Section 2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.19">4.4.4</a></li>
                         <li><em>Section 2.7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.22">4.7.6</a></li>

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -221 +221 @@
    This document defines HTTP/1.1 request and response semantics in terms of
    the architecture, syntax notation, and conformance criteria defined in
-   &architecture;.
+   <xref target="Part1"/>.
 </t>
 <t>

draft-ietf-httpbis/latest/p4-conditional.html

@@ -449 +449 @@
   } 
   @bottom-center {
-       content: "Expires January 15, 2013"; 
+       content: "Expires January 16, 2013"; 
   } 
   @bottom-right {
@@ -491 +491 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2012-07-14">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-07-15">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP/1.1 conditional requests, including metadata header fields for indicating state changes, request header fields for making preconditions on such state, and rules for constructing the responses to a conditional request when one or more preconditions evaluate to false.">
@@ -517 +517 @@
             </tr>
             <tr>
-               <td class="left">Expires: January 15, 2013</td>
+               <td class="left">Expires: January 16, 2013</td>
                <td class="right">J. Reschke, Editor</td>
             </tr>
@@ -526 +526 @@
             <tr>
                <td class="left"></td>
-               <td class="right">July 14, 2012</td>
+               <td class="right">July 15, 2012</td>
             </tr>
          </tbody>
@@ -553 +553 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on January 15, 2013.</p>
+      <p>This Internet-Draft will expire on January 16, 2013.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -627 +627 @@
          target resource. Each precondition is based on metadata that is expected to change if the selected representation of the target
          resource is changed. This document defines the HTTP/1.1 conditional request mechanisms in terms of the architecture, syntax
-         notation, and conformance criteria defined in <a href="p1-messaging.html#architecture" title="Architecture">Section 2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
+         notation, and conformance criteria defined in <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
       </p>
       <p id="rfc.section.1.p.2">Conditional GET requests are the most efficient mechanism for HTTP cache updates <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>. Conditionals can also be applied to state-changing methods, such as PUT and DELETE, to prevent the "lost update" problem:
@@ -1377 +1377 @@
                   <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">2.3.3</a>, <a href="#rfc.xref.Part1.3">5</a>, <a href="#rfc.xref.Part1.4">5</a>, <a href="#rfc.xref.Part1.5">5</a>, <a href="#rfc.xref.Part1.6">5</a>, <a href="#rfc.xref.Part1.7">7</a>, <a href="#rfc.xref.Part1.8">8</a>, <a href="#Part1"><b>9.1</b></a><ul>
                         <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.3">5</a></li>
-                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1</a></li>
                         <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">5</a></li>
                         <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">5</a></li>

draft-ietf-httpbis/latest/p4-conditional.xml

@@ -141 +141 @@
    This document defines the HTTP/1.1 conditional request mechanisms in terms
    of the architecture, syntax notation, and conformance criteria defined in
-   &architecture;.
+   <xref target="Part1"/>.
 </t>
 <t>