Ignore:
Timestamp:
04/08/10 15:03:20 (10 years ago)
Author:
julian.reschke@…
Message:

regen HTML using latest version of xslt

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/orig/rfc4234.html

    r598 r978  
    3737}
    3838
    39 dl.empty dd {
     39ul.empty {
     40  list-style-type: none;
     41}
     42ul.empty li {
    4043  margin-top: .5em;
    4144}
     
    118121}
    119122table.header {
     123  border-spacing: 1px;
    120124  width: 95%;
    121125  font-size: 10pt;
     
    129133  white-space: nowrap;
    130134}
    131 td.header {
     135table.header td {
    132136  background-color: gray;
    133137  width: 50%;
    134138}
    135 td.header a {
     139table.header a {
    136140  color: white;
    137141}
     
    305309      <link rel="Alternate" title="Authorative ASCII Version" href="http://www.ietf.org/rfc/rfc4234.txt">
    306310      <link rel="Help" title="Additional Information on tools.ietf.org" href="http://tools.ietf.org/html/rfc4234">
    307       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.438, 2009-05-27 13:34:05, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     311      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.520, 2010-07-14 12:36:35, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    308312      <meta name="keywords" content="ABNF, Augmented, Backus-Naur, Form, electronic, mail">
    309       <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    310       <meta name="DC.Creator" content="Crocker, D.">
    311       <meta name="DC.Creator" content="Overell, P.">
    312       <meta name="DC.Identifier" content="urn:ietf:rfc:4234">
    313       <meta name="DC.Date.Issued" scheme="ISO8601" content="2005-10">
    314       <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2234">
    315       <meta name="DC.Description.Abstract" content="Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity, with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order- independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications.">
    316       <meta name="DC.isPartOf" content="urn:ISSN:2070-1721">
     313      <link rel="schema.dct" href="http://purl.org/dc/terms/">
     314      <meta name="dct.creator" content="Crocker, D.">
     315      <meta name="dct.creator" content="Overell, P.">
     316      <meta name="dct.identifier" content="urn:ietf:rfc:4234">
     317      <meta name="dct.issued" scheme="ISO8601" content="2005-10">
     318      <meta name="dct.replaces" content="urn:ietf:rfc:2234">
     319      <meta name="dct.abstract" content="Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity, with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order- independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications.">
     320      <meta name="dct.isPartOf" content="urn:issn:2070-1721">
     321      <meta name="description" content="Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity, with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order- independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications.">
    317322   </head>
    318323   <body>
    319       <table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1">
    320          <tr>
    321             <td class="header left">Network Working Group</td>
    322             <td class="header right">D. Crocker, Editor</td>
    323          </tr>
    324          <tr>
    325             <td class="header left">Request for Comments: 4234</td>
    326             <td class="header right">Brandenburg InternetWorking</td>
    327          </tr>
    328          <tr>
    329             <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2234">2234</a></td>
    330             <td class="header right">P. Overell</td>
    331          </tr>
    332          <tr>
    333             <td class="header left">Category: Standards Track</td>
    334             <td class="header right">THUS plc.</td>
    335          </tr>
    336          <tr>
    337             <td class="header left"></td>
    338             <td class="header right">October 2005</td>
    339          </tr>
     324      <table class="header">
     325         <tbody>
     326            <tr>
     327               <td class="left">Network Working Group</td>
     328               <td class="right">D. Crocker, Editor</td>
     329            </tr>
     330            <tr>
     331               <td class="left">Request for Comments: 4234</td>
     332               <td class="right">Brandenburg InternetWorking</td>
     333            </tr>
     334            <tr>
     335               <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2234">2234</a></td>
     336               <td class="right">P. Overell</td>
     337            </tr>
     338            <tr>
     339               <td class="left">Category: Standards Track</td>
     340               <td class="right">THUS plc.</td>
     341            </tr>
     342            <tr>
     343               <td class="left"></td>
     344               <td class="right">October 2005</td>
     345            </tr>
     346         </tbody>
    340347      </table>
    341348      <p class="title">Augmented BNF for Syntax Specifications: ABNF</p>
     
    482489</pre>  <p>will match "abc", "Abc", "aBc", "abC", "ABc", "aBC", "AbC", and "ABC".</p>
    483490      <p id="rfc.section.2.3.p.10"> </p>
    484       <dl class="empty">
    485          <dd>To specify a rule that IS case SENSITIVE, specify the characters individually.</dd>
    486       </dl>
     491      <ul class="empty">
     492         <li>To specify a rule that IS case SENSITIVE, specify the characters individually.</li>
     493      </ul>
    487494      <div id="rfc.figure.u.8"></div>
    488495      <p>For example:</p>  <pre class="text">
     
    522529      </p>
    523530      <p id="rfc.section.3.1.p.5">NOTE: </p>
    524       <dl class="empty">
    525          <dd>This specification for ABNF does not provide for implicit specification of linear white space.</dd>
    526       </dl>
     531      <ul class="empty">
     532         <li>This specification for ABNF does not provide for implicit specification of linear white space.</li>
     533      </ul>
    527534      <p id="rfc.section.3.1.p.6">Any grammar that wishes to permit linear white space around delimiters or string segments must specify it explicitly. It is
    528535         often useful to provide for such white space in "core" rules that are then used variously among higher-level rules. The "core"
     
    621628         (loosest) at the bottom:
    622629      </p>
    623       <dl class="empty">
    624          <dd>Strings, Names formation</dd>
    625          <dd>Comment</dd>
    626          <dd>Value range</dd>
    627          <dd>Repetition</dd>
    628          <dd>Grouping, Optional</dd>
    629          <dd>Concatenation</dd>
    630          <dd>Alternative</dd>
    631       </dl>
     630      <ul class="empty">
     631         <li>Strings, Names formation</li>
     632         <li>Comment</li>
     633         <li>Value range</li>
     634         <li>Repetition</li>
     635         <li>Grouping, Optional</li>
     636         <li>Concatenation</li>
     637         <li>Alternative</li>
     638      </ul>
    632639      <p id="rfc.section.3.10.p.2">Use of the alternative operator, freely mixed with concatenations, can be confusing.</p>
    633640      <p id="rfc.section.3.10.p.3"> </p>
    634       <dl class="empty">
    635          <dd>Again, it is recommended that the grouping operator be used to make explicit concatenation groups.</dd>
    636       </dl>
     641      <ul class="empty">
     642         <li>Again, it is recommended that the grouping operator be used to make explicit concatenation groups.</li>
     643      </ul>
    637644      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;ABNF DEFINITION OF ABNF
    638645      </h1>
     
    717724      <h2 id="rfc.references.1"><a href="#rfc.section.6.1" id="rfc.section.6.1">6.1.</a> Normative References
    718725      </h2>
    719       <table summary="Normative References"
     726      <table
    720727         <tr>
    721728            <td class="reference"><b id="US-ASCII">[US-ASCII]</b></td>
     
    727734      <h2 id="rfc.references.2"><a href="#rfc.section.6.2" id="rfc.section.6.2">6.2.</a> Informative References
    728735      </h2>
    729       <table summary="Informative References">     
    730          <!--WARNING: unused reference 'RFC2234'-->
     736      <table>     
    731737         <tr>
    732738            <td class="reference"><b id="RFC2234">[RFC2234]</b></td>
     
    741747         <tr>
    742748            <td class="reference"><b id="RFC822">[RFC822]</b></td>
    743             <td class="top"><a href="mailto:DCrocker@UDel-Relay" title="University of Delaware, Dept. of Electrical&#xA;                     Engineering">Crocker, D.H.</a>, “<a href="http://tools.ietf.org/html/rfc822">Standard for the format of ARPA Internet text messages</a>”, STD&nbsp;11, RFC&nbsp;822, August&nbsp;1982.
     749            <td class="top"><a href="mailto:DCrocker@UDel-Relay" title="University of Delaware, Dept. of Electrical&#xA;                     Engineering">Crocker, D.</a>, “<a href="http://tools.ietf.org/html/rfc822">Standard for the format of ARPA Internet text messages</a>”, STD&nbsp;11, RFC&nbsp;822, August&nbsp;1982.
    744750            </td>
    745751         </tr>
    746752      </table>
    747       <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
    748       <address class="vcard"><span class="vcardline"><span class="fn">Dave Crocker</span>
    749             (editor)
    750             <span class="n hidden"><span class="family-name">Crocker</span><span class="given-name">Dave</span></span></span><span class="org vcardline">Brandenburg InternetWorking</span><span class="adr"><span class="street-address vcardline">675 Spruce Dr.</span><span class="vcardline"><span class="locality">Sunnyvale</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">94086</span></span><span class="country-name vcardline">US</span></span><span class="vcardline tel">Phone: <a href="tel:+1.408.246.8253"><span class="value">+1.408.246.8253</span></a></span><span class="vcardline">EMail: <a href="mailto:dcrocker@bbiw.net"><span class="email">dcrocker@bbiw.net</span></a></span></address>
    751       <address class="vcard"><span class="vcardline"><span class="fn">Paul Overell</span><span class="n hidden"><span class="family-name">Overell</span><span class="given-name">Paul</span></span></span><span class="org vcardline">THUS plc.</span><span class="adr"><span class="street-address vcardline">1/2 Berkeley Square, </span><span class="street-address vcardline">99 Berkeley Street</span><span class="vcardline"><span class="locality">Glasgow</span>, <span class="postal-code">G3 7HR</span></span><span class="country-name vcardline">UK</span></span><span class="vcardline">EMail: <a href="mailto:paul.overell@thus.net"><span class="email">paul.overell@thus.net</span></a></span></address>
    752       <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a>&nbsp;ACKNOWLEDGEMENTS
     753      <div class="avoidbreak">
     754         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
     755         <address class="vcard"><span class="vcardline"><span class="fn">Dave Crocker</span>
     756               (editor)
     757               <span class="n hidden"><span class="family-name">Crocker</span><span class="given-name">Dave</span></span></span><span class="org vcardline">Brandenburg InternetWorking</span><span class="adr"><span class="street-address vcardline">675 Spruce Dr.</span><span class="vcardline"><span class="locality">Sunnyvale</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">94086</span></span><span class="country-name vcardline">US</span></span><span class="vcardline tel">Phone: <a href="tel:+1.408.246.8253"><span class="value">+1.408.246.8253</span></a></span><span class="vcardline">EMail: <a href="mailto:dcrocker@bbiw.net"><span class="email">dcrocker@bbiw.net</span></a></span></address>
     758         <address class="vcard"><span class="vcardline"><span class="fn">Paul Overell</span><span class="n hidden"><span class="family-name">Overell</span><span class="given-name">Paul</span></span></span><span class="org vcardline">THUS plc.</span><span class="adr"><span class="street-address vcardline">1/2 Berkeley Square,</span><span class="street-address vcardline">99 Berkeley Street</span><span class="vcardline"><span class="locality">Glasgow</span>, <span class="postal-code">G3 7HR</span></span><span class="country-name vcardline">UK</span></span><span class="vcardline">EMail: <a href="mailto:paul.overell@thus.net"><span class="email">paul.overell@thus.net</span></a></span></address>
     759      </div>
     760      <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;ACKNOWLEDGEMENTS
    753761      </h1>
    754762      <p id="rfc.section.A.p.1">The syntax for ABNF was originally specified in RFC 733. Ken L. Harrenstien, of SRI International, was responsible for re-coding
     
    842850      <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result
    843851         of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users
    844          of this specification can be obtained from the IETF on-line IPR repository at &lt;<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>&gt;.
     852         of this specification can be obtained from the IETF on-line IPR repository at <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
    845853      </p>
    846854      <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
Note: See TracChangeset for help on using the changeset viewer.