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

Timestamp:

23/06/12 12:01:38 (10 years ago)

Author:

julian.reschke@…

Message:

Simplify use of "Note:", make upper/lowercase of sentence start consistent; use "—" where appropriate

File:

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

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

@@ -15 +15 @@
   <!ENTITY ID-MONTH "June">
   <!ENTITY ID-YEAR "2012">
+  <!ENTITY mdash "&#8212;">
+  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
   <!ENTITY architecture                "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY notation                    "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
@@ -635 +637 @@
 </t>
 <t>
-   Additionally, clients can influence freshness calculation -- either
-   constraining it relaxing it -- by using the max-age and min-fresh
+   Additionally, clients can influence freshness calculation &mdash; either
+   constraining it relaxing it &mdash; by using the max-age and min-fresh
    request cache directives. See <xref target="cache-request-directive" /> 
    for details.
@@ -694 +696 @@
 <x:note>
    <t>
-      <x:h>Note:</x:h> RFC 2616 (<xref target="RFC2616" x:fmt=","
+      &Note; RFC 2616 (<xref target="RFC2616" x:fmt=","
       x:sec="13.9"/>) required that caches do not calculate heuristic
       freshness for URIs with query components (i.e., those containing '?').
@@ -1201 +1203 @@
 <x:note>
    <t>
-       <x:h>Note:</x:h> HTTP/1.0 caches might not implement Cache-Control and
+       &Note; HTTP/1.0 caches might not implement Cache-Control and
        might only implement Pragma: no-cache (see <xref target="header.pragma"
        />).
@@ -1379 +1381 @@
       fields defined by this specification. Field names are case-insensitive.
       </t>
-      <t> <x:h>Note:</x:h> This usage of the word "private" only controls
+      <t>&Note; This usage of the word "private" only controls
       where the response can be stored; it cannot ensure the privacy of the
       message content. Also, private response directives with field-names are
@@ -1408 +1410 @@
       fields defined by this specification. Field names are case-insensitive.
       </t>
-      <t> <x:h>Note:</x:h> Most HTTP/1.0 caches will not recognize or obey
+      <t>&Note; Most HTTP/1.0 caches will not recognize or obey
       this directive. Also, no-cache response directives with field-names are
       often handled by implementations as if an unqualified no-cache directive
@@ -1598 +1600 @@
 <x:note>
    <t>
-       <x:h>Note:</x:h> If a response includes a Cache-Control field with the
+       &Note; If a response includes a Cache-Control field with the
        max-age directive (see <xref target="cache-response-directive" />),
        that directive overrides the Expires field. Likewise, the s-maxage
@@ -1674 +1676 @@
 <x:note>
    <t>
-      <x:h>Note:</x:h> Because the meaning of "Pragma: no-cache" in responses is not
+      &Note; Because the meaning of "Pragma: no-cache" in responses is not
       specified, it does not provide a reliable replacement for
       "Cache-Control: no-cache" in them.