Ignore:
Timestamp:
Jul 29, 2010, 11:11:34 PM (9 years ago)
Author:
fielding@…
Message:

Addresses #109: Clarify entity / representation / variant terminology

Removed entity-header adjective and ABNF and clarified distinction
between payload and representation.

Uncapitalize the phrase effective request URI so that it doesn't
dominate the prose, and define the term "target resource" to be
used instead of the "resource identified by the effective request URI".

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r960 r965  
    312312  <x:anchor-alias value="weak"/>
    313313<t>
    314    Entity-tags are used for comparing two or more representations from the same
    315    requested resource. HTTP/1.1 uses entity-tags in the ETag (<xref target="header.etag"/>),
     314   Entity-tags are used for comparing two or more representations of the same
     315   resource. HTTP/1.1 uses entity-tags in the ETag (<xref target="header.etag"/>),
    316316   If-Match (<xref target="header.if-match"/>), If-None-Match (<xref target="header.if-none-match"/>), and
    317317   If-Range (&header-if-range;) header fields. The definition of how they
     
    725725   related to conditional requests.
    726726</t>
    727 <t>
    728    For entity-header fields, both sender and recipient refer to either the
    729    client or the server, depending on who sends and who receives the message.
    730 </t>
    731727
    732728<section title="ETag" anchor="header.etag">
     
    738734   The "ETag" response-header field provides the current value of the
    739735   entity-tag (see <xref target="entity.tags"/>) for one representation of
    740    the resource identified by the Effective Request URI.  An entity-tag
     736   the resource identified by the effective request URI.  An entity-tag
    741737   is intended for use as a resource-local identifier for differentiating
    742738   between representations of the same resource that vary over time or via
     
    10581054  <x:anchor-alias value="Last-Modified-v"/>
    10591055<t>
    1060    The "Last-Modified" entity-header field indicates the date and time at
     1056   The "Last-Modified" header field indicates the date and time at
    10611057   which the origin server believes the representation was last modified.
    10621058</t>
     
    10981094</t>
    10991095<t>
    1100    The Last-Modified entity-header field value is often used as a cache
     1096   The Last-Modified header field value is often used as a cache
    11011097   validator. In simple terms, a cache entry is considered to be valid
    11021098   if the representation has not been modified since the Last-Modified value.
Note: See TracChangeset for help on using the changeset viewer.