Ignore:
Timestamp:
Sep 15, 2012, 11:35:33 PM (7 years ago)
Author:
fielding@…
Message:

(editorial) further simplify representation; remove bits that are defined under payload

File:
1 edited

Legend:

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

    r1898 r1900  
    316316   if the request is successfully applied, whereas a representation in the
    317317   payload of a POST request (<xref target="POST"/>) represents an anonymous
    318    resource for providing data to be processed, such as a specific encoding
    319    format for the information that a user entered within an HTML form.
     318   resource for providing data to be processed, such as the information that
     319   a user entered within an HTML form.
    320320</t>
    321321<t>
     
    323323   (<xref target="GET"/>) contains a representation of the target resource,
    324324   as observed at the time of the message origination date
    325    (<xref target="header.date"/>), whereas the same response to POST might
    326    contain either a representation of the processing result or a current
    327    representation of the target resource after applying the processing.
    328    Response messages with an error status code usually contain a
    329    representation that describes the error and what next steps are suggested
     325   (<xref target="header.date"/>), whereas the same status code in a response
     326   to POST might contain either a representation of the processing result or
     327   a current representation of the target resource after applying the
     328   processing. Some responses only contain the representation's header fields
     329   as the payload. Response messages with an error status code usually contain
     330   a representation that describes the error and what next steps are suggested
    330331   for resolving it.
    331 </t>
    332 <t>
    333    A representation body is only present in a message when a message body is
    334    present, as described in &message-body;. The representation body is obtained
    335    from the message body by decoding any <x:ref>Transfer-Encoding</x:ref> that
    336    might have been applied to ensure safe and proper transfer of the message.
    337332</t>
    338333
Note: See TracChangeset for help on using the changeset viewer.