Ignore:
Timestamp:
Jul 22, 2010, 10:43:26 PM (9 years ago)
Author:
fielding@…
Message:

Addresses #109: Clarify entity / representation / variant terminology

Replace more entity, entities, and entity-body, as appropriate.

Addresses #183: "requested resource" in content-encoding definition

Fixed.

Clarifies #178: Content-MD5 and partial responses

New terminology makes it easier to understand what is digested.

File:
1 edited

Legend:

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

    r867 r874  
    654654</section>
    655655
    656 <section title="Representation" anchor="entity">
     656<section title="Representation" anchor="representation">
    657657<t>
    658658   Request and Response messages &MAY; transfer a representation if not otherwise
     
    779779</t>
    780780<t>
    781    If the OPTIONS request includes an entity-body (as indicated by the
     781   If the OPTIONS request includes a message-body (as indicated by the
    782782   presence of Content-Length or Transfer-Encoding), then the media type
    783783   &MUST; be indicated by a Content-Type field. Although this
     
    833833  <iref primary="true" item="Methods" subitem="GET" x:for-anchor=""/>
    834834<t>
    835    The GET method means retrieve whatever information (in the form of an
    836    entity) currently corresponds to the resource identified by the
     835   The GET method means retrieve whatever information (in the form of a
     836   representation) currently corresponds to the resource identified by the
    837837   Effective Request URI.
    838838</t>
     
    850850   circumstances described by the conditional header field(s). The
    851851   conditional GET method is intended to reduce unnecessary network
    852    usage by allowing cached entities to be refreshed without requiring
     852   usage by allowing cached representations to be refreshed without requiring
    853853   multiple requests or transferring data already held by the client.
    854854</t>
     
    889889   The response to a HEAD request &MAY; be cacheable in the sense that the
    890890   information contained in the response &MAY; be used to update a
    891    previously cached entity from that resource. If the new field values
    892    indicate that the cached entity differs from the current entity (as
     891   previously cached representation from that resource. If the new field values
     892   indicate that the cached representation differs from the current representation (as
    893893   would be indicated by a change in Content-Length, Content-MD5, ETag
    894894   or Last-Modified), then the cache &MUST; treat the cache entry as
     
    902902<t>
    903903   The POST method is used to request that the origin server accept the
    904    entity enclosed in the request as data to be processed by the resource
     904   representation enclosed in the request as data to be processed by the resource
    905905   identified by the Effective Request URI. POST is designed
    906906   to allow a uniform method to cover the following functions:
     
    930930   resource that can be identified by a URI. In this case, either 200
    931931   (OK) or 204 (No Content) is the appropriate response status,
    932    depending on whether or not the response includes an entity that
     932   depending on whether or not the response includes a representation that
    933933   describes the result.
    934934</t>
    935935<t>
    936936   If a resource has been created on the origin server, the response
    937    &SHOULD; be 201 (Created) and contain an entity which describes the
     937   &SHOULD; be 201 (Created) and contain a representation which describes the
    938938   status of the request and refers to the new resource, and a Location
    939939   header (see <xref target="header.location"/>).
     
    10301030<t>
    10311031   A successful response &SHOULD; be 200 (OK) if the response includes an
    1032    entity describing the status, 202 (Accepted) if the action has not
     1032   representation describing the status, 202 (Accepted) if the action has not
    10331033   yet been enacted, or 204 (No Content) if the action has been enacted
    10341034   but the response does not include a representation.
     
    10361036<t>
    10371037   If the request passes through a cache and the Effective Request URI
    1038    identifies one or more currently cached entities, those entries &SHOULD; be
    1039    treated as stale. Responses to this method are not cacheable.
     1038   identifies one or more currently cached representations, those entries &SHOULD; be
     1039   treated as stale. Responses to the DELETE method &MUST-NOT; be cached.
    10401040</t>
    10411041</section>
     
    10511051   of the request message. The final recipient of the request
    10521052   &SHOULD; reflect the message received back to the client as the
    1053    entity-body of a 200 (OK) response. The final recipient is either the
     1053   message-body of a 200 (OK) response. The final recipient is either the
    10541054   origin server or the first proxy or gateway to receive a Max-Forwards
    10551055   value of zero (0) in the request (see <xref target="header.max-forwards"/>).
     
    10661066</t>
    10671067<t>
    1068    If the request is valid, the response &SHOULD; contain the entire
    1069    request message in the entity-body, with a Content-Type of
    1070    "message/http" (see &media-type-message-http;). Responses to this method
    1071    &MUST-NOT; be cached.
     1068   If the request is valid, the response &SHOULD; have a Content-Type of
     1069   "message/http" (see &media-type-message-http;) and contain a message-body
     1070   that encloses a copy of the entire request message.
     1071   Responses to the TRACE method &MUST-NOT; be cached.
    10721072</t>
    10731073</section>
     
    11651165  <list style="hanging">
    11661166    <t hangText="GET">
    1167           an entity corresponding to the requested resource is sent in
     1167          a representation corresponding to the requested resource is sent in
    11681168          the response;
    11691169    </t>
     
    11731173    </t>
    11741174    <t hangText="POST">
    1175       an entity describing or containing the result of the action;
     1175      a representation describing or containing the result of the action;
    11761176    </t>
    11771177    <t hangText="TRACE">
    1178       an entity containing the request message as received by the
     1178      a representation containing the request message as received by the
    11791179      end server.
    11801180    </t>
     
    12011201<t>
    12021202   A 201 response &MAY; contain an ETag response header field indicating
    1203    the current value of the entity tag for the representation of the resource
     1203   the current value of the entity-tag for the representation of the resource
    12041204   just created (see &header-etag;).
    12051205</t>
     
    12921292<t>
    12931293   The server has fulfilled the partial GET request for the resource
    1294    and the enclosed entity is a partial representation as defined in &status-206;.
     1294   and the enclosed payload is a partial representation as defined in &status-206;.
    12951295</t>
    12961296</section>
     
    15251525   The 4xx class of status code is intended for cases in which the
    15261526   client seems to have erred. Except when responding to a HEAD request,
    1527    the server &SHOULD; include an entity containing an explanation of the
     1527   the server &SHOULD; include a representation containing an explanation of the
    15281528   error situation, and whether it is a temporary or permanent
    15291529   condition. These status codes are applicable to any request method.
    1530    User agents &SHOULD; display any included entity to the user.
     1530   User agents &SHOULD; display any included representation to the user.
    15311531</t>
    15321532<t>
     
    16141614<t>
    16151615   The resource identified by the request is only capable of generating
    1616    response entities which have content characteristics not acceptable
     1616   response representations which have content characteristics not acceptable
    16171617   according to the accept headers sent in the request.
    16181618</t>
     
    16711671   and resubmit the request. The response body &SHOULD; include enough
    16721672   information for the user to recognize the source of the conflict.
    1673    Ideally, the response entity would include enough information for the
     1673   Ideally, the response representation would include enough information for the
    16741674   user or user agent to fix the problem; however, that might not be
    16751675   possible and is not required.
     
    17411741<t>
    17421742   The server is refusing to process a request because the request
    1743    entity is larger than the server is willing or able to process. The
     1743   representation is larger than the server is willing or able to process. The
    17441744   server &MAY; close the connection to prevent the client from continuing
    17451745   the request.
     
    18081808   which the server is aware that it has erred or is incapable of
    18091809   performing the request. Except when responding to a HEAD request, the
    1810    server &SHOULD; include an entity containing an explanation of the
     1810   server &SHOULD; include a representation containing an explanation of the
    18111811   error situation, and whether it is a temporary or permanent
    1812    condition. User agents &SHOULD; display any included entity to the
     1812   condition. User agents &SHOULD; display any included representation to the
    18131813   user. These response codes are applicable to any request method.
    18141814</t>
     
    18901890   using the same major version as the client, as described in &http-version;,
    18911891   other than with this error message. The response &SHOULD; contain
    1892    an entity describing why that version is not supported and what other
     1892   a representation describing why that version is not supported and what other
    18931893   protocols are supported by that server.
    18941894</t>
Note: See TracChangeset for help on using the changeset viewer.