Changeset 2475

Timestamp:

05/11/13 01:09:07 (9 years ago)

Author:

fielding@…

Message:

clarify that content coding example is about strong entity tags; addresses #518

Location:

draft-ietf-httpbis/latest

Files:

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

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

@@ -916 +916 @@
 
 <em>...binary data...</em></pre><div class="note" id="rfc.section.2.3.3.p.7">
-                  <p><b>Note:</b> Content codings are a property of the representation, so therefore an entity-tag of an encoded representation has to be distinct
-                     from an unencoded representation to prevent conflicts during cache updates and range requests. In contrast, transfer codings
-                     (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) apply only during message transfer and do not require distinct entity-tags.
+                  <p><b>Note:</b> Content codings are a property of the representation data, so a strong entity-tag for a content-encoded representation has
+                     to be distinct from the entity tag of an unencoded representation to prevent potential conflicts during cache updates and
+                     range requests. In contrast, transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) apply only during message transfer and do not result in distinct entity-tags.
                   </p> 
                </div>

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

@@ -585 +585 @@
 <x:note>
   <t>
-    &Note; Content codings are a property of the representation,
-    so therefore an entity-tag of an encoded representation has to be distinct
-    from an unencoded representation to prevent conflicts during cache updates
-    and range requests.  In contrast, transfer codings (&transfer-codings;)
-    apply only during message transfer and do not require distinct entity-tags.
+    &Note; Content codings are a property of the representation data,
+    so a strong entity-tag for a content-encoded representation has to be
+    distinct from the entity tag of an unencoded representation to prevent
+    potential conflicts during cache updates and range requests. In contrast,
+    transfer codings (&transfer-codings;) apply only during message transfer
+    and do not result in distinct entity-tags.
   </t>
 </x:note>