Dec 30, 2007, 6:56:05 AM (12 years ago)

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.

1 edited


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

    r113 r115  
    1616  <!ENTITY ID-YEAR "2007">
    1717  <!ENTITY messaging                  "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    18   <!ENTITY caching                    "<xref target='Part6' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1918  <!ENTITY header-if-range            "<xref target='Part5' x:rel='#header.if-range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2019  <!ENTITY header-range               "<xref target='Part5' x:rel='#header.range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    192191<note title="Editorial Note (To be removed by RFC Editor)">
    193192  <t>
    194     This version of the HTTP specification contains only minimal editorial
    195     changes from <xref target="RFC2616"/> (abstract, introductory paragraph,
    196     and authors' addresses).  All other changes are due to partitioning the
    197     original into seven mostly independent parts.  The intent is for readers
    198     of future drafts to able to use draft 00 as the basis for comparison
    199     when the WG makes later changes to the specification text.  This draft
    200     will shortly be followed by draft 01 (containing the first round of changes
    201     that have already been agreed to on the mailing list). There is no point in
    202     reviewing this draft other than to verify that the partitioning has been
    203     done correctly.  Roy T. Fielding, Yves Lafon, and Julian Reschke
    204     will be the editors after draft 00 is submitted.
    205   </t>
    206   <t>
    207193    Discussion of this draft should take place on the HTTPBIS working group
    208194    mailing list (ietf-http-wg@w3.org). The current issues list is
    308    If the conditional GET used a strong cache validator (see &caching;),
     294   If the conditional GET used a strong cache validator (see <xref target="weak.and.strong.validators"/>),
    309295   the response &SHOULD-NOT;  include other entity-headers.
    310296   Otherwise (i.e., the conditional GET used a weak validator), the
    587573   The ETag response-header field provides the current value of the
    588574   entity tag for the requested variant. The headers used with entity
    589    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
     575   tags are described in Sections <xref target="header.if-match" format="counter"/>
     576   and <xref target="header.if-none-match" format="counter"/> of this document,
     577   and in &header-if-range;. The entity tag
    590578   &MAY; be used for comparison with other entities from the same resource
    591579   (see <xref target="weak.and.strong.validators"/>).
     1157<section title="Change Log (to be removed by RFC Editor before publication)">
     1159<section title="Since RFC2616">
     1161  Extracted relevant partitions from <xref target="RFC2616"/>.
     1165<section title="Since draft-ietf-httpbis-p4-conditional-00">
     1167  TBD.
Note: See TracChangeset for help on using the changeset viewer.