Changeset 161 for draft-ietf-httpbis

Timestamp:

12/01/08 02:21:34 (13 years ago)

Author:

fielding@…

Message:

editorial: write preliminary introduction to p3 noting future reorg

Location:

draft-ietf-httpbis/latest

Files:

• p3-payload.html (modified) (3 diffs)
• p3-payload.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p3-payload.html

@@ -565 +565 @@
       </ul>
       <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
-      <p id="rfc.section.1.p.1">This document will define aspects of HTTP related to the payload of messages (message content), including metadata and media
-         types, along with HTTP content negotiation. Right now it only includes the extracted relevant sections of RFC 2616 without
-         edit.
+      <p id="rfc.section.1.p.1">This document defines HTTP message payloads (a.k.a., content), the associated metadata header fields that define how the payload
+         is intended to be interpreted by a recipient, the request header fields that may influence content selection, and the various
+         selection algorithms that are collectively referred to as HTTP content negotiation.
+      </p>
+      <p id="rfc.section.1.p.2">This document is currently disorganized in order to minimize the changes between drafts and enable reviewers to see the smaller
+         errata changes. The next draft will reorganize the sections to better reflect the content. In particular, the sections on
+         entities will be renamed payload and moved to the first half of the document, while the sections on content negotiation and
+         associated request header fields will be moved to the second half. The current mess reflects how widely dispersed these topics
+         and associated requirements had become in <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
       </p>
       <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2>
@@ -1477 +1483 @@
       <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a>&nbsp;Since RFC2616
       </h2>
-      <p id="rfc.section.D.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
+      <p id="rfc.section.D.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
       </p>
       <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a>&nbsp;Since draft-ietf-httpbis-p3-payload-00
@@ -1694 +1700 @@
                   <li class="indline1"><em>RFC2388</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2388.1">2.3.2</a>, <a class="iref" href="#RFC2388"><b>9.2</b></a></li>
                   <li class="indline1"><em>RFC2557</em>&nbsp;&nbsp;<a class="iref" href="#RFC2557"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2557.1">A.6</a>, <a class="iref" href="#rfc.xref.RFC2557.2">C.1</a></li>
-                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#RFC2616"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">D.1</a></li>
+                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">D.1</a></li>
                   <li class="indline1"><em>RFC2822</em>&nbsp;&nbsp;<a class="iref" href="#RFC2822"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2822.1">A</a></li>
                   <li class="indline1"><em>RFC3629</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3629.1">2.1</a>, <a class="iref" href="#RFC3629"><b>9.2</b></a></li>

draft-ietf-httpbis/latest/p3-payload.xml

@@ -214 +214 @@
 <section title="Introduction" anchor="introduction">
 <t>
-   This document will define aspects of HTTP related to the payload of
-   messages (message content), including metadata and media types, along
-   with HTTP content negotiation.  Right now it only includes the extracted
-   relevant sections of RFC 2616 without edit.
+   This document defines HTTP message payloads (a.k.a., content), the
+   associated metadata header fields that define how the payload is intended
+   to be interpreted by a recipient, the request header fields that
+   may influence content selection, and the various selection algorithms
+   that are collectively referred to as HTTP content negotiation.
+</t>
+<t>
+   This document is currently disorganized in order to minimize the changes
+   between drafts and enable reviewers to see the smaller errata changes.
+   The next draft will reorganize the sections to better reflect the content.
+   In particular, the sections on entities will be renamed payload and moved
+   to the first half of the document, while the sections on content negotiation
+   and associated request header fields will be moved to the second half.  The
+   current mess reflects how widely dispersed these topics and associated
+   requirements had become in <xref target="RFC2616"/>.
 </t>