Changeset 2104 for draft-ietf-httpbis

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

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (3 diffs)
• p2-semantics.xml (modified) (3 diffs)

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

@@ -1776 +1776 @@
       </div>
       <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a id="request.conneg" href="#request.conneg">Content Negotiation</a></h2>
+      <p id="rfc.section.5.3.p.1">The following request header fields are sent by a user agent to engage in <a href="#proactive.negotiation" class="smpl">proactive negotiation</a> of the response content, as defined in <a href="#proactive.negotiation" title="Proactive Negotiation">Section&nbsp;3.4.1</a>. 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.
+      </p>
       <div id="rfc.table.u.5">
          <table class="tt full left" cellpadding="3" cellspacing="0">
@@ -1805 +1809 @@
       </div>
       <h3 id="rfc.section.5.3.1"><a href="#rfc.section.5.3.1">5.3.1</a>&nbsp;<a id="quality.values" href="#quality.values">Quality Values</a></h3>
-      <p id="rfc.section.5.3.1.p.1">Many of the request header fields for proactive content negotiation use a common parameter, named "q" (case-insensitive),
-         to assign a relative "weight" to the preference for that associated kind of content. This weight is referred to as a "quality
-         value" (or "qvalue") because the same parameter name is often used within server configurations to assign a weight to the
-         relative quality of the various representations that can be selected for a resource.
+      <p id="rfc.section.5.3.1.p.1">Many of the request header fields for <a href="#proactive.negotiation" class="smpl">proactive negotiation</a> use a common parameter, named "q" (case-insensitive), to assign a relative "weight" to the preference for that associated
+         kind of content. This weight is referred to as a "quality value" (or "qvalue") because the same parameter name is often used
+         within server configurations to assign a weight to the relative quality of the various representations that can be selected
+         for a resource.
       </p>
       <p id="rfc.section.5.3.1.p.2">The weight is normalized to a real number in the range 0 through 1, where 0.001 is the least preferred and 1 is the most preferred;
@@ -1919 +1923 @@
       <div id="rfc.iref.a.2"></div>
       <h3 id="rfc.section.5.3.3"><a href="#rfc.section.5.3.3">5.3.3</a>&nbsp;<a id="header.accept-charset" href="#header.accept-charset">Accept-Charset</a></h3>
-      <p id="rfc.section.5.3.3.p.1">The "Accept-Charset" header field can be sent by a user agent to indicate what charsets are acceptable in a selected representation.
-         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.
+      <p id="rfc.section.5.3.3.p.1">The "Accept-Charset" header field can be sent by a user agent to 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 information in those charsets.
       </p>
       <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.29"></span>  <a href="#header.accept-charset" class="smpl">Accept-Charset</a> = 1#( ( <a href="#charset" class="smpl">charset</a> / "*" ) [ <a href="#quality.values" class="smpl">weight</a> ] )

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"/>