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

Timestamp:

10/01/13 09:11:48 (10 years ago)

Author:

fielding@…

Message:

(editorial) add intro for proactive negotiation fields and clarify that they might apply to any response content, not just representations of the target resource

File:

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

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

@@ -1972 +1972 @@
 
 <section title="Content Negotiation" anchor="request.conneg">
+<t>
+   The following request header fields are sent by a user agent to engage in
+   <x:ref>proactive negotiation</x:ref> of the response content, as defined in
+   <xref target="proactive.negotiation"/>. The preferences sent in these
+   fields apply to any content in the response, including representations of
+   the target resource, representations of error or processing status, and
+   potentially even the miscellaneous text strings that might appear within
+   the protocol.
+</t>
 <texttable align="left">
   <ttcol>Header Field Name</ttcol>
@@ -1986 +1995 @@
   <x:anchor-alias value="qvalue"/>
 <t>
-   Many of the request header fields for proactive content negotiation
+   Many of the request header fields for <x:ref>proactive negotiation</x:ref>
    use a common parameter, named "q" (case-insensitive), to assign a relative
    "weight" to the preference for that associated kind of content.
@@ -2143 +2152 @@
 <t>
    The "Accept-Charset" header field can be sent by a user agent to
-   indicate what charsets are acceptable in a selected representation.
+   indicate what charsets are acceptable in textual response content.
    This field allows user agents capable of understanding more comprehensive
    or special-purpose charsets to signal that capability to an origin server
-   that is capable of representing documents in those charsets.
+   that is capable of representing information in those charsets.
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept-Charset"/>