Changeset 972 for draft-ietf-httpbis/latest/p2-semantics.xml

Timestamp:

02/08/10 13:20:54 (12 years ago)

Author:

julian.reschke@…

Message:

lowercase "effective request URI" throughout, use "target resource" instead of "resource identified by the effective request URI" where possible.

File:

• draft-ietf-httpbis/latest/p2-semantics.xml (modified) (9 diffs)

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

@@ -433 +433 @@
   <x:anchor-alias value="extension-method"/>
 <t>
-   The Method token indicates the method to be performed on the resource
-   identified by the effective request URI (&effective-request-uri;). The
-   method is case-sensitive.
+   The Method token indicates the method to be performed on the target
+   resource (&effective-request-uri;). The method is case-sensitive.
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Method"/><iref primary="true" item="Grammar" subitem="extension-method"/>
@@ -634 +633 @@
    information about the response which cannot be placed in the Status-Line.
    These header fields give information about the server and about
-   further access to the resource identified by the effective request URI
-   (&effective-request-uri;).
+   further access to the target resource (&effective-request-uri;).
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="response-header"/>
@@ -684 +682 @@
 </t>
 <t>
-   In the common case, an HTTP response is a representation of the resource
-   located at the effective request URI (see &effective-request-uri;). However,
-   this is not always the case. To determine the URI of the resource a
-   response is associated with, the following rules are used (with the first
-   applicable one being selected):
+   In the common case, an HTTP response is a representation of the target
+   resource (see &effective-request-uri;). However, this is not always the
+   case. To determine the URI of the resource a response is associated with,
+   the following rules are used (with the first applicable one being selected):
 </t>
 <t><list style="numbers">
    <t>If the response status code is 200 or 203 and the request method was GET,
-   the response payload is a representation of the resource identified by the effective request URI.</t>
+   the response payload is a representation of the target resource.</t>
    <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 resource identified
-   by the effective request URI (see &caching-combining-headers;).</t>
+   or HEAD, the response payload is a partial representation of the target
+   (see &caching-combining-headers;).</t>
    <t>If the response has a Content-Location header, and that URI is the same
    as the effective request URI, the response payload is a representation of the
-   resource identified by the effective request URI.</t>
+   target resource.</t>
    <t>If the response has a Content-Location header, and that URI is not the
    same as the effective request URI, then the response asserts that its
@@ -833 +830 @@
 <t>
    The GET method means retrieve whatever information (in the form of a
-   representation) currently corresponds to the resource identified by the
-   effective request URI.
+   representation) currently corresponds to the target resource.
 </t>
 <t>   
-   If the effective request URI identifies a data-producing process, it is the
+   If the target resource is a data-producing process, it is the
    produced data which shall be returned as the representation in the response and not
    the source text of the process, unless that text happens to be the output of
@@ -901 +897 @@
 <t>
    The POST method is used to request that the origin server accept the
-   representation enclosed in the request as data to be processed by the resource
-   identified by the effective request URI. POST is designed
-   to allow a uniform method to cover the following functions:
+   representation enclosed in the request as data to be processed by the 
+   target resource. POST is designed to allow a uniform method to cover the
+   following functions:
   <list style="symbols">
     <t>
@@ -942 +938 @@
    include explicit freshness information (see &p6-explicit;). A
    cached POST response with a Content-Location header 
-   (see &header-content-location;) whose value is the Effective 
+   (see &header-content-location;) whose value is the effective 
    Request URI &MAY; be used to satisfy subsequent GET and HEAD requests.
 </t>
@@ -972 +968 @@
 </t>
 <t>   
-   If the resource identified by the effective request URI could not be
-   created or modified, an appropriate error response &SHOULD; be given
-   that reflects the nature of the problem.
+   If the target resource could not be created or modified, an appropriate
+   error response &SHOULD; be given that reflects the nature of the problem.
    The recipient of the representation &MUST-NOT; ignore any Content-*
    headers (headers starting with the prefix "Content-") that it does
@@ -1024 +1019 @@
   <iref primary="true" item="Methods" subitem="DELETE" x:for-anchor=""/>
 <t>
-   The DELETE method requests that the origin server delete the resource
-   identified by the effective request URI. This method &MAY; be overridden by
+   The DELETE method requests that the origin server delete the target
+   resource. This method &MAY; be overridden by
    human intervention (or other means) on the origin server. The client cannot
    be guaranteed that the operation has been carried out, even if the
@@ -1171 +1166 @@
   <list style="hanging">
     <t hangText="GET">
-          a representation of the resource corresponding to the effective
-          request URI is sent in the response;
+          a representation of the target resource is sent in the response;
     </t>
     <t hangText="HEAD">