Changeset 115 for draft-ietf-httpbis/latest/p4-conditional.xml

Timestamp:

30/12/07 14:56:05 (13 years ago)

Author:

julian.reschke@…

Message:

Add templates for Changes sections throughout, remove intro specific to draft -00, enhance a few more inter-document references, cleanup some leftovers of the symref switchover.

File:

• draft-ietf-httpbis/latest/p4-conditional.xml (modified) (5 diffs)

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

@@ -16 +16 @@
   <!ENTITY ID-YEAR "2007">
   <!ENTITY messaging                  "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
-  <!ENTITY caching                    "<xref target='Part6' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY header-if-range            "<xref target='Part5' x:rel='#header.if-range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY header-range               "<xref target='Part5' x:rel='#header.range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
@@ -192 +191 @@
 <note title="Editorial Note (To be removed by RFC Editor)">
   <t>
-    This version of the HTTP specification contains only minimal editorial
-    changes from <xref target="RFC2616"/> (abstract, introductory paragraph,
-    and authors' addresses).  All other changes are due to partitioning the
-    original into seven mostly independent parts.  The intent is for readers
-    of future drafts to able to use draft 00 as the basis for comparison
-    when the WG makes later changes to the specification text.  This draft
-    will shortly be followed by draft 01 (containing the first round of changes
-    that have already been agreed to on the mailing list). There is no point in
-    reviewing this draft other than to verify that the partitioning has been
-    done correctly.  Roy T. Fielding, Yves Lafon, and Julian Reschke
-    will be the editors after draft 00 is submitted.
-  </t>
-  <t>
     Discussion of this draft should take place on the HTTPBIS working group
     mailing list (ietf-http-wg@w3.org). The current issues list is
@@ -306 +292 @@
 </t>
 <t>
-   If the conditional GET used a strong cache validator (see &caching;),
+   If the conditional GET used a strong cache validator (see <xref target="weak.and.strong.validators"/>),
    the response &SHOULD-NOT;  include other entity-headers.
    Otherwise (i.e., the conditional GET used a weak validator), the
@@ -587 +573 @@
    The ETag response-header field provides the current value of the
    entity tag for the requested variant. The headers used with entity
-   tags are described in Sections <xref target="header.if-match" format="counter"/>, <xref target="header.if-none-match" format="counter"/> and &header-if-range;. The entity tag
+   tags are described in Sections <xref target="header.if-match" format="counter"/>
+   and <xref target="header.if-none-match" format="counter"/> of this document,
+   and in &header-if-range;. The entity tag
    &MAY; be used for comparison with other entities from the same resource
    (see <xref target="weak.and.strong.validators"/>).
@@ -1167 +1155 @@
 </section>
 
+<section title="Change Log (to be removed by RFC Editor before publication)">
+
+<section title="Since RFC2616">
+<t>
+  Extracted relevant partitions from <xref target="RFC2616"/>.
+</t>
+</section>
+
+<section title="Since draft-ietf-httpbis-p4-conditional-00">
+<t>
+  TBD.
+</t>
+</section>
+
+</section>
+
 </back>
 </rfc>