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

Timestamp:

Dec 23, 2007, 5:22:38 AM (12 years ago)

Author:

julian.reschke@…

Message:

Cleanup references after switch to symbolic references (removing duplicated RFC numbers), clean up some of the references XML code.

File:

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

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

@@ -224 +224 @@
    This document will define aspects of HTTP related to caching response
    messages.  Right now it only includes the extracted relevant sections
-   of <xref target="RFC2616">RFC 2616</xref> without edit.
+   of <xref target="RFC2616" x:fmt="none">RFC 2616</xref> without edit.
 </t>
 
@@ -458 +458 @@
    A correct cache &MUST; respond to a request with the most up-to-date
    response held by the cache that is appropriate to the request (see
-   sections <xref target="disambiguating.expiration.values" format="counter"/>,
+   Sections <xref target="disambiguating.expiration.values" format="counter"/>,
    <xref target="disambiguating.multiple.responses" format="counter"/>,
    and <xref target="cache.replacement" format="counter"/>) which meets one of the following
@@ -477 +477 @@
          origin server, in carefully considered circumstances the cache
          &MAY; still return the response with the appropriate Warning
-         header (see section <xref target="exceptions.to.the.rules.and.warnings" format="counter"/>
+         header (see Sections <xref target="exceptions.to.the.rules.and.warnings" format="counter"/>
          and <xref target="header.warning" format="counter"/>), unless such a response
          is prohibited (e.g., by a "no-store" cache-directive, or by a
@@ -1480 +1480 @@
 <section title="Cache Replacement" anchor="cache.replacement">
 <t>
-   If a new cacheable (see sections <xref target="what.may.be.stored.by.caches" format="counter"/>,
+   If a new cacheable (see Sections <xref target="what.may.be.stored.by.caches" format="counter"/>,
    <xref target="disambiguating.expiration.values" format="counter"/>,
    <xref target="disambiguating.multiple.responses" format="counter"/>
@@ -2314 +2314 @@
 <t>
    If a character set other than ISO-8859-1 is used, it &MUST; be encoded
-   in the warn-text using the method described in RFC 2047 <xref target="RFC2047"/>.
+   in the warn-text using the method described in <xref target="RFC2047"/>.
 </t>
 <t>
@@ -2778 +2778 @@
 
 <reference anchor="RFC2047">
-<front>
-<title abbrev="Message Header Extensions">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</title>
-<author initials="K." surname="Moore" fullname="Keith Moore">
-<organization>University of Tennessee</organization>
-<address>
-<postal>
-<street>107 Ayres Hall</street>
-<street>Knoxville TN 37996-1301</street></postal>
-<email>moore@cs.utk.edu</email></address></author>
-<date month="November" year="1996"/>
-<area>Applications</area>
-<keyword>Amercian Standard Code for Information Interchange</keyword>
-<keyword>mail</keyword>
-<keyword>multipurpose internet mail extensions</keyword>
-</front>
-<seriesInfo name="RFC" value="2047"/>
+  <front>
+    <title abbrev="Message Header Extensions">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</title>
+    <author initials="K." surname="Moore" fullname="Keith Moore">
+      <organization>University of Tennessee</organization>
+      <address><email>moore@cs.utk.edu</email></address>
+    </author>
+    <date month="November" year="1996"/>
+  </front>
+  <seriesInfo name="RFC" value="2047"/>
 </reference>