Changeset 2347


Ignore:
Timestamp:
Aug 6, 2013, 5:49:31 AM (6 years ago)
Author:
mnot@…
Message:

Start to work on #450; all done except for intro rewrite and moving 5.3 to a subsection of 3.4.1.

File:
1 edited

Legend:

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

    r2344 r2347  
    263263  <x:anchor-alias value="target resource"/>
    264264<t>
    265    The target of each HTTP request is called a resource.
     265   The target of a HTTP request is called a resource.
    266266   HTTP does not limit the nature of a resource; it merely
    267267   defines an interface that might be used to interact with resources.
     
    333333</t>
    334334<t>
    335    The following header fields are defined to convey representation metadata:
     335   The following header fields convey representation metadata:
    336336</t>
    337337<texttable align="left">
     
    345345</texttable>
    346346
    347 <section title="Processing the Data" anchor="data.type">
     347<section title="Processing Representation Data" anchor="data.type">
    348348
    349349<section title="Media Type" anchor="media.type">
     
    543543   transformed without losing the identity of its underlying media type
    544544   and without loss of information. Frequently, the representation is stored
    545    in coded form, transmitted directly, and only decoded by the recipient.
     545   in coded form, transmitted directly, and only decoded by the final recipient.
    546546</t>
    547547<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="content-coding"/>
     
    729729         resource identified by the Content-Location field-value. However,
    730730         such an assertion cannot be trusted unless it can be verified by
    731          other means (not defined by HTTP). The information might still be
     731         other means (not defined by this document). The information might still be
    732732         useful for revision history links.</t>
    733733      <t>Otherwise, the payload is unidentified.</t>
     
    758758         representation of the resource identified by the Content-Location
    759759         field-value. However, such an assertion cannot be trusted unless
    760          it can be verified by other means (not defined by HTTP).</t>
     760         it can be verified by other means (not defined by this document).</t>
    761761      <t>Otherwise, the payload is unidentified.</t>
    762762   </list>
     
    950950</t>
    951951<t>
    952    Note that, in all cases, the supplier of representations to the origin
    953    server determines which representations might be considered to be the
    954    "same information".
     952   Note that, in all cases, the resource determines which representations might
     953   be considered to be the "same information".
    955954</t>
    956955
     
    960959<t>
    961960   When content negotiation preferences are sent by the user agent in a
    962    request in order to encourage an algorithm located at the server to
     961   request to encourage an algorithm located at the server to
    963962   select the preferred representation, it is called
    964963   <x:dfn>proactive negotiation</x:dfn>
     
    10471046</t>
    10481047<t>
     1048  Reactive negotiation can also be supported in successful responses (e.g.,
     1049  <x:ref>200 (OK)</x:ref> responses) if the payload format allows it.
     1050</t>
     1051<t>
    10491052   Reactive negotiation is advantageous when the response would vary
    10501053   over commonly-used dimensions (such as type, language, or encoding),
     
    10761079   fields when present in a request (<xref target="request.header.fields"/>)
    10771080   if those additional semantics do not conflict with the method.
     1081</t>
     1082<t>
     1083   For example, a client can send conditional request header fields
     1084   (<xref target="request.conditionals"/>) to make the requested
     1085   action conditional on the current state of the target resource
     1086   (<xref target="Part4"/>).
    10781087</t>
    10791088<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="method"/>
     
    11541163   with the <x:ref>405 (Method Not Allowed)</x:ref> status code.
    11551164</t>
    1156 <t>
    1157    A client can send conditional request header fields
    1158    (<xref target="request.conditionals"/>) to make the requested
    1159    action conditional on the current state of the target resource
    1160    (<xref target="Part4"/>).
    1161 </t>
    11621165</section>
    11631166
     
    15701573<t>
    15711574   If a DELETE method is successfully applied, the origin server &SHOULD; send
    1572    a <x:ref>202 (Accepted)</x:ref> status code if the action seems okay but
     1575   a <x:ref>202 (Accepted)</x:ref> status code if the action will likely succeed but
    15731576   has not yet been enacted,
    15741577   a <x:ref>204 (No Content)</x:ref> status code if the action has been
     
    16771680  <iref primary="true" item="OPTIONS method" x:for-anchor=""/>
    16781681<t>
    1679    The OPTIONS method requests information about the
    1680    communication options available on the request/response chain
    1681    identified by the effective request URI. This method allows a client to
    1682    determine the options and/or requirements associated with a resource,
    1683    or the capabilities of a server, without implying a resource action.
     1682   The OPTIONS method requests information about the communication options
     1683   available for the target resource, either at the origin server or an
     1684   intervening intermediary. This method allows a client to determine the
     1685   options and/or requirements associated with a resource, or the capabilities
     1686   of a server, without implying a resource action.
    16841687</t>
    16851688<t>
     
    33933396<t>
    33943397   The <x:dfn>409 (Conflict)</x:dfn> status code indicates that the request
    3395    could not be completed due to a conflict with the current state of the
     3398   could not be completed due to a conflict with the current state of the target
    33963399   resource. This code is used in situations where the user might be able to
    33973400   resolve the conflict and resubmit the request. The server &SHOULD; generate
Note: See TracChangeset for help on using the changeset viewer.