Changeset 162 for draft-ietf-httpbis/latest/p2-semantics.xml

Timestamp:

Jan 11, 2008, 7:39:06 PM (12 years ago)

Author:

fielding@…

Message:

editorial: write preliminary introduction to p2 noting future reorg

File:

• draft-ietf-httpbis/latest/p2-semantics.xml (modified) (2 diffs)

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -22 +22 @@
   <!ENTITY auth                       "<xref target='Part7' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY content-negotiation        "<xref target='Part3' x:rel='#content.negotiation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
-  <!ENTITY diff2045entity             "<xref target='Part3' x:rel='#differences.between.http.entities.and.rfc.2045.entities' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY uri                        "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY http-url                   "<xref target='Part1' x:rel='#http-url' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
@@ -245 +244 @@
 <section title="Introduction" anchor="introduction">
 <t>
-   This document will define aspects of HTTP related to request and response
-   semantics. Right now it only includes the extracted relevant sections of
-   RFC 2616 with only minor edits.
-</t>
-<t>
-   The HTTP protocol is a request/response protocol. A client sends a
-   request to the server in the form of a request method, URI, and
-   protocol version, followed by a MIME-like message containing request
-   modifiers, client information, and possible body content over a
-   connection with a server. The server responds with a status line,
-   including the message's protocol version and a success or error code,
-   followed by a MIME-like message containing server information, entity
-   metainformation, and possible entity-body content. The relationship
-   between HTTP and MIME is described in &diff2045entity;.
+   This document defines HTTP/1.1 request and response semantics.  Each HTTP
+   message, as defined in &messaging;, is in the form of either a request or
+   a response.  An HTTP server listens on a connection for HTTP requests and
+   responds to each request, in the order received on that connection, with
+   one or more HTTP response messages.  This document defines the commonly
+   agreed upon semantics of the HTTP uniform interface, the intentions defined
+   by each request method, and the various response messages that might be
+   expected as a result of applying that method for the requested resource.
+</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 will be ordered according to the typical
+   processing of an HTTP request message (after message parsing): resource
+   mapping, general header fields, methods, request modifiers, response
+   status, and resource metadata.  The current mess reflects how widely
+   dispersed these topics and associated requirements had become in
+   <xref target="RFC2616"/>.
 </t>