Changeset 874 for draft-ietf-httpbis/latest/p5-range.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/p5-range.xml (modified) (13 diffs)

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

@@ -316 +316 @@
 <t>
    HTTP/1.1 allows a client to request that only part (a range of) the
-   response entity be included within the response. HTTP/1.1 uses range
+   representation be included within the response. HTTP/1.1 uses range
    units in the Range (<xref target="header.range"/>) and Content-Range (<xref target="header.content-range"/>)
-   header fields. An entity can be broken down into subranges according
+   header fields. A representation can be broken down into subranges according
    to various structural units.
 </t>
@@ -412 +412 @@
 <section title="Combining Ranges" anchor="combining.byte.ranges">
 <t>
-   A response might transfer only a subrange of an entity-body, either because
+   A response might transfer only a subrange of a representation, either because
    the request included one or more Range specifications, or because 
-   a connection was broken prematurely.
+   a connection closed prematurely.
    After several such transfers, a cache might have received several 
-   ranges of the same entity-body.
+   ranges of the same representation.
 </t>
 <t>
@@ -498 +498 @@
   <x:anchor-alias value="other-range-resp-spec"/>
 <t>
-   The "Content-Range" entity-header field is sent with a partial entity-body to
-   specify where in the full entity-body the partial body should be
+   The "Content-Range" entity-header field is sent with a partial representation to
+   specify where in the full representation the partial body should be
    applied. Range units are defined in <xref target="range.units"/>.
 </t>
@@ -522 +522 @@
 </artwork></figure>
 <t>
-   The header &SHOULD; indicate the total length of the full entity-body,
+   The header &SHOULD; indicate the total length of the full representation,
    unless this length is unknown or difficult to determine. The asterisk
    "*" character means that the instance-length is unknown at the time
@@ -617 +617 @@
    invalid, the server &SHOULD; treat the request as if the invalid Range
    header field did not exist. (Normally, this means return a 200
-   response containing the full entity).
+   response containing the full representation).
 </t>
 <t>
@@ -643 +643 @@
   <x:anchor-alias value="If-Range-v"/>
 <t>
-   If a client has a partial copy of an entity in its cache, and wishes
-   to have an up-to-date copy of the entire entity in its cache, it
+   If a client has a partial copy of a representation in its cache, and wishes
+   to have an up-to-date copy of the entire representation in its cache, it
    could use the Range request-header with a conditional GET (using
    either or both of If-Unmodified-Since and If-Match.) However, if the
@@ -662 +662 @@
 </artwork></figure>
 <t>
-   If the client has no entity tag for a representation, 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
@@ -671 +671 @@
 </t>
 <t>
-   If the entity tag given in the If-Range header matches the current
+   If the entity-tag given in the If-Range header matches the current
    cache validator for the representation, then the server &SHOULD; provide the
    specified sub-range of the representation using a 206 (Partial Content)
@@ -744 +744 @@
    A suffix-byte-range-spec is used to specify the suffix of the
    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
+   this form specifies the last N bytes of a representation.) If the
    representation is shorter than the specified suffix-length, the entire
    representation is used.
@@ -751 +751 @@
    If a syntactically valid byte-range-set includes at least one byte-range-spec
    whose first-byte-pos is less than the current length of
-   the entity-body, or at least one suffix-byte-range-spec with a non-zero
+   the representation, or at least one suffix-byte-range-spec with a non-zero
    suffix-length, then the byte-range-set is satisfiable.
    Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set
@@ -760 +760 @@
 </t>
 <t>
-   Examples of byte-ranges-specifier values (assuming an entity-body of
+   Examples of byte-ranges-specifier values (assuming a representation of
    length 10000):
   <list style="symbols">
@@ -820 +820 @@
    possible, since Range supports efficient recovery from partially
    failed transfers, and supports efficient partial retrieval of large
-   entities.
+   representations.
 </t>
 <t>
    If the server supports the Range header and the specified range or
-   ranges are appropriate for the entity:
+   ranges are appropriate for the representation:
   <list style="symbols">
      <t>The presence of a Range header in an unconditional GET modifies
@@ -845 +845 @@
 <t>
    If a proxy that supports ranges receives a Range request, forwards
-   the request to an inbound server, and receives an entire entity in
+   the request to an inbound server, and receives an entire representation in
    reply, it &SHOULD; only return the requested range to its client. It
    &SHOULD; store the entire received response in its cache if that is