Changeset 1926


Ignore:
Timestamp:
Oct 1, 2012, 3:17:51 AM (7 years ago)
Author:
fielding@…
Message:

(editorial) tweak intro to better match document order

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

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

    r1925 r1926  
    842842      </ul>
    843843      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    844       <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,
    845          interprets the message semantics in relation to the identified request target, and responds to that request with one or more
    846          response messages. This document defines HTTP/1.1 request and response semantics in terms of the architecture defined in <a href="#Part1" id="rfc.xref.Part1.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
    847       </p>
    848       <p id="rfc.section.1.p.2">HTTP provides a uniform interface for interacting with resources regardless of their type, nature, or implementation. HTTP
    849          semantics includes the intentions defined by each request method (<a href="#methods" title="Request Methods">Section&nbsp;5</a>), extensions to those semantics that might be described in request header fields (<a href="#request.header.fields" title="Request Header Fields">Section&nbsp;6</a>), the meaning of status codes to indicate a machine-readable response (<a href="#status.codes" title="Response Status Codes">Section&nbsp;7</a>), and other control data and resource metadata that might be given in response header fields (<a href="#response.header.fields" title="Response Header Fields">Section&nbsp;8</a>).
    850       </p>
    851       <p id="rfc.section.1.p.3"><span id="rfc.iref.c.1"></span> In addition, this document defines the payload of messages (a.k.a., content), the associated metadata header fields that define
    852          how the payload is intended to be interpreted by a recipient, the request header fields that might influence content selection,
    853          and the various selection algorithms that are collectively referred to as "<dfn>content negotiation</dfn>".
     844      <p id="rfc.section.1.p.1">Each Hypertext Transfer Protocol (HTTP) message is either a request or a response. A server listens on a connection for a
     845         request, parses each message received, interprets the message semantics in relation to the identified request target, and
     846         responds to that request with one or more response messages. A client constructs request messages to communicate specific
     847         intentions, and examines received responses to see if the intentions were carried out and determine how to interpret the results.
     848         This document defines HTTP/1.1 request and response semantics in terms of the architecture defined in <a href="#Part1" id="rfc.xref.Part1.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>.
     849      </p>
     850      <p id="rfc.section.1.p.2">HTTP provides a uniform interface for interacting with a resource (<a href="#resource" title="Resource">Section&nbsp;2</a>), regardless of its type, nature, or implementation, and for transferring content in message payloads in the form of a representation
     851         (<a href="#representation" title="Representation">Section&nbsp;3</a>).
     852      </p>
     853      <p id="rfc.section.1.p.3">HTTP semantics include the intentions defined by each request method (<a href="#methods" title="Request Methods">Section&nbsp;5</a>), extensions to those semantics that might be described in request header fields (<a href="#request.header.fields" title="Request Header Fields">Section&nbsp;6</a>), the meaning of status codes to indicate a machine-readable response (<a href="#status.codes" title="Response Status Codes">Section&nbsp;7</a>), and the meaning of other control data and resource metadata that might be given in response header fields (<a href="#response.header.fields" title="Response Header Fields">Section&nbsp;8</a>).
     854      </p>
     855      <p id="rfc.section.1.p.4"><span id="rfc.iref.c.1"></span> This document also defines representation metadata that describe how a payload is intended to be interpreted by a recipient,
     856         the request header fields that might influence content selection, and the various selection algorithms that are collectively
     857         referred to as "<dfn>content negotiation</dfn>" (<a href="#content.negotiation" title="Content Negotiation">Section&nbsp;3.4</a>).
    854858      </p>
    855859      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="conformance" href="#conformance">Conformance and Error Handling</a></h2>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1925 r1926  
    193193<section title="Introduction" anchor="introduction">
    194194<t>
    195    Each HTTP message is either a request or a response. A server listens on a
    196    connection for a request, parses each message received, interprets the
    197    message semantics in relation to the identified request target, and
    198    responds to that request with one or more response messages.
     195   Each Hypertext Transfer Protocol (HTTP) message is either a request or a
     196   response. A server listens on a connection for a request, parses each
     197   message received, interprets the message semantics in relation to the
     198   identified request target, and responds to that request with one or more
     199   response messages. A client constructs request messages to communicate
     200   specific intentions, and examines received responses to see if the
     201   intentions were carried out and determine how to interpret the results.
    199202   This document defines HTTP/1.1 request and response semantics in terms of
    200203   the architecture defined in <xref target="Part1"/>.
    201204</t>
    202205<t>
    203    HTTP provides a uniform interface for interacting with resources regardless
    204    of their type, nature, or implementation.  HTTP semantics includes the
    205    intentions defined by each request method (<xref target="methods"/>),
    206    extensions to those semantics that might be described in request header
    207    fields (<xref target="request.header.fields"/>),
     206   HTTP provides a uniform interface for interacting with a resource
     207   (<xref target="resource"/>), regardless of its type, nature, or
     208   implementation, and for transferring content  in message payloads in the
     209   form of a representation (<xref target="representation"/>).
     210</t>
     211<t>
     212   HTTP semantics include the intentions defined by each request method
     213   (<xref target="methods"/>), extensions to those semantics that might be
     214   described in request header fields (<xref target="request.header.fields"/>),
    208215   the meaning of status codes to indicate a machine-readable response
    209    (<xref target="status.codes"/>), and other control data
     216   (<xref target="status.codes"/>), and the meaning of other control data
    210217   and resource metadata that might be given in response header fields
    211218   (<xref target="response.header.fields"/>).
    212219</t>
    213220<t><iref item="content negotiation"/>
    214    In addition, this document defines the payload of messages (a.k.a.,
    215    content), the associated metadata header fields that define how the payload
    216    is intended to be interpreted by a recipient, the request header fields
    217    that might influence content selection, and the various selection
     221   This document also defines representation metadata that describe how a
     222   payload is intended to be interpreted by a recipient, the request header
     223   fields that might influence content selection, and the various selection
    218224   algorithms that are collectively referred to as
    219    "<x:dfn>content negotiation</x:dfn>".
     225   "<x:dfn>content negotiation</x:dfn>" (<xref target="content.negotiation"/>).
    220226</t>
    221227<section title="Conformance and Error Handling" anchor="conformance">
Note: See TracChangeset for help on using the changeset viewer.