Changeset 866 for draft-ietf-httpbis/latest/p5-range.xml

Timestamp:

22/07/10 09:06:27 (13 years ago)

Author:

fielding@…

Message:

Addresses #109: Clarify entity / representation / variant terminology

Replaced entity with representation.

File:

• draft-ietf-httpbis/latest/p5-range.xml (modified) (13 diffs)

draft-ietf-httpbis/latest/p5-range.xml

@@ -419 +419 @@
 </t>
 <t>
-   If a cache has a stored non-empty set of subranges for an entity, and
+   If a cache has a stored non-empty set of subranges for a representation, and
    an incoming response transfers another subrange, the cache &MAY;
    combine the new subrange with the existing set if both the following
@@ -445 +445 @@
 <t>
    For entity-header fields, both sender and recipient refer to either the
-   client or the server, depending on who sends and who receives the entity.
+   client or the server, depending on who sends and who receives the message.
 </t>
 
@@ -549 +549 @@
 </t>
 <t>
-   Examples of byte-content-range-spec values, assuming that the entity
+   Examples of byte-content-range-spec values, assuming that the representation
    contains a total of 1234 bytes:
    <list style="symbols">
@@ -647 +647 @@
    could use the Range request-header with a conditional GET (using
    either or both of If-Unmodified-Since and If-Match.) However, if the
-   condition fails because the entity has been modified, the client
+   condition fails because the representation has been modified, the client
    would then have to make a second request to obtain the entire current
-   entity-body.
+   representation.
 </t>
 <t>
    The "If-Range" request-header field allows a client to "short-circuit" the second
-   request. Informally, its meaning is "if the entity is unchanged, send
+   request. Informally, its meaning is "if the representation is unchanged, send
    me the part(s) that I am missing; otherwise, send me the entire new
-   entity".
+   representation".
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-Range"/><iref primary="true" item="Grammar" subitem="If-Range-v"/>
@@ -662 +662 @@
 </artwork></figure>
 <t>
-   If the client has no entity tag for an entity, but does have a Last-Modified
+   If the client has no entity tag for a representation, but does have a Last-Modified
    date, it &MAY; use that date in an If-Range header. (The
    server can distinguish between a valid HTTP-date and any form of
@@ -672 +672 @@
 <t>
    If the entity tag given in the If-Range header matches the current
-   cache validator for the entity, then the server &SHOULD; provide the
-   specified sub-range of the entity using a 206 (Partial Content)
+   cache validator for the representation, then the server &SHOULD; provide the
+   specified sub-range of the representation using a 206 (Partial Content)
    response. If the cache validator does not match, then the server &SHOULD;
-   return the entire entity using a 200 (OK) response.
+   return the entire representation using a 200 (OK) response.
 </t>
 </section>
@@ -685 +685 @@
 <section title="Byte Ranges" anchor="byte.ranges">
 <t>
-   Since all HTTP entities are represented in HTTP messages as sequences
+   Since all HTTP representations are transferred as sequences
    of bytes, the concept of a byte range is meaningful for any HTTP
-   entity. (However, not all clients and servers need to support byte-range
+   representation. (However, not all clients and servers need to support byte-range
    operations.)
 </t>
 <t>
    Byte range specifications in HTTP apply to the sequence of bytes in
-   the entity-body (not necessarily the same as the message-body).
+   the representation body (not necessarily the same as the message-body).
 </t>
 <t anchor="rule.ranges-specifier">
@@ -705 +705 @@
 
    A byte range operation &MAY; specify a single range of bytes, or a set
-   of ranges within a single entity.
+   of ranges within a single representation.
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="ranges-specifier"/><iref primary="true" item="Grammar" subitem="byte-ranges-specifier"/><iref primary="true" item="Grammar" subitem="byte-range-set"/><iref primary="true" item="Grammar" subitem="byte-range-spec"/><iref primary="true" item="Grammar" subitem="first-byte-pos"/><iref primary="true" item="Grammar" subitem="last-byte-pos"/>
@@ -729 +729 @@
 <t>
    If the last-byte-pos value is absent, or if the value is greater than
-   or equal to the current length of the entity-body, last-byte-pos is
-   taken to be equal to one less than the current length of the entity-body
+   or equal to the current length of the representation body, last-byte-pos is
+   taken to be equal to one less than the current length of the representation
    in bytes.
 </t>
 <t>
    By its choice of last-byte-pos, a client can limit the number of
-   bytes retrieved without knowing the size of the entity.
+   bytes retrieved without knowing the size of the representation.
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="suffix-byte-range-spec"/><iref primary="true" item="Grammar" subitem="suffix-length"/>
@@ -743 +743 @@
 <t>
    A suffix-byte-range-spec is used to specify the suffix of the
-   entity-body, of a length given by the suffix-length value. (That is,
+   representation body, of a length given by the suffix-length value. (That is,
    this form specifies the last N bytes of an entity-body.) If the
-   entity is shorter than the specified suffix-length, the entire
-   entity-body is used.
+   representation is shorter than the specified suffix-length, the entire
+   representation is used.
 </t>
 <t>
@@ -757 +757 @@
    of 416 (Requested range not satisfiable). Otherwise, the server
    &SHOULD; return a response with a status of 206 (Partial Content)
-   containing the satisfiable ranges of the entity-body.
+   containing the satisfiable ranges of the representation.
 </t>
 <t>
@@ -805 +805 @@
 <t>
    The "Range" request-header field defines the GET method (conditional or
-   not) to request one or more sub-ranges of the response entity-body, instead
-   of the entire entity body.
+   not) to request one or more sub-ranges of the response representation body, instead
+   of the entire representation body.
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Range"/>
@@ -1287 +1287 @@
       Notes:
   <list style="numbers">
-      <t>Additional CRLFs may precede the first boundary string in the
-         entity.</t>
+      <t>Additional CRLFs may precede the first boundary string in the body.</t>
 
       <t>Although <xref target="RFC2046"/> permits the boundary string to be