Ignore:
Timestamp:
Aug 2, 2010, 6:20:54 AM (9 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:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r971 r972  
    433433  <x:anchor-alias value="extension-method"/>
    434434<t>
    435    The Method token indicates the method to be performed on the resource
    436    identified by the effective request URI (&effective-request-uri;). The
    437    method is case-sensitive.
     435   The Method token indicates the method to be performed on the target
     436   resource (&effective-request-uri;). The method is case-sensitive.
    438437</t>
    439438<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Method"/><iref primary="true" item="Grammar" subitem="extension-method"/>
     
    634633   information about the response which cannot be placed in the Status-Line.
    635634   These header fields give information about the server and about
    636    further access to the resource identified by the effective request URI
    637    (&effective-request-uri;).
     635   further access to the target resource (&effective-request-uri;).
    638636</t>
    639637<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="response-header"/>
     
    684682</t>
    685683<t>
    686    In the common case, an HTTP response is a representation of the resource
    687    located at the effective request URI (see &effective-request-uri;). However,
    688    this is not always the case. To determine the URI of the resource a
    689    response is associated with, the following rules are used (with the first
    690    applicable one being selected):
     684   In the common case, an HTTP response is a representation of the target
     685   resource (see &effective-request-uri;). However, this is not always the
     686   case. To determine the URI of the resource a response is associated with,
     687   the following rules are used (with the first applicable one being selected):
    691688</t>
    692689<t><list style="numbers">
    693690   <t>If the response status code is 200 or 203 and the request method was GET,
    694    the response payload is a representation of the resource identified by the effective request URI.</t>
     691   the response payload is a representation of the target resource.</t>
    695692   <t>If the response status code is 204, 206, or 304 and the request method was GET
    696    or HEAD, the response payload is a partial representation of the resource identified
    697    by the effective request URI (see &caching-combining-headers;).</t>
     693   or HEAD, the response payload is a partial representation of the target
     694   (see &caching-combining-headers;).</t>
    698695   <t>If the response has a Content-Location header, and that URI is the same
    699696   as the effective request URI, the response payload is a representation of the
    700    resource identified by the effective request URI.</t>
     697   target resource.</t>
    701698   <t>If the response has a Content-Location header, and that URI is not the
    702699   same as the effective request URI, then the response asserts that its
     
    833830<t>
    834831   The GET method means retrieve whatever information (in the form of a
    835    representation) currently corresponds to the resource identified by the
    836    effective request URI.
     832   representation) currently corresponds to the target resource.
    837833</t>
    838834<t>   
    839    If the effective request URI identifies a data-producing process, it is the
     835   If the target resource is a data-producing process, it is the
    840836   produced data which shall be returned as the representation in the response and not
    841837   the source text of the process, unless that text happens to be the output of
     
    901897<t>
    902898   The POST method is used to request that the origin server accept the
    903    representation enclosed in the request as data to be processed by the resource
    904    identified by the effective request URI. POST is designed
    905    to allow a uniform method to cover the following functions:
     899   representation enclosed in the request as data to be processed by the
     900   target resource. POST is designed to allow a uniform method to cover the
     901   following functions:
    906902  <list style="symbols">
    907903    <t>
     
    942938   include explicit freshness information (see &p6-explicit;). A
    943939   cached POST response with a Content-Location header
    944    (see &header-content-location;) whose value is the Effective
     940   (see &header-content-location;) whose value is the effective
    945941   Request URI &MAY; be used to satisfy subsequent GET and HEAD requests.
    946942</t>
     
    972968</t>
    973969<t>   
    974    If the resource identified by the effective request URI could not be
    975    created or modified, an appropriate error response &SHOULD; be given
    976    that reflects the nature of the problem.
     970   If the target resource could not be created or modified, an appropriate
     971   error response &SHOULD; be given that reflects the nature of the problem.
    977972   The recipient of the representation &MUST-NOT; ignore any Content-*
    978973   headers (headers starting with the prefix "Content-") that it does
     
    10241019  <iref primary="true" item="Methods" subitem="DELETE" x:for-anchor=""/>
    10251020<t>
    1026    The DELETE method requests that the origin server delete the resource
    1027    identified by the effective request URI. This method &MAY; be overridden by
     1021   The DELETE method requests that the origin server delete the target
     1022   resource. This method &MAY; be overridden by
    10281023   human intervention (or other means) on the origin server. The client cannot
    10291024   be guaranteed that the operation has been carried out, even if the
     
    11711166  <list style="hanging">
    11721167    <t hangText="GET">
    1173           a representation of the resource corresponding to the effective
    1174           request URI is sent in the response;
     1168          a representation of the target resource is sent in the response;
    11751169    </t>
    11761170    <t hangText="HEAD">
Note: See TracChangeset for help on using the changeset viewer.