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

Timestamp:

05/01/13 13:09:32 (10 years ago)

Author:

fielding@…

Message:

(editorial) more consistency regarding representation

File:

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

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

@@ -207 +207 @@
    HTTP provides a uniform interface for interacting with a resource
    (<xref target="resources"/>), regardless of its type, nature, or
-   implementation, and for transferring content  in message payloads in the
-   form of a representation (<xref target="representations"/>).
+   implementation, via the manipulation and transfer of representations
+   (<xref target="representations"/>).
 </t>
 <t>
@@ -486 +486 @@
    assume a media type of
    "application/octet-stream" (<xref target="RFC2046" x:fmt="," x:sec="4.5.1"/>)
-   or examine the representation data to determine its type.
+   or examine the data to determine its type.
 </t>
 <t>
@@ -774 +774 @@
    response message and its field-value refers to a URI that differs from the
    effective request URI, then the origin server claims that the field-value
-   is an identifier for the payload's representation. Such a claim can only be
-   trusted if both identifiers share the same resource owner, which cannot be
-   programmatically determined via HTTP.
+   is an identifier for the representation enclosed as the payload. Such a
+   claim can only be trusted if both identifiers share the same resource
+   owner, which cannot be programmatically determined via HTTP.
    <list style="symbols">
     <t>For a response to a GET or HEAD request, this is an indication that the
@@ -813 +813 @@
 <t>
    For example, if a client makes a PUT request on a negotiated resource and
-   the origin server accepts that PUT (without redirection), then the new set
-   of values for that resource is expected to be consistent with the one
+   the origin server accepts that PUT (without redirection), then the new
+   state of that resource is expected to be consistent with the one
    representation supplied in that PUT; the Content-Location cannot be used as
    a form of reverse content selection identifier to update only one of the
@@ -868 +868 @@
 <t>
    Likewise, the payload of a <x:ref>200 (OK)</x:ref> response to GET
-   (<xref target="GET"/>) contains a representation 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 that describes the error and what next steps are suggested
-   for resolving it.
+   (<xref target="GET"/>) ought to contain a representation 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.
 </t>
 <t>
@@ -896 +897 @@
   <x:anchor-alias value="content negotiation"/>
 <t>
-   When responses convey a representation, whether indicating a success or
+   When responses convey payload information, whether indicating a success or
    an error, the origin server often has different ways of representing that
    information; for example, in different formats, languages, or encodings.
@@ -1288 +1289 @@
    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 representation implied by the
-   request without transferring the representation data. This method is
+   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.