Changeset 1858 for draft-ietf-httpbis/latest/p2-semantics.xml

Timestamp:

Sep 3, 2012, 2:29:18 PM (7 years ago)

Author:

fielding@…

Message:

(editorial) change of terms for content negotiation:

server-driven => proactive (UA sends Accept* fields)
agent-driven => reactive (UA waits for 300/Alternatives)

File:

• draft-ietf-httpbis/latest/p2-semantics.xml (modified) (15 diffs)

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

@@ -27 +27 @@
   <!ENTITY auth                       "<xref target='Part7' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY content-negotiation        "<xref target='content.negotiation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
-  <!ENTITY agent-driven-negotiation   "<xref target='agent-driven.negotiation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
+  <!ENTITY reactive-negotiation       "<xref target='reactive.negotiation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY abnf-extension             "<xref target='Part1' x:rel='#abnf.extension' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY whitespace                 "<xref target='Part1' x:rel='#whitespace' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
@@ -703 +703 @@
 <t>
    This specification defines two patterns of content negotiation;
-   "server-driven", where the server selects the representation based
-   upon the client's stated preferences, and "agent-driven" negotiation,
+   "proactive", where the server selects the representation based
+   upon the client's stated preferences, and "reactive" negotiation,
    where the server provides a list of representations for the client to
    choose from, based upon their metadata. In addition,  there are
@@ -717 +717 @@
    and practicality. In particular, when the number of preferences or
    capabilities to be expressed by a client are large (such as when many
-   different formats are supported by a user-agent), server-driven
+   different formats are supported by a user-agent), proactive
    negotiation becomes unwieldy, and might not be appropriate. Conversely,
    when the number of representations to choose from is very large,
-   agent-driven negotiation might not be appropriate.
+   reactive negotiation might not be appropriate.
 </t>
 <t>
@@ -728 +728 @@
 </t>
 
-<section title="Server-driven Negotiation" anchor="server-driven.negotiation">
+<section title="Proactive Negotiation" anchor="proactive.negotiation">
 <t>
    If the selection of the best representation for a response is made by
-   an algorithm located at the server, it is called server-driven
+   an algorithm located at the server, it is called proactive
    negotiation. Selection is based on the available representations of
    the response (the dimensions over which it can vary; e.g., language,
@@ -739 +739 @@
 </t>
 <t>
-   Server-driven negotiation is advantageous when the algorithm for
+   Proactive negotiation is advantageous when the algorithm for
    selecting from among the available representations is difficult to
    describe to the user agent, or when the server desires to send its
@@ -750 +750 @@
 </t>
 <t>
-   Server-driven negotiation has disadvantages:
+   Proactive negotiation has disadvantages:
   <list style="numbers">
     <t>
@@ -776 +776 @@
 </t>
 <t>
-   Server-driven negotiation allows the user agent to specify its preferences,
+   Proactive negotiation allows the user agent to specify its preferences,
    but it cannot expect responses to always honor them. For example, the origin
-   server might not implement server-driven negotiation, or it might decide that
+   server might not implement proactive negotiation, or it might decide that
    sending a response that doesn't conform to them is better than sending a <x:ref>406
    (Not Acceptable)</x:ref> response.
@@ -784 +784 @@
 <t>
    HTTP/1.1 includes the following header fields for enabling
-   server-driven negotiation through description of user agent
+   proactive negotiation through description of user agent
    capabilities and user preferences: <x:ref>Accept</x:ref>
    (<xref target="header.accept"/>), <x:ref>Accept-Charset</x:ref>
@@ -805 +805 @@
    The <x:ref>Vary</x:ref> header field (&header-vary;) can be used to express
    the parameters the server uses to select a representation that is subject to
-   server-driven negotiation.
-</t>
-</section>
-
-<section title="Agent-driven Negotiation" anchor="agent-driven.negotiation">
-<t>
-   With agent-driven negotiation, selection of the best representation
+   proactive negotiation.
+</t>
+</section>
+
+<section title="Reactive Negotiation" anchor="reactive.negotiation">
+<t>
+   With reactive negotiation, selection of the best representation
    for a response is performed by the user agent after receiving an
    initial response from the origin server. Selection is based on a list
@@ -822 +822 @@
 </t>
 <t>
-   Agent-driven negotiation is advantageous when the response would vary
+   Reactive negotiation is advantageous when the response would vary
    over commonly-used dimensions (such as type, language, or encoding),
    when the origin server is unable to determine a user agent's
@@ -829 +829 @@
 </t>
 <t>
-   Agent-driven negotiation suffers from the disadvantage of needing a
+   Reactive negotiation suffers from the disadvantage of needing a
    second request to obtain the best alternate representation. This
    second request is only efficient when caching is used. In addition,
@@ -839 +839 @@
 <t>
    This specification defines the <x:ref>300 (Multiple Choices)</x:ref> and
-   <x:ref>406 (Not Acceptable)</x:ref> status codes for enabling agent-driven
+   <x:ref>406 (Not Acceptable)</x:ref> status codes for enabling reactive
    negotiation when the server is unwilling or unable to provide a varying
-   response using server-driven negotiation.
+   response using proactive negotiation.
 </t>
 </section>
@@ -1710 +1710 @@
   <x:anchor-alias value="qvalue"/>
 <t>
-   Many of the request header fields for server-driven content negotiation
+   Many of the request header fields for proactive content negotiation
    use a common parameter, named "q", to assign a relative "weight" to the
    preference for that associated kind of content.
@@ -2593 +2593 @@
         <t>
           Redirection offering a choice of matching resources for use by
-          agent-driven content negotiation (&agent-driven-negotiation;). This
+          reactive content negotiation (&reactive-negotiation;). This
           is status code <x:ref>300 (Multiple Choices)</x:ref>.
         </t>
@@ -2652 +2652 @@
 <t>
    The target resource has more than one
-   representation, each with its own specific location, and agent-driven
+   representation, each with its own specific location, and reactive
    negotiation information (&content-negotiation;) is being provided so that
    the user (or user agent) can select a preferred representation by