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

Timestamp:

06/01/13 07:26:25 (9 years ago)

Author:

fielding@…

Message:

(editorial) more consistency regarding representation; explain what HEAD does instead of what it doesn't do

File:

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

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

@@ -848 +848 @@
 <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
+   message "<x:dfn>payload</x:dfn>".  In some cases, a payload might contain
+   only the associated representation's header fields (e.g., responses to
    HEAD) or only some part(s) of the representation data
    (e.g., the <x:ref>206 (Partial Content)</x:ref> status code).
@@ -855 +855 @@
 <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>
    For example, a representation in the payload of a PUT request
    (<xref target="PUT"/>) represents the desired state of the <x:ref>target resource</x:ref>
@@ -867 +863 @@
 </t>
 <t>
-   Likewise, the payload of a <x:ref>200 (OK)</x:ref> response to GET
-   (<xref target="GET"/>) ought to contain a representation of the
+   In a response, the payload's purpose is defined by both the request method
+   and the response status code.
+   For example, the payload of a <x:ref>200 (OK)</x:ref> response to GET
+   (<xref target="GET"/>) represents the current state of the
    <x:ref>target resource</x:ref>, as observed at the time of the message
-   origination date (<xref target="header.date"/>), whereas the same status
-   code in a response to POST might contain either a representation of the
-   processing result or a current representation of the target resource after
-   applying the processing. Response messages with an error status code
-   usually contain a representation of the error condition, such that it
-   describes the error state and what next steps are suggested for resolving
-   it.
+   origination date (<xref target="header.date"/>), whereas the payload of
+   the same status code in a response to POST might represent either the
+   processing result or the new state of the target resource after applying
+   the processing. Response messages with an error status code usually contain
+   a payload that represents the error condition, such that it describes the
+   error state and what next steps are suggested for resolving it.
 </t>
 <t>
@@ -1079 +1076 @@
    <c><xref target="GET" format="counter"/></c>
    <c>HEAD</c>
-   <c>Same as GET, but do not include a message body in the response.</c>
+   <c>Same as GET, but only transfer the status line and header block.</c>
    <c><xref target="HEAD" format="counter"/></c>
    <c>POST</c>
@@ -1286 +1283 @@
 <t>
    The HEAD method is identical to GET except that the server &MUST-NOT;
-   send a message body in the response. The metadata contained
-   in the HTTP header fields in response to a HEAD request &SHOULD; be identical
-   to the information sent in response to a GET request. This method can
-   be used for obtaining metadata about the selected representation
-   without transferring the representation data. This method is
-   often used for testing hypertext links for validity, accessibility,
-   and recent modification.
+   send a message body in the response (i.e., the response terminates at the
+   end of the header block). The metadata contained in the HTTP header fields
+   in response to a HEAD request &SHOULD; be identical to the information sent
+   in response to a GET request. This method can be used for obtaining
+   metadata about the selected representation without transferring the
+   representation data. This method is often used for testing hypertext links
+   for validity, accessibility, and recent modification.
 </t>
 <t>