Changeset 457 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

Feb 28, 2009, 11:31:30 AM (11 years ago)

Author:

julian.reschke@…

Message:

Editorial change: move definition of quality values from Part 3 to Part 1. In Part 1, make the grammar of the TE request header independent from accept-params, defined in Part 3.

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (14 diffs)

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -25 +25 @@
   <!ENTITY entity-body            "<xref target='Part3' x:rel='#entity.body' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY entity-header-fields   "<xref target='Part3' x:rel='#entity.header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
-  <!ENTITY header-accept          "<xref target='Part3' x:rel='#header.accept' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY header-cache-control   "<xref target='Part6' x:rel='#header.cache-control' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY header-expect          "<xref target='Part2' x:rel='#header.expect' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
@@ -31 +30 @@
   <!ENTITY header-warning         "<xref target='Part6' x:rel='#header.warning' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY idempotent-methods     "<xref target='Part2' x:rel='#idempotent.methods' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
-  <!ENTITY qvalue                 "<xref target='Part3' x:rel='#quality.values' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY request-header-fields  "<xref target='Part2' x:rel='#request.header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY response-header-fields "<xref target='Part2' x:rel='#response.header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
@@ -474 +472 @@
   <x:anchor-alias value="request-header"/>
   <x:anchor-alias value="response-header"/>
-  <x:anchor-alias value="accept-params"/>
   <x:anchor-alias value="entity-body"/>
   <x:anchor-alias value="entity-header"/>
@@ -488 +485 @@
 </artwork></figure>
 <figure><!-- Part3--><artwork type="abnf2616">
-  <x:ref>accept-params</x:ref>   = &lt;accept-params, defined in &header-accept;&gt;
   <x:ref>entity-body</x:ref>     = &lt;entity-body, defined in &entity-body;&gt;
   <x:ref>entity-header</x:ref>   = &lt;entity-header, defined in &entity-header-fields;&gt;
@@ -1145 +1141 @@
    the product value).
 </t>
