Changeset 1079 for draft-ietf-httpbis

Timestamp:

07/11/10 15:55:57 (10 years ago)

Author:

julian.reschke@…

Message:

fix typo ('target' -> 'target resource') (see #110)

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (5 diffs)
• p2-semantics.xml (modified) (1 diff)

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

@@ -403 +403 @@
       <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="2010-11-01">
+      <meta name="dct.issued" scheme="ISO8601" content="2010-11-07">
       <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, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and response-header fields.">
@@ -434 +434 @@
             </tr>
             <tr>
-               <td class="left">Expires: May 5, 2011</td>
+               <td class="left">Expires: May 11, 2011</td>
                <td class="right">HP</td>
             </tr>
@@ -487 +487 @@
             <tr>
                <td class="left"></td>
-               <td class="right">November 1, 2010</td>
+               <td class="right">November 7, 2010</td>
             </tr>
          </tbody>
@@ -514 +514 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on May 5, 2011.</p>
+      <p>This Internet-Draft will expire on May 11, 2011.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -962 +962 @@
          </li>
          <li>If the response status code is 204, 206, or 304 and the request method was GET or HEAD, the response payload is a partial
-            representation of the target (see <a href="p6-cache.html#combining.responses" title="Combining Responses">Section 2.8</a> of <a href="#Part6" id="rfc.xref.Part6.7"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
+            representation of the target resource (see <a href="p6-cache.html#combining.responses" title="Combining Responses">Section 2.8</a> of <a href="#Part6" id="rfc.xref.Part6.7"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
          </li>
          <li>If the response has a Content-Location header field, and that URI is the same as the effective request URI, the response payload

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

@@ -759 +759 @@
    <t>If the response status code is 204, 206, or 304 and the request method was GET
    or HEAD, the response payload is a partial representation of the target
-   (see &combining-responses;).</t>
+   resource (see &combining-responses;).</t>
    <t>If the response has a Content-Location header field, and that URI is the same
    as the effective request URI, the response payload is a representation of the