Changeset 2473

Timestamp:

05/11/13 00:29:53 (9 years ago)

Author:

fielding@…

Message:

remove sentence on strong validators being unique across representations because they are only required to be unique per representation data; addresses #518

Location:

draft-ietf-httpbis/latest

Files:

• p4-conditional.html (modified) (5 diffs)
• p4-conditional.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p4-conditional.html

@@ -445 +445 @@
   }
   @bottom-center {
-       content: "Expires May 5, 2014";
+       content: "Expires May 8, 2014";
   }
   @bottom-right {
@@ -488 +488 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2013-11-01">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-11-04">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP/1.1 conditional requests, including metadata header fields for indicating state changes, request header fields for making preconditions on such state, and rules for constructing the responses to a conditional request when one or more preconditions evaluate to false.">
@@ -514 +514 @@
             </tr>
             <tr>
-               <td class="left">Expires: May 5, 2014</td>
-               <td class="right">November 1, 2013</td>
+               <td class="left">Expires: May 8, 2014</td>
+               <td class="right">November 4, 2013</td>
             </tr>
          </tbody>
@@ -543 +543 @@
             in progress”.
          </p>
-         <p>This Internet-Draft will expire on May 5, 2014.</p>
+         <p>This Internet-Draft will expire on May 8, 2014.</p>
       </div>
       <div id="rfc.copyrightnotice">
@@ -675 +675 @@
             <p id="rfc.section.2.1.p.3">A strong validator might change for other reasons, such as when a semantically significant part of the representation metadata
                is changed (e.g., <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a>), but it is in the best interests of the origin server to only change the value when it is necessary to invalidate the stored
-               responses held by remote caches and authoring tools. A strong validator is unique across all representations of a given resource,
-               such that no two representations of that resource can share the same validator unless their representation data is identical.
+               responses held by remote caches and authoring tools.
             </p>
             <p id="rfc.section.2.1.p.4">Cache entries might persist for arbitrarily long periods, regardless of expiration times. Thus, a cache might attempt to validate

draft-ietf-httpbis/latest/p4-conditional.xml

@@ -217 +217 @@
    (e.g., <x:ref>Content-Type</x:ref>), but it is in the best interests of the
    origin server to only change the value when it is necessary to invalidate
-   the stored responses held by remote caches and authoring tools. A strong
-   validator is unique across all representations of a given resource, such
-   that no two representations of that resource can share the same validator
-   unless their representation data is identical.
+   the stored responses held by remote caches and authoring tools.
 </t>
 <t>