Ignore:
Timestamp:
14/09/13 23:59:24 (7 years ago)
Author:
fielding@…
Message:

rephrase misused SHOULDs; addresses #472

File:
1 edited

Legend:

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

    r2396 r2398  
    14601460   For example, if the target resource is configured to always have a
    14611461   <x:ref>Content-Type</x:ref> of "text/html" and the representation being PUT
    1462    has a Content-Type of "image/jpeg", then the origin server &SHOULD; do one of:
     1462   has a Content-Type of "image/jpeg", the origin server ought to do one of:
    14631463   <list style="letters">
    14641464      <t>reconfigure the target resource to reflect the new media type;</t>
     
    21282128</artwork></figure>
    21292129<t>
    2130    &SHOULD; be interpreted as "I prefer audio/basic, but send me any audio
     2130   is interpreted as "I prefer audio/basic, but send me any audio
    21312131   type if it is the best available after an 80% mark-down in quality".
    21322132</t>
Note: See TracChangeset for help on using the changeset viewer.