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

Timestamp:

18/09/12 09:26:12 (10 years ago)

Author:

fielding@…

Message:

(editorial) define payload within representation

File:

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

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

@@ -304 +304 @@
    of data (representation body).
 </t>
-<t>
-   HTTP messages can transfer a full or partial representation in the payload
-   (<xref target="payload"/>) if not otherwise restricted by the request
-   method or response status code. In a request, the purpose of such a
-   representation is defined by the method semantics. In a response, the
-   purpose is defined by both the request method and the response status code.
+
+<section title="Message Payload" anchor="payload">
+<iref item="payload"/>
+<t>
+   Some HTTP messages transfer a complete or partial representation as the
+   message "<x:dfn>payload</x:dfn>".  In some cases, a payload might only
+   contain the associated representation's header fields (e.g., responses to
+   HEAD) or only some part(s) of the representation body
+   (e.g., the <x:ref>206 (Partial Content)</x:ref> status code).
+</t>
+<t>
+   The purpose of a payload in a request is defined by the method semantics.
+   In a response, the payload's purpose is defined by both the request method
+   and the response status code.
 </t>
 <t>
@@ -331 +339 @@
    for resolving it.
 </t>
+<t>
+   Header fields that specifically describe the payload, rather than the
+   associated representation, are referred to as "payload header fields".
+   Payload header fields are defined in other parts of this specification,
+   due to their impact on message parsing.
+</t>
+<texttable align="left">
+  <ttcol>Header Field Name</ttcol>
+  <ttcol>Defined in...</ttcol>
+
+  <c>Content-Length</c> <c>&header-content-length;</c>
+  <c>Content-Range</c> <c>&header-content-range;</c>
+  <c>Transfer-Encoding</c> <c>&header-transfer-encoding;</c>
+</texttable>
+</section>
 
 <section title="Associating a Representation with its Resource" anchor="associating.representation.with.resource">
@@ -845 +868 @@
 </t>
 </section>
-</section>
-</section>
-
-<section title="Payload" anchor="payload">
-<t>
-   HTTP messages &MAY; transfer a payload if not otherwise restricted by
-   the request method or response status code.  The payload consists of
-   metadata, in the form of header fields, and data, in the form of the
-   sequence of octets in the message body after any transfer-coding has
-   been decoded.
-</t>
-<iref item="payload"/>
-<t>   
-   A "<x:dfn>payload</x:dfn>" in HTTP is always a partial or complete
-   representation of some resource.  We use separate terms for payload
-   and representation because some messages contain only the associated
-   representation's header fields (e.g., responses to HEAD) or only some
-   part(s) of the representation (e.g., the <x:ref>206 (Partial Content)</x:ref>
-   status code).
-</t>
-<section title="Payload Header Fields" anchor="payload.header.fields">
-  <x:anchor-alias value="payload-header"/>
-<t>
-   HTTP header fields that specifically define the payload, rather than the
-   associated representation, are referred to as "payload header fields".
-   The following payload header fields are defined by HTTP/1.1:
-</t>
-<texttable align="left">
-  <ttcol>Header Field Name</ttcol>
-  <ttcol>Defined in...</ttcol>
-
-  <c>Content-Length</c> <c>&header-content-length;</c>
-  <c>Content-Range</c> <c>&header-content-range;</c>
-</texttable>
-</section>
-
-<section title="Payload Body" anchor="payload.body">
-  <x:anchor-alias value="payload-body"/>
-<t>
-   A payload body is only present in a message when a message body is
-   present, as described in &message-body;. The payload body is obtained
-   from the message body by decoding any <x:ref>Transfer-Encoding</x:ref> that
-   might have been applied to ensure safe and proper transfer of the message.
-</t>
 </section>
 </section>