+</section>
+
+<section title="Quality Values" anchor="quality.values">
+  <x:anchor-alias value="qvalue"/>
+<t>
+   Both transfer codings (TE request header, <xref target="header.te"/>)
+   and content negotiation (&content.negotiation;) use short "floating point"
+   numbers to indicate the relative importance ("weight") of various
+   negotiable parameters.  A weight is normalized to a real number in
+   the range 0 through 1, where 0 is the minimum and 1 the maximum
+   value. If a parameter has a quality value of 0, then content with
+   this parameter is `not acceptable' for the client. HTTP/1.1
+   applications &MUST-NOT; generate more than three digits after the
+   decimal point. User configuration of these values &SHOULD; also be
+   limited in this fashion.
+</t>
+<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="qvalue"/>
+  <x:ref>qvalue</x:ref>         = ( "0" [ "." 0*3<x:ref>DIGIT</x:ref> ] )
+                 / ( "1" [ "." 0*3("0") ] )
+</artwork></figure>
+<x:note>
+  <t>
+     <x:h>Note:</x:h> "Quality values" is a misnomer, since these values merely represent
+     relative degradation in desired quality.
+  </t>
+</x:note>
 </section>
 
@@ -2381 +2403 @@
   <x:anchor-alias value="TE-v"/>
   <x:anchor-alias value="t-codings"/>
+  <x:anchor-alias value="te-params"/>
+  <x:anchor-alias value="te-ext"/>
 <t>
    The request-header field "TE" indicates what extension transfer-codings
@@ -2389 +2413 @@
    parameters (as described in <xref target="transfer.codings"/>).
 </t>
-<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="TE"/><iref primary="true" item="Grammar" subitem="TE-v"/><iref primary="true" item="Grammar" subitem="t-codings"/>
+<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="TE"/><iref primary="true" item="Grammar" subitem="TE-v"/><iref primary="true" item="Grammar" subitem="t-codings"/><iref primary="true" item="Grammar" subitem="te-params"/><iref primary="true" item="Grammar" subitem="te-ext"/>
   <x:ref>TE</x:ref>        = "TE" ":" <x:ref>OWS</x:ref> <x:ref>TE-v</x:ref>
   <x:ref>TE-v</x:ref>      = #<x:ref>t-codings</x:ref>
-  <x:ref>t-codings</x:ref> = "trailers" / ( <x:ref>transfer-extension</x:ref> [ <x:ref>accept-params</x:ref> ] )
+  <x:ref>t-codings</x:ref> = "trailers" / ( <x:ref>transfer-extension</x:ref> [ <x:ref>te-params</x:ref> ] )
+  <x:ref>te-params</x:ref> = <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> "q=" <x:ref>qvalue</x:ref> *( <x:ref>te-ext</x:ref> )
+  <x:ref>te-ext</x:ref>    = <x:ref>OWS</x:ref> ";" <x:ref>OWS</x:ref> <x:ref>token</x:ref> [ "=" ( <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref> ) ]
 </artwork></figure>
 <t>
@@ -2435 +2461 @@
       <t>If the transfer-coding being tested is one of the transfer-codings
          listed in the TE field, then it is acceptable unless it
-         is accompanied by a qvalue of 0. (As defined in &qvalue;, a
+         is accompanied by a qvalue of 0. (As defined in <xref target="quality.values"/>, a
          qvalue of 0 means "not acceptable.")</t>
     </x:lt>
@@ -2448 +2474 @@
 <t>
    If the TE field-value is empty or if no TE field is present, the only
-   transfer-coding  is "chunked". A message with no transfer-coding is
+   transfer-coding is "chunked". A message with no transfer-coding is
    always acceptable.
 </t>
@@ -4094 +4120 @@
 </t>
 <t>
+   Quality Values of zero should indicate that "I don't want something"
+   to allow clients to refuse a representation. (<xref target="quality.values"/>)
+</t>
+<t>
    Transfer-coding had significant problems, particularly with
    interactions with chunked encoding. The solution is that transfer-codings
@@ -4464 +4494 @@
 
 <x:ref>absolute-URI</x:ref> = &lt;absolute-URI, defined in [RFC3986], Section 4.3&gt;
-<x:ref>accept-params</x:ref> = &lt;accept-params, defined in [Part3], Section 5.1&gt;
 <x:ref>asctime-date</x:ref> = wkday SP date3 SP time SP 4DIGIT
 <x:ref>attribute</x:ref> = token
@@ -4533 +4562 @@
 <x:ref>quoted-string</x:ref> = DQUOTE *( qdtext / quoted-pair ) DQUOTE
 <x:ref>quoted-text</x:ref> = %x01-09 / %x0B-0C / %x0E-FF
+<x:ref>qvalue</x:ref> = ( "0" [ "." *3DIGIT ] ) / ( "1" [ "." *3"0" ] )
 
 <x:ref>received-by</x:ref> = ( uri-host [ ":" port ] ) / pseudonym
@@ -4565 +4595 @@
 <x:ref>start-line</x:ref> = Request-Line / Status-Line
 
-<x:ref>t-codings</x:ref> = "trailers" / ( transfer-extension [ accept-params ] )
+<x:ref>t-codings</x:ref> = "trailers" / ( transfer-extension [ te-params ] )
 <x:ref>tchar</x:ref> = "!" / "#" / "$" / "%" / "&amp;" / "'" / "*" / "+" / "-" / "." /
  "^" / "_" / "`" / "|" / "~" / DIGIT / ALPHA
+<x:ref>te-ext</x:ref> = OWS ";" OWS token [ "=" ( token / quoted-string ) ]
+<x:ref>te-params</x:ref> = OWS ";" OWS "q=" qvalue *te-ext
 <x:ref>time</x:ref> = 2DIGIT ":" 2DIGIT ":" 2DIGIT
 <x:ref>token</x:ref> = 1*tchar
@@ -4948 +4980 @@
       Rewrite introduction; add mostly new Architecture Section.
     </t>
+    <t>
+      Move definition of quality values from Part 3 into Part 1;
+      make TE request header grammar independent of accept-params (defined in Part 3).
+    </t>
   </list>
 </t>