Changeset 2114 for draft-ietf-httpbis/latest

Timestamp:

11/01/13 13:39:01 (10 years ago)

Author:

fielding@…

Message:

(editorial) improve description of 300 and 406 in reactive negotiation; partly addresses #426

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (1 diff)
• p2-semantics.xml (modified) (1 diff)

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

@@ -1233 +1233 @@
          manually by the user selecting from a generated (possibly hypertext) menu.
       </p>
-      <p id="rfc.section.3.4.2.p.2">The <a href="#status.300" class="smpl">300 (Multiple Choices)</a> and <a href="#status.406" class="smpl">406 (Not Acceptable)</a> status codes indicate reactive negotiation when the origin server is unwilling or unable to provide a varying response using
-         proactive negotiation.
+      <p id="rfc.section.3.4.2.p.2">A server can send a <a href="#status.300" class="smpl">300 (Multiple Choices)</a> response to indicate that reactive negotiation by the user agent is desired, or a <a href="#status.406" class="smpl">406 (Not Acceptable)</a> status code to indicate that proactive negotiation has failed. In both cases, the response ought to include information about
+         the available representations so that the user or user agent can react by making a selection.
       </p>
       <p id="rfc.section.3.4.2.p.3">Reactive negotiation is advantageous when the response would vary over commonly-used dimensions (such as type, language, or

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

@@ -1015 +1015 @@
 </t>
 <t>
-   The <x:ref>300 (Multiple Choices)</x:ref> and
-   <x:ref>406 (Not Acceptable)</x:ref> status codes indicate reactive
-   negotiation when the origin server is unwilling or unable to provide a
-   varying response using proactive negotiation.
+   A server can send a <x:ref>300 (Multiple Choices)</x:ref> response to
+   indicate that reactive negotiation by the user agent is desired, or a
+   <x:ref>406 (Not Acceptable)</x:ref> status code to indicate that proactive
+   negotiation has failed. In both cases, the response ought to include
+   information about the available representations so that the user or
+   user agent can react by making a selection.
 </t>
 <t>