Ignore:
Timestamp:
06/01/14 23:53:08 (7 years ago)
Author:
fielding@…
Message:

Reduce the resource owners SHOULD NOT... for action parameters in Resources to a discussion of precedence and forward reference to the MUST discussion under Safe Methods; remove mention of anonymous resources since it is superfluous to and distracting from the discussion of payloads; both in response to Resnick comments, see #532

File:
1 edited

Legend:

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

    r2538 r2539  
    286286   semantics in the request method (<xref target="methods"/>) and a few
    287287   request-modifying header fields (<xref target="request.header.fields"/>).
    288    Resource owners &SHOULD-NOT; include request semantics within a URI,
    289    such as by specifying an action to invoke within the path or query
    290    components of the effective request URI, unless those semantics are
    291    disabled when they are inconsistent with the request method.
     288   If there is a conflict between the method semantics and any semantic
     289   implied by the URI itself, as described in <xref target="safe.methods"/>,
     290   the method semantics take precedence.
    292291</t>
    293292</section>
     
    888887   The purpose of a payload in a request is defined by the method semantics.
    889888   For example, a representation in the payload of a PUT request
    890    (<xref target="PUT"/>) represents the desired state of the <x:ref>target resource</x:ref>
    891    if the request is successfully applied, whereas a representation in the
    892    payload of a POST request (<xref target="POST"/>) represents an anonymous
    893    resource for providing data to be processed, such as the information that
    894    a user entered within an HTML form.
     889   (<xref target="PUT"/>) represents the desired state of the
     890   <x:ref>target resource</x:ref> if the request is successfully applied,
     891   whereas a representation in the payload of a POST request
     892   (<xref target="POST"/>) represents information to be processed by the
     893   target resource.
    895894</t>
    896895<t>
Note: See TracChangeset for help on using the changeset viewer.