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

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:

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

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

@@ -654 +654 @@
 </section>
 
-<section title="Representation" anchor="entity">
+<section title="Representation" anchor="representation">
 <t>
    Request and Response messages &MAY; transfer a representation if not otherwise
@@ -779 +779 @@
 </t>
 <t>
-   If the OPTIONS request includes an entity-body (as indicated by the
+   If the OPTIONS request includes a message-body (as indicated by the
    presence of Content-Length or Transfer-Encoding), then the media type
    &MUST; be indicated by a Content-Type field. Although this
@@ -833 +833 @@
   <iref primary="true" item="Methods" subitem="GET" x:for-anchor=""/>
 <t>
-   The GET method means retrieve whatever information (in the form of an
-   entity) currently corresponds to the resource identified by the
+   The GET method means retrieve whatever information (in the form of a
+   representation) currently corresponds to the resource identified by the
    Effective Request URI.
 </t>
@@ -850 +850 @@
    circumstances described by the conditional header field(s). The
    conditional GET method is intended to reduce unnecessary network
-   usage by allowing cached entities to be refreshed without requiring
+   usage by allowing cached representations to be refreshed without requiring
    multiple requests or transferring data already held by the client.
 </t>
@@ -889 +889 @@
    The response to a HEAD request &MAY; be cacheable in the sense that the
    information contained in the response &MAY; be used to update a
-   previously cached entity from that resource. If the new field values
-   indicate that the cached entity differs from the current entity (as
+   previously cached representation from that resource. If the new field values
+   indicate that the cached representation differs from the current representation (as
    would be indicated by a change in Content-Length, Content-MD5, ETag
    or Last-Modified), then the cache &MUST; treat the cache entry as
@@ -902 +902 @@
 <t>
    The POST method is used to request that the origin server accept the
-   entity enclosed in the request as data to be processed by the resource
+   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:
@@ -930 +930 @@
    resource that can be identified by a URI. In this case, either 200
    (OK) or 204 (No Content) is the appropriate response status,
-   depending on whether or not the response includes an entity that
+   depending on whether or not the response includes a representation that
    describes the result.
 </t>
 <t>
    If a resource has been created on the origin server, the response
-   &SHOULD; be 201 (Created) and contain an entity which describes the
+   &SHOULD; be 201 (Created) and contain a representation which describes the
    status of the request and refers to the new resource, and a Location
    header (see <xref target="header.location"/>).
@@ -1030 +1030 @@
 <t>
    A successful response &SHOULD; be 200 (OK) if the response includes an
-   entity describing the status, 202 (Accepted) if the action has not
+   representation describing the status, 202 (Accepted) if the action has not
    yet been enacted, or 204 (No Content) if the action has been enacted
    but the response does not include a representation.
@@ -1036 +1036 @@
 <t>
    If the request passes through a cache and the Effective Request URI
-   identifies one or more currently cached entities, those entries &SHOULD; be
-   treated as stale. Responses to this method are not cacheable.
+   identifies one or more currently cached representations, those entries &SHOULD; be
+   treated as stale. Responses to the DELETE method &MUST-NOT; be cached.
 </t>
 </section>
@@ -1051 +1051 @@
    of the request message. The final recipient of the request
    &SHOULD; reflect the message received back to the client as the
-   entity-body of a 200 (OK) response. The final recipient is either the
+   message-body of a 200 (OK) response. The final recipient is either the
    origin server or the first proxy or gateway to receive a Max-Forwards
    value of zero (0) in the request (see <xref target="header.max-forwards"/>).
@@ -1066 +1066 @@
 </t>
 <t>
-   If the request is valid, the response &SHOULD; contain the entire
-   request message in the entity-body, with a Content-Type of
-   "message/http" (see &media-type-message-http;). Responses to this method
-   &MUST-NOT; be cached.
+   If the request is valid, the response &SHOULD; have a Content-Type of
+   "message/http" (see &media-type-message-http;) and contain a message-body
+   that encloses a copy of the entire request message.
+   Responses to the TRACE method &MUST-NOT; be cached.
 </t>
 </section>
@@ -1165 +1165 @@
   <list style="hanging">
     <t hangText="GET">
-          an entity corresponding to the requested resource is sent in
+          a representation corresponding to the requested resource is sent in
           the response;
     </t>
@@ -1173 +1173 @@
     </t>
     <t hangText="POST">
-      an entity describing or containing the result of the action;
+      a representation describing or containing the result of the action;
     </t>
     <t hangText="TRACE">
-      an entity containing the request message as received by the
+      a representation containing the request message as received by the
       end server.
     </t>
@@ -1201 +1201 @@
 <t>
    A 201 response &MAY; contain an ETag response header field indicating
-   the current value of the entity tag for the representation of the resource
+   the current value of the entity-tag for the representation of the resource
    just created (see &header-etag;).
 </t>
@@ -1292 +1292 @@
 <t>
    The server has fulfilled the partial GET request for the resource
-   and the enclosed entity is a partial representation as defined in &status-206;.
+   and the enclosed payload is a partial representation as defined in &status-206;.
 </t>
 </section>
@@ -1525 +1525 @@
    The 4xx class of status code is intended for cases in which the
    client seems to have erred. Except when responding to a HEAD request,
-   the server &SHOULD; include an entity containing an explanation of the
+   the server &SHOULD; include a representation containing an explanation of the
    error situation, and whether it is a temporary or permanent
    condition. These status codes are applicable to any request method.
-   User agents &SHOULD; display any included entity to the user.
+   User agents &SHOULD; display any included representation to the user.
 </t>
 <t>
@@ -1614 +1614 @@
 <t>
    The resource identified by the request is only capable of generating
-   response entities which have content characteristics not acceptable
+   response representations which have content characteristics not acceptable
    according to the accept headers sent in the request.
 </t>
@@ -1671 +1671 @@
    and resubmit the request. The response body &SHOULD; include enough
    information for the user to recognize the source of the conflict.
-   Ideally, the response entity would include enough information for the
+   Ideally, the response representation would include enough information for the
    user or user agent to fix the problem; however, that might not be
    possible and is not required.
@@ -1741 +1741 @@
 <t>
    The server is refusing to process a request because the request
-   entity is larger than the server is willing or able to process. The
+   representation is larger than the server is willing or able to process. The
    server &MAY; close the connection to prevent the client from continuing
    the request.
@@ -1808 +1808 @@
    which the server is aware that it has erred or is incapable of
    performing the request. Except when responding to a HEAD request, the
-   server &SHOULD; include an entity containing an explanation of the
+   server &SHOULD; include a representation containing an explanation of the
    error situation, and whether it is a temporary or permanent
-   condition. User agents &SHOULD; display any included entity to the
+   condition. User agents &SHOULD; display any included representation to the
    user. These response codes are applicable to any request method.
 </t>
@@ -1890 +1890 @@
    using the same major version as the client, as described in &http-version;,
    other than with this error message. The response &SHOULD; contain
-   an entity describing why that version is not supported and what other
+   a representation describing why that version is not supported and what other
    protocols are supported by that server.
 </t>