Changeset 965 for draft-ietf-httpbis/latest/p6-cache.xml

Timestamp:

30/07/10 06:11:34 (10 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:

• draft-ietf-httpbis/latest/p6-cache.xml (modified) (5 diffs)

draft-ietf-httpbis/latest/p6-cache.xml

@@ -504 +504 @@
    unless:
    <list style="symbols">
-      <t>The presented Effective Request URI (&effective-request-uri;) and
+      <t>The presented effective request URI (&effective-request-uri;) and
       that of the stored response match, and</t>
       <t>the request method associated with the stored response allows it to
@@ -868 +868 @@
    An invalidation based on a URI from a Location or Content-Location header
    &MUST-NOT; be performed if the host part of that URI differs from the host
-   part in the Effective Request URI (&effective-request-uri;). This helps
+   part in the effective request URI (&effective-request-uri;). This helps
    prevent denial of service attacks.
 </t>
 <t>
    A cache that passes through requests for methods it does not understand
-   &SHOULD; invalidate the Effective Request URI (&effective-request-uri;).
+   &SHOULD; invalidate the effective request URI (&effective-request-uri;).
 </t>
 <t>
    Here, "invalidate" means that the cache will either remove all stored
-   responses related to the Effective Request URI, or will mark these as
+   responses related to the effective request URI, or will mark these as
    "invalid" and in need of a mandatory validation before they can be returned
    in response to a subsequent request.
@@ -1010 +1010 @@
    related to caching.
 </t>
-<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 message.
-</t>
 
 <section anchor="header.age" title="Age">
@@ -1435 +1431 @@
    <x:anchor-alias value="Expires-v"/>
 <t>
-   The "Expires" entity-header field gives the date/time after which the
+   The "Expires" header field gives the date/time after which the
    response is considered stale. See <xref target="expiration.model" /> for
    further discussion of the freshness model.
@@ -2608 +2604 @@
   <list style="symbols"> 
     <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/109"/>:
+      "Clarify entity / representation / variant terminology"
+    </t>
+    <t>
       <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/220"/>:
       "consider removing the 'changes from 2068' sections"