Ignore:
Timestamp:
Jul 14, 2012, 11:50:17 PM (7 years ago)
Author:
fielding@…
Message:

More tweaks to p2 abstract and introduction

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1782 r1784  
    500500      <meta name="dct.issued" scheme="ISO8601" content="2012-07-14">
    501501      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    502       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the six-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34;. Part 2 defines the semantics of HTTP messages, as expressed by request methods, request header fields, response status codes, and response header fields, the payload of messages as metadata and body content, and the mechanisms for content negotiation.">
    503       <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the six-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34;. Part 2 defines the semantics of HTTP messages, as expressed by request methods, request header fields, response status codes, and response header fields, the payload of messages as metadata and body content, and the mechanisms for content negotiation.">
     502      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
     503      <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
    504504   </head>
    505505   <body onload="init();">
     
    541541      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    542542      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information
    543          systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the
    544          six-part specification that defines the protocol referred to as "HTTP/1.1".
    545       </p> 
    546       <p>Part 2 defines the semantics of HTTP messages, as expressed by request methods, request header fields, response status codes,
    547          and response header fields, the payload of messages as metadata and body content, and the mechanisms for content negotiation.
     543         systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields,
     544         response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms
     545         for content negotiation.
    548546      </p>
    549547      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
     
    804802      </ul>
    805803      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    806       <p id="rfc.section.1.p.1">This document defines HTTP/1.1 request and response semantics in terms of the architecture, syntax notation, and conformance
    807          criteria defined in <a href="p1-messaging.html#architecture" title="Architecture">Section 2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. Each HTTP message is either a request or a response. A server listens on a connection for a request, parses each message
    808          received, interprets the message semantics in relation to the identified request target, and responds to that request with
    809          one or more response messages.
     804      <p id="rfc.section.1.p.1">Each HTTP message is either a request or a response. A server listens on a connection for a request, parses each message received,
     805         interprets the message semantics in relation to the identified request target, and responds to that request with one or more
     806         response messages. This document defines HTTP/1.1 request and response semantics in terms of the architecture, syntax notation,
     807         and conformance criteria defined in <a href="p1-messaging.html#architecture" title="Architecture">Section 2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    810808      </p>
    811809      <p id="rfc.section.1.p.2">HTTP provides a uniform interface for interacting with resources regardless of their type, nature, or implementation. HTTP
     
    819817      </p>
    820818      <div class="note" id="rfc.section.1.p.4">
    821          <p>This document is currently disorganized in order to minimize the changes between drafts and enable reviewers to see the smaller
     819         <p> <b>Note:</b> This document is currently disorganized in order to minimize changes between drafts and enable reviewers to see the smaller
    822820            errata changes. A future draft will reorganize the sections to better reflect the content. In particular, the sections will
    823821            be ordered according to the typical processing of an HTTP request message (after message parsing): resource mapping, methods,
Note: See TracChangeset for help on using the changeset viewer.