Changeset 459


Ignore:
Timestamp:
28/02/09 19:47:52 (12 years ago)
Author:
julian.reschke@…
Message:

Editorial: transform lists and tables in artwork into real lists and tables

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p3-payload.html

    r458 r459  
    10031003      </p>
    10041004      <div id="rfc.figure.u.18"></div><pre class="text">  Accept: text/*, text/html, text/html;level=1, */*
    1005 </pre><p id="rfc.section.5.1.p.14">have the following precedence:</p>
    1006       <div id="rfc.figure.u.19"></div><pre class="text">    1) text/html;level=1
    1007     2) text/html
    1008     3) text/*
    1009     4) */*
    1010 </pre><p id="rfc.section.5.1.p.16">The media type quality factor associated with a given type is determined by finding the media range with the highest precedence
     1005</pre><p id="rfc.section.5.1.p.14">have the following precedence: </p>
     1006      <ol>
     1007         <li>text/html;level=1</li>
     1008         <li>text/html</li>
     1009         <li>text/*</li>
     1010         <li>*/*</li>
     1011      </ol>
     1012      <p id="rfc.section.5.1.p.15">The media type quality factor associated with a given type is determined by finding the media range with the highest precedence
    10111013         which matches that type. For example,
    10121014      </p>
    1013       <div id="rfc.figure.u.20"></div><pre class="text">  Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
     1015      <div id="rfc.figure.u.19"></div><pre class="text">  Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
    10141016          text/html;level=2;q=0.4, */*;q=0.5
    1015 </pre><p id="rfc.section.5.1.p.18">would cause the following values to be associated:</p>
    1016       <div id="rfc.figure.u.21"></div><pre class="text">    text/html;level=1         = 1
    1017     text/html                 = 0.7
    1018     text/plain                = 0.3
    1019     image/jpeg                = 0.5
    1020     text/html;level=2         = 0.4
    1021     text/html;level=3         = 0.7
    1022 </pre><p id="rfc.section.5.1.p.20"> <b>Note:</b> A user agent might be provided with a default set of quality values for certain media ranges. However, unless the user agent
     1017</pre><p id="rfc.section.5.1.p.17">would cause the following values to be associated:</p>
     1018      <div id="rfc.table.u.1">
     1019         <table summary="" class="tt full" cellpadding="3" cellspacing="0">
     1020            <thead>
     1021               <tr>
     1022                  <th>Media Type</th>
     1023                  <th>Quality Value</th>
     1024               </tr>
     1025            </thead>
     1026            <tbody>
     1027               <tr>
     1028                  <td>text/html;level=1</td>
     1029                  <td>1</td>
     1030               </tr>
     1031               <tr>
     1032                  <td>text/html</td>
     1033                  <td>0.7</td>
     1034               </tr>
     1035               <tr>
     1036                  <td>text/plain</td>
     1037                  <td>0.3</td>
     1038               </tr>
     1039               <tr>
     1040                  <td>image/jpeg</td>
     1041                  <td>0.5</td>
     1042               </tr>
     1043               <tr>
     1044                  <td>text/html;level=2</td>
     1045                  <td>0.4</td>
     1046               </tr>
     1047               <tr>
     1048                  <td>text/html;level=3</td>
     1049                  <td>0.7</td>
     1050               </tr>
     1051            </tbody>
     1052         </table>
     1053      </div>
     1054      <p id="rfc.section.5.1.p.18"> <b>Note:</b> A user agent might be provided with a default set of quality values for certain media ranges. However, unless the user agent
    10231055         is a closed system which cannot interact with other rendering agents, this default set ought to be configurable by the user.
    10241056      </p>
    … …  
    10301062         to a server which is capable of representing documents in those character sets.
    10311063      </p>
    1032       <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span>  <a href="#header.accept-charset" class="smpl">Accept-Charset</a>   = "Accept-Charset" ":" <a href="#core.rules" class="smpl">OWS</a>
     1064      <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span>  <a href="#header.accept-charset" class="smpl">Accept-Charset</a>   = "Accept-Charset" ":" <a href="#core.rules" class="smpl">OWS</a>
    10331065          <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a>
    10341066  <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a> = 1#( ( <a href="#rule.charset" class="smpl">charset</a> / "*" )
    … …  
    10371069         example is
    10381070      </p>
    1039       <div id="rfc.figure.u.23"></div><pre class="text">  Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
     1071      <div id="rfc.figure.u.21"></div><pre class="text">  Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
    10401072</pre><p id="rfc.section.5.2.p.5">The special value "*", if present in the Accept-Charset field, matches every character set (including ISO-8859-1) which is
    10411073         not mentioned elsewhere in the Accept-Charset field. If no "*" is present in an Accept-Charset field, then all character sets
    … …  
    10511083      <p id="rfc.section.5.3.p.1">The request-header field "Accept-Encoding" is similar to Accept, but restricts the content-codings (<a href="#content.codings" title="Content Codings">Section&nbsp;2.2</a>) that are acceptable in the response.
    10521084      </p>
    1053       <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.23"></span><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a>    = "Accept-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a>
     1085      <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.23"></span><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a>    = "Accept-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a>
    10541086                     <a href="#header.accept-encoding" class="smpl">Accept-Encoding-v</a>
    10551087  <a href="#header.accept-encoding" class="smpl">Accept-Encoding-v</a>  =
    … …  
    10591091      </p>
    10601092      <p id="rfc.section.5.3.p.4">Examples of its use are:</p>
    1061       <div id="rfc.figure.u.25"></div><pre class="text">  Accept-Encoding: compress, gzip
     1093      <div id="rfc.figure.u.23"></div><pre class="text">  Accept-Encoding: compress, gzip
    10621094  Accept-Encoding:
    10631095  Accept-Encoding: *
    … …  
    11011133         as a response to the request. Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;2.4</a>.
    11021134      </p>
    1103       <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span>  <a href="#header.accept-language" class="smpl">Accept-Language</a>   = "Accept-Language" ":" <a href="#core.rules" class="smpl">OWS</a>
     1135      <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span>  <a href="#header.accept-language" class="smpl">Accept-Language</a>   = "Accept-Language" ":" <a href="#core.rules" class="smpl">OWS</a>
    11041136                    <a href="#header.accept-language" class="smpl">Accept-Language-v</a>
    11051137  <a href="#header.accept-language" class="smpl">Accept-Language-v</a> =
    … …  
    11101142         languages specified by that range. The quality value defaults to "q=1". For example,
    11111143      </p>
    1112       <div id="rfc.figure.u.27"></div><pre class="text">  Accept-Language: da, en-gb;q=0.8, en;q=0.7
     1144      <div id="rfc.figure.u.25"></div><pre class="text">  Accept-Language: da, en-gb;q=0.8, en;q=0.7
    11131145</pre><p id="rfc.section.5.4.p.5">would mean: "I prefer Danish, but will accept British English and other types of English."</p>
    11141146      <p id="rfc.section.5.4.p.6">For matching, the "Basic Filtering" matching scheme, defined in <a href="http://tools.ietf.org/html/rfc4647#section-3.3.1">Section 3.3.1</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.2"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, is used:
    … …  
    11541186         to be compressed without losing the identity of its underlying media type.
    11551187      </p>
    1156       <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span>  <a href="#header.content-encoding" class="smpl">Content-Encoding</a>   = "Content-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a>
     1188      <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span>  <a href="#header.content-encoding" class="smpl">Content-Encoding</a>   = "Content-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a>
    11571189  <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a> = 1#<a href="#content.codings" class="smpl">content-coding</a>
    11581190</pre><p id="rfc.section.5.5.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section&nbsp;2.2</a>. An example of its use is
    11591191      </p>
    1160       <div id="rfc.figure.u.29"></div><pre class="text">  Content-Encoding: gzip
     1192      <div id="rfc.figure.u.27"></div><pre class="text">  Content-Encoding: gzip
    11611193</pre><p id="rfc.section.5.5.p.5">The content-coding is a characteristic of the entity identified by the request-target. Typically, the entity-body is stored
    11621194         with this encoding and is only decoded before rendering or analogous usage. However, a non-transparent proxy <em class="bcp14">MAY</em> modify the content-coding if the new coding is known to be acceptable to the recipient, unless the "no-transform" cache-control
    … …  
    11751207         Note that this might not be equivalent to all the languages used within the entity-body.
    11761208      </p>
    1177       <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.31"></span><span id="rfc.iref.g.32"></span>  <a href="#header.content-language" class="smpl">Content-Language</a>   = "Content-Language" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-language" class="smpl">Content-Language-v</a>
     1209      <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.31"></span><span id="rfc.iref.g.32"></span>  <a href="#header.content-language" class="smpl">Content-Language</a>   = "Content-Language" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-language" class="smpl">Content-Language-v</a>
    11781210  <a href="#header.content-language" class="smpl">Content-Language-v</a> = 1#<a href="#language.tags" class="smpl">language-tag</a>
    11791211</pre><p id="rfc.section.5.6.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;2.4</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate entities according to the user's
    11801212         own preferred language. Thus, if the body content is intended only for a Danish-literate audience, the appropriate field is
    11811213      </p>
    1182       <div id="rfc.figure.u.31"></div><pre class="text">  Content-Language: da
     1214      <div id="rfc.figure.u.29"></div><pre class="text">  Content-Language: da
    11831215</pre><p id="rfc.section.5.6.p.5">If no Content-Language is specified, the default is that the content is intended for all language audiences. This might mean
    11841216         that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language
    … …  
    11881220         simultaneously in the original Maori and English versions, would call for
    11891221      </p>
    1190       <div id="rfc.figure.u.32"></div><pre class="text">  Content-Language: mi, en
     1222      <div id="rfc.figure.u.30"></div><pre class="text">  Content-Language: mi, en
    11911223</pre><p id="rfc.section.5.6.p.8">However, just because multiple languages are present within an entity does not mean that it is intended for multiple linguistic
    11921224         audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin," which is clearly intended
    … …  
    12031235         accessed, the server <em class="bcp14">SHOULD</em> provide a Content-Location for the particular variant which is returned.
    12041236      </p>
    1205       <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.33"></span><span id="rfc.iref.g.34"></span>  <a href="#header.content-location" class="smpl">Content-Location</a>   = "Content-Location" ":" <a href="#core.rules" class="smpl">OWS</a>
     1237      <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.33"></span><span id="rfc.iref.g.34"></span>  <a href="#header.content-location" class="smpl">Content-Location</a>   = "Content-Location" ":" <a href="#core.rules" class="smpl">OWS</a>
    12061238                    <a href="#header.content-location" class="smpl">Content-Location-v</a>
    12071239  <a href="#header.content-location" class="smpl">Content-Location-v</a> =
    … …  
    12241256         attacks.)
    12251257      </p>
    1226       <div id="rfc.figure.u.34"></div><pre class="inline"><span id="rfc.iref.g.35"></span><span id="rfc.iref.g.36"></span>  <a href="#header.content-md5" class="smpl">Content-MD5</a>   = "Content-MD5" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-md5" class="smpl">Content-MD5-v</a>
     1258      <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.35"></span><span id="rfc.iref.g.36"></span>  <a href="#header.content-md5" class="smpl">Content-MD5</a>   = "Content-MD5" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-md5" class="smpl">Content-MD5-v</a>
    12271259  <a href="#header.content-md5" class="smpl">Content-MD5-v</a> = &lt;base64 of 128 bit MD5 digest as per <a href="#RFC1864" id="rfc.xref.RFC1864.2"><cite title="The Content-MD5 Header Field">[RFC1864]</cite></a>&gt;
    12281260</pre><p id="rfc.section.5.8.p.3">The Content-MD5 header field <em class="bcp14">MAY</em> be generated by an origin server or client to function as an integrity check of the entity-body. Only origin servers or clients <em class="bcp14">MAY</em> generate the Content-MD5 header field; proxies and gateways <em class="bcp14">MUST NOT</em> generate it, as this would defeat its value as an end-to-end integrity check. Any recipient of the entity-body, including
    … …  
    12611293         the HEAD method, the media type that would have been sent had the request been a GET.
    12621294      </p>
    1263       <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span>  <a href="#header.content-type" class="smpl">Content-Type</a>   = "Content-Type" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-type" class="smpl">Content-Type-v</a>
     1295      <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span>  <a href="#header.content-type" class="smpl">Content-Type</a>   = "Content-Type" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-type" class="smpl">Content-Type-v</a>
    12641296  <a href="#header.content-type" class="smpl">Content-Type-v</a> = <a href="#media.types" class="smpl">media-type</a>
    12651297</pre><p id="rfc.section.5.9.p.3">Media types are defined in <a href="#media.types" title="Media Types">Section&nbsp;2.3</a>. An example of the field is
    12661298      </p>
    1267       <div id="rfc.figure.u.36"></div><pre class="text">  Content-Type: text/html; charset=ISO-8859-4
     1299      <div id="rfc.figure.u.34"></div><pre class="text">  Content-Type: text/html; charset=ISO-8859-4
    12681300</pre><p id="rfc.section.5.9.p.5">Further discussion of methods for identifying the media type of an entity is provided in <a href="#type" title="Type">Section&nbsp;3.2.1</a>.
    12691301      </p>
    … …  
    15891621         environments.
    15901622      </p>
    1591       <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.39"></span><span id="rfc.iref.g.40"></span>  <a href="#mime-version" class="smpl">MIME-Version</a>   = "MIME-Version" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#mime-version" class="smpl">MIME-Version-v</a>
     1623      <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.39"></span><span id="rfc.iref.g.40"></span>  <a href="#mime-version" class="smpl">MIME-Version</a>   = "MIME-Version" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#mime-version" class="smpl">MIME-Version-v</a>
    15921624  <a href="#mime-version" class="smpl">MIME-Version-v</a> = 1*<a href="#notation" class="smpl">DIGIT</a> "." 1*<a href="#notation" class="smpl">DIGIT</a>
    15931625</pre><p id="rfc.section.A.1.p.3">MIME version "1.0" is the default for use in HTTP/1.1. However, HTTP/1.1 message parsing and semantics are defined by this
    … …  
    16471679         in <a href="#RFC2183" id="rfc.xref.RFC2183.3"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a>.
    16481680      </p>
    1649       <div id="rfc.figure.u.38"></div><pre class="inline"><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span><span id="rfc.iref.g.45"></span><span id="rfc.iref.g.46"></span><span id="rfc.iref.g.47"></span>  <a href="#content-disposition" class="smpl">content-disposition</a> = "Content-Disposition" ":" <a href="#core.rules" class="smpl">OWS</a>
     1681      <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span><span id="rfc.iref.g.45"></span><span id="rfc.iref.g.46"></span><span id="rfc.iref.g.47"></span>  <a href="#content-disposition" class="smpl">content-disposition</a> = "Content-Disposition" ":" <a href="#core.rules" class="smpl">OWS</a>
    16501682                        <a href="#content-disposition" class="smpl">content-disposition-v</a>
    16511683  <a href="#content-disposition" class="smpl">content-disposition-v</a> = <a href="#content-disposition" class="smpl">disposition-type</a>
    … …  
    16571689  <a href="#content-disposition" class="smpl">disp-extension-parm</a> = <a href="#core.rules" class="smpl">token</a> "=" ( <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a> )
    16581690</pre><p id="rfc.section.B.1.p.3">An example is</p>
    1659       <div id="rfc.figure.u.39"></div><pre class="text">  Content-Disposition: attachment; filename="fname.ext"
     1691      <div id="rfc.figure.u.37"></div><pre class="text">  Content-Disposition: attachment; filename="fname.ext"
    16601692</pre><p id="rfc.section.B.1.p.5">The receiving user agent <em class="bcp14">SHOULD NOT</em> respect any directory path information present in the filename-parm parameter, which is the only parameter believed to apply
    16611693         to HTTP implementations at this time. The filename <em class="bcp14">SHOULD</em> be treated as a terminal component only.
    … …  
    16871719      </p>
    16881720      <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    1689       <div id="rfc.figure.u.40"></div> <pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = "Accept:" OWS Accept-v
     1721      <div id="rfc.figure.u.38"></div> <pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = "Accept:" OWS Accept-v
    16901722<a href="#header.accept-charset" class="smpl">Accept-Charset</a> = "Accept-Charset:" OWS Accept-Charset-v
    16911723<a href="#header.accept-charset" class="smpl">Accept-Charset-v</a> = *( "," OWS ) ( charset / "*" ) [ OWS ";" OWS "q="
    … …  
    17761808
    17771809
    1778 </pre> <div id="rfc.figure.u.41"></div>
     1810</pre> <div id="rfc.figure.u.39"></div>
    17791811      <p>ABNF diagnostics:</p><pre class="inline">; Accept defined but not used
    17801812; Accept-Charset defined but not used

  • draft-ietf-httpbis/latest/p3-payload.xml

    r458 r459  
    10001000<t>
    10011001   have the following precedence:
    1002 </t>
    1003 <figure><artwork type="example">
    1004     1) text/html;level=1
    1005     2) text/html
    1006     3) text/*
    1007     4) */*
    1008 </artwork></figure>
     1002   <list style="numbers">
     1003    <t>text/html;level=1</t>
     1004    <t>text/html</t>
     1005    <t>text/*</t>
     1006    <t>*/*</t>
     1007   </list>
     1008</t>
    10091009<t>
    10101010   The media type quality factor associated with a given type is
    … …  
    10191019   would cause the following values to be associated:
    10201020</t>
    1021 <figure><artwork type="example">
    1022     text/html;level=1         = 1
    1023     text/html                 = 0.7
    1024     text/plain                = 0.3
    1025     image/jpeg                = 0.5
    1026     text/html;level=2         = 0.4
    1027     text/html;level=3         = 0.7
    1028 </artwork></figure>
     1021<texttable align="left">
     1022  <ttcol>Media Type</ttcol><ttcol>Quality Value</ttcol>
     1023  <c>text/html;level=1</c>    <c>1</c>
     1024  <c>text/html</c>            <c>0.7</c>
     1025  <c>text/plain</c>           <c>0.3</c>
     1026  <c>image/jpeg</c>           <c>0.5</c>
     1027  <c>text/html;level=2</c>    <c>0.4</c>
     1028  <c>text/html;level=3</c>    <c>0.7</c>
     1029</texttable>
    10291030<t>
    10301031      <x:h>Note:</x:h> A user agent might be provided with a default set of quality
Note: See TracChangeset for help on using the changeset viewer